Fixed typo
diff --git a/source/documentation/geosparql/geosparql-fuseki.md b/source/documentation/geosparql/geosparql-fuseki.md
index 1c09150..2de806b 100644
--- a/source/documentation/geosparql/geosparql-fuseki.md
+++ b/source/documentation/geosparql/geosparql-fuseki.md
@@ -24,7 +24,7 @@
## Clarifications on GeoSPARQL
### Geographic Markup Language (GML)
-GeoSPARQL refers to the Geographic Markup Language (GML) as one format for `GeometryLiterals`. This does not mean that GML is part of the GeoSPARQL standard. Instead a subset of geometry encodings from the GML standards are permitted (specifically the `GML 2.0 Simple Features Profile (10-100r3)` is supported by GeoSPARQL Jena). The expected encoding of data is in RDF triples and can be loaded from any RDF file format supported by Apache Jena. Conversion of GML to RDF is out of scope of the GeopSARQL standard and Apache Jena.
+GeoSPARQL refers to the Geographic Markup Language (GML) as one format for `GeometryLiterals`. This does not mean that GML is part of the GeoSPARQL standard. Instead a subset of geometry encodings from the GML standards are permitted (specifically the `GML 2.0 Simple Features Profile (10-100r3)` is supported by GeoSPARQL Jena). The expected encoding of data is in RDF triples and can be loaded from any RDF file format supported by Apache Jena. Conversion of GML to RDF is out of scope of the GeoSPARQL standard and Apache Jena.
### Geo Predicates Lat/Lon
Historically, geopsatial data has frequently been encoded as Latitude/Longitude coordinates in the WGS84 coordinate reference system. The GeoSPARQL standard specifically chooses not to adopt this approach and instead uses the more versatile `GeomtryLiteral`, which permits multiple encoding formats that support multiple coordinate reference systems and geometry shapes. Therefore, Lat/Lon Geo Predicates are not part of the GeoSPARQL standard. However, GeoSPARQL Jena provides two methods to support users with geo predicates in their geosptail data.
