Updating to four terrain parameters

Author: jackdmarquez

hands-on/session II/1.Tutorial.ipynb

@@ -101,7 +101,7 @@
     "\n",
     "###  -- Option A: Generating Data Using the SOMOSPIE Application Module\n",
     "\n",
-    "We use the [SOMOSPIE](https://github.com/TauferLab/SOMOSPIE) application, specifically its GEOtiled module, to generate a high-resolution dataset of terrain parameters. This process involves using Digital Elevation Models (DEMs) from the USGS 3D Elevation Program as input. The GEOtiled module processes this data to produce two key terrain parameters: elevation, and hillshading, all at a 30 m resolution specifically for the state of Tennessee. The output consists of four TIFF format image files, each representing the calculated elevation, and hillshading."
+    "We use the [SOMOSPIE](https://github.com/TauferLab/SOMOSPIE) application, specifically its GEOtiled module, to generate a high-resolution dataset of terrain parameters. This process involves using Digital Elevation Models (DEMs) from the USGS 3D Elevation Program as input. The GEOtiled module processes this data to produce two key terrain parameters: aspect, slope, elevation, and hillshading, all at a 30 m resolution specifically for the state of Tennessee. The output consists of four TIFF format image files, each representing the calculated aspect, slope, elevation, and hillshading."
    ]
   },
   {
@@ -228,9 +228,9 @@
    "id": "c7a45c22",
    "metadata": {},
    "source": [
-    "The following cell takes the processed DEMs and calculates the other terrain parameter (hillshading). \n",
+    "The following cell takes the processed DEMs and calculates the other terrain parameter (aspect, slope, and hillshading). \n",
     "\n",
-    "***Note:** This cell is compute-heavy because we are calculating the hillshading from the elevation. Therefore, it can take up to 10 mins.* "
+    "***Note:** This cell is compute-heavy because we are calculating the other three terrain parameters from the elevation. Therefore, it can take up to 10 mins.* "
    ]
   },
   {
@@ -268,7 +268,7 @@
    "id": "75c83ed2",
    "metadata": {},
    "source": [
-    "The following cell uses the GEOtiled library to visualize the four terrain parameters: elevation, and hillshading.\n",
+    "The following cell uses the GEOtiled library to visualize the four terrain parameters: aspect, slope, elevation, and hillshading.\n",
     "\n",
     "***Note:** This cell can take up to 5 mins to visualize the data.* "
    ]
@@ -338,7 +338,7 @@
    "source": [
     "### -> Option B. Accessing Data from Dataverse Public Commons\n",
     "\n",
-    "High-resolution data for elevation and hillshading at a 30m resolution for Tennessee might already exist in public storage repositories. If available, you can directly download this data to proceed to Step 2 without the need for initial data generation."
+    "High-resolution data for elevation, aspect, slope and hillshading at a 30m resolution for Tennessee might already exist in public storage repositories. If available, you can directly download this data to proceed to Step 2 without the need for initial data generation."
    ]
   },
   {
@@ -387,7 +387,8 @@
    "id": "8eeb8a50",
    "metadata": {},
    "source": [
-    "The following cell uses the GEOtiled library to verify the download step and visualize the four terrain parameters: elevation, and hillshading. \n",
+    "The following cell uses the GEOtiled library to verify the download step and visualize the four terrain parameters: aspect, slope, elevation, and hillshading. \n",
+    "\n",
     "***Note:** This cell can take up to 5 mins to visualize the data.* "
    ]
   },
@@ -582,7 +583,7 @@
    "source": [
     "### - Option A: Loading the Dataset from Local Storage\n",
     "\n",
-    "This option involves importing the dataset into the dashboard directly from local storage contained within the Docker image."
+    "This option involves importing the dataset into the dashboard directly from local storage contained within the Codespace."
    ]
   },
   {