aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDavid Robillard <d@drobilla.net>2020-10-13 20:11:00 +0200
committerDavid Robillard <d@drobilla.net>2020-10-27 13:13:59 +0100
commit9911a658c0205fa3fb04706604e804ede0a5b047 (patch)
tree8aa635f2a6a915d46c802514ec2b5a70eeb0b097
parent9c9effab183be6333fc5f67add4ccc52fd3c16fe (diff)
downloadserd-9911a658c0205fa3fb04706604e804ede0a5b047.tar.gz
serd-9911a658c0205fa3fb04706604e804ede0a5b047.tar.bz2
serd-9911a658c0205fa3fb04706604e804ede0a5b047.zip
fixup! WIP: Improve documentation
-rw-r--r--serd/serd.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/serd/serd.h b/serd/serd.h
index 04decb82..d816cf5c 100644
--- a/serd/serd.h
+++ b/serd/serd.h
@@ -150,7 +150,7 @@ typedef uint32_t SerdSerialisationFlags;
An RDF node, in the abstract sense, can be either a resource, literal, or a
blank. This type is more precise, because syntactically there are two ways
to refer to a resource (by URI or CURIE). Serd also has support for
- variables nodes to support some features, which are not RDF nodes.
+ variable nodes to support some features, which are not RDF nodes.
There are also two ways to refer to a blank node in syntax (by ID or
anonymously), but this is handled by statement flags rather than distinct