diff --git a/spec/index.html b/spec/index.html
index fe4b7a3..2b63706 100644
--- a/spec/index.html
+++ b/spec/index.html
@@ -194,7 +194,7 @@
[[[RDF11-CONCEPTS]]] [[RDF11-CONCEPTS]] lacks clarity on the representation of
language-tagged strings,
- where language tags of the form `xx-YY`
+ where language tags of the form `xx-YY`
are treated as being case insensitive. Implementations might represent language tags
using all lower case in the form `xx-yy`,
retain the original representation `xx-YY`,
@@ -202,10 +202,10 @@
Introduction
leading to different canonical forms, and therefore, different hashed values.
- The Canonicalization algorithm is based on the RDF 1.1 definition,
- in the sense that the language tag `xx-YY`
+ in the sense that the language tag `xx-YY`
is case insensitive, which might lead to different canonicalizations if the user is not aware of this problem.
- User communities ought to agree to use lower case
- language tags,
+ language tags,
while being aware that some implementations might normalize language tags,
affecting hash values.
- Future evolution of RDF might regulate this issue, which RDF environments might have to adapt to,
@@ -1064,8 +1064,8 @@
Algorithm
and associated canonical identifiers.
- [[RDF12-CONCEPTS]] allows implementations to convert
-
language tags to lower case
+ [[RDF11-CONCEPTS]] allows implementations to convert
+
language tags to lower case
leading to different canonical forms of
language-tagged strings.
A possible solution is to require that all triples including a
language-tagged string
@@ -3539,7 +3539,7 @@
A Canonical form of N-Quads
as appropriate.
[[RDF11-CONCEPTS]] allows implementations to convert
-
language tags
+
language tags.
This represents a potential interoperability issue if language tags
are not converted to lower case uniformly, as different implementations
might end up using different canonical representations of such language tags.