diff --git a/why_we_use_git_and_gitlab.ipynb b/why_we_use_git_and_gitlab.ipynb
index 39887505aa2921db2a1eae0daed21a84f2953906..c296f7a7bc60d2139d66e7a4d895a790329783d1 100644
--- a/why_we_use_git_and_gitlab.ipynb
+++ b/why_we_use_git_and_gitlab.ipynb
@@ -180,7 +180,7 @@
     "<ul>\n",
     "No. You should convert to GeoJSON. Besides, you can always convert back if you ever needed to!\n",
     "<br>\n",
-    "Also, unlike shape files which have dependent files (.shx, .dbf, .prj) at risk of getting misplaced or left untracked, with GeoJSON there is only one file to track (.geojson). GeoJSON files are just text, so we can visibly see any edits made to the files in GitLab as they are made. We can also easily manipulate the files using programming languages like Python or R! These are a few reasons we ask that any geospatial data you have be converted to GeoJSON before pushing it to the repository. Conversion is painless, and there is a Jupyter Notebook in this folder to help.\n",
+    "Also, unlike shape files which have dependent files (.shx, .dbf, .prj) at risk of getting misplaced or left untracked, with GeoJSON there is only one file to track (.geojson). GeoJSON files are just text, so we can visibly see any edits made to the files in GitLab as they are made. We can also easily manipulate the files using programming languages like Python or R! These are a few reasons we ask that any geospatial data you have be converted to GeoJSON before pushing it to the repository. Conversion is painless, and if you need help you can reach out to someone on the CID team for a conversion utility.\n",
     "</font>"
    ]
   },