Minor edits to 10-remote-data.ipynb (#208)

Author: geographika

workshop/jupyter/content/notebooks/10-remote-data.ipynb

@@ -35,7 +35,7 @@
    "metadata": {},
    "source": [
     "## OGC API\n",
-    "In recent yeays OGC has been developing a family of Standards that improves, and will eventually replace, the OGC Web Service Standards (WMS, WFS, WCS, WPS, etc.) These newer Standards build upon the legacy of the OGC Web Service Standards, but define resource-centric APIs that take advantage of modern web development practices. They are designed to make it easy for ANYONE to provide and use geospatial data on the web, and to integrate this data with ANY other type of information. "
+    "In recent years OGC has been developing a family of Standards that improves, and will eventually replace, the OGC Web Service Standards (WMS, WFS, WCS, WPS, etc.) These newer Standards build upon the legacy of the OGC Web Service Standards, but define resource-centric APIs that take advantage of modern web development practices. They are designed to make it easy for ANYONE to provide and use geospatial data on the web, and to integrate this data with ANY other type of information. "
    ]
   },
   {
@@ -313,7 +313,7 @@
     "OGC Web Feature Service (WFS) can be used to download vector data (called *Features*) from a remote server.\n",
     "In [Lesson 04 - Vector Data](04-vector-data.ipynb) we have learned that vector data\n",
     "can come in various formats. With WFS the default format is GML, both \"flat\", record-like Simple Features,\n",
-    "but also as more complex GML application schema data. Most WFS implementations though, notably GeoServer, will\n",
+    "but also as more complex GML application schema data. Most WFS implementations though, notably GeoServer and MapServer, will\n",
     "also allow you to download data in additional vector formats such as GeoJSON and even as ESRI Shapefiles.\n",
     "\n",
     "When talking about \"WFS\", the OGC WFS version 1 and 2 is meant. Recently OGC has focused efforts on modernizing the  OWS specifications, which are a total rewrite (using REST, OpenAPI and GeoJSON). As a result, WFS has been rebranded as \"OGC API - Features\".\n",
@@ -674,9 +674,9 @@
    "source": [
     "## Searching for the data in CSW server - OPTIONAL\n",
     "This last section is quite advanced, you may want to skip if\n",
-    "time pressures.\n",
+    "there are time pressures.\n",
     "\n",
-    "We will use a metadata service (CSW) to find our target \n",
+    "We will use a metadata service (CSW - Catalogue Services for the Web) to find our target \n",
     "data service, a regular WFS (v2). All via OWSLib.\n",
     "\n",
     "### Step 1 - Find WFS endpoints by querying a CSW endpoint"
@@ -766,7 +766,7 @@
    },
    "source": [
     "### Step 2 - Get the WFS endpoint and interact with it\n",
-    "Let's have a look at WFS data in czech Geology survey."
+    "Let's have a look at WFS data from the Czech Geology survey."
    ]
   },
   {
@@ -857,7 +857,7 @@
     "tags": []
    },
    "source": [
-    "Print list of available layers "
+    "Print a list of available layers "
    ]
   },
   {