Merge branch 'main' into fix-imgs

book/content/Getting_Started.md

@@ -9,27 +9,25 @@ will guide you through taking the two onboarding surveys and gaining access to t
 required credentials and information to get you on the hub.
 
 
-2. Once we have your survey, within the next day or two we will invite you to the CryoCloud GitHub organization and CryoCloudUsers team (you will receive an email from GitHub 
-when we do this). Please accept this invitation within 7 days or it will disappear and we will have to 
-resend it. Your membership on that GitHub team provides you with access to the CryoCloud.
+2. Once we have your survey, within the next day or two we will invite you to the CryoCloud GitHub organization and CryoCloudUsers team (you will receive an email when we do this from GitHub at the email you have linked to your GitHub profile). Please accept this invitation within 7 days or it will disappear and we will have to resend it. Your membership on that GitHub team provides you with access to the CryoCloud.
 
 
-3. Open up the [CryoCloud JupyterHub](https://hub.cryointhecloud.com) to make sure it works for you. 
+4. Open up the [CryoCloud JupyterHub](https://hub.cryointhecloud.com) to make sure it works for you. 
 You will need your Github username and password to sign on.
 
 
-4. Watch the [CryoCloud training recording](https://youtu.be/bBNPuVEG4lE) to learn your way around the CryoCloud.
+5. Watch the [CryoCloud training recording](https://youtu.be/bBNPuVEG4lE) to learn your way around the CryoCloud.
 
 
-5. Fill out the [CryoCloud Onboarding Survey](https://forms.gle/8Mr9Ykc8M7jY9fCd7). This 
+6. Fill out the [CryoCloud Onboarding Survey](https://forms.gle/8Mr9Ykc8M7jY9fCd7). This 
 Onboarding Survey will be one of the most important outcomes of the CryoCloud program to help 
 us ensure we are building infrastructure and community 
 practices that best meet your needs. We will gather a subset of the survey information at 6-month intervals to gauge the change that CryoCloud has produced. This survey will take ~5-10 min. Thank you for your time in filling out this survey!
 
 
-6. Add yourself to our [Slack channel](https://join.slack.com/t/cryospherecloud/shared_invite/zt-1isgbeuhh-q~cYYKtn_6i3PR1alGca_g) 
+7. Add yourself to our [Slack channel](https://join.slack.com/t/cryospherecloud/shared_invite/zt-1isgbeuhh-q~cYYKtn_6i3PR1alGca_g) 
 to join the community, get updates, and ask any questions.
 
 
-7. We welcome feedback on the onboarding training in a [short anonymous feedback form](https://forms.gle/2C7mHpwnwzWa8USk9), 
+8. We welcome feedback on the onboarding training in a [short anonymous feedback form](https://forms.gle/2C7mHpwnwzWa8USk9), 
 which will help us to improve the training system for the next group of CryoCloud users. 


book/content/hub_best_practices.md

@@ -42,7 +42,7 @@ If you want to use an older/different environment from our CryoCloud repositorie
 
 If you want to use a tag from Docker Hub
 * Search for them in [https://hub.docker.com/](https://hub.docker.com/)
-* The tags will take the form of `account/image:tag`: `tensorflow/tensorflow:latest`
+* The tags will take the form of `account/image:tag` (e.g., `pangeo/ml-notebook:latest`).
 
 ***
 

book/how_tos/background/python.md

@@ -94,7 +94,7 @@ Then, also in your home directory, create a new textfile called `.condarc` (the
 envs_dirs:
  - ~/envs
 ```
-This will indicates to conda that all the new environments have to live inside `~envs` (`~` is the unix character for your home directory). 
+This will indicates to conda that all the new environments have to live inside `~envs` (`~` is the unix character for your home directory). In doing so, you ensure that the new environments you build will be permanent to your CryoCloud account. 
 ````
 
 You can now create a new environment with `conda`.

book/how_tos/data_access/index.md

@@ -6,6 +6,11 @@ outside developers to get more "stable" packages. Please let us know if you enco
 any issues with these. Data access tutorials are currently all derived from the NASA OpenScapes cookbook.
 
 ## Data Access Notebooks covered here
-* Creation and access to an S3 bucket
-* Single and multi-file access to cloud optimized geotiffs via HTTPS and S3 buckets
-* Single and multi-file access to NetCDFs and HDF5 files via S3 buckets
+* [Setting up an AWS S3 bucket](https://book.cryointhecloud.com/how_tos/data_access/Instructions_for_configuring_AWS_S3_bucket.html)
+* [Using the CryoCloud S3 scratch bucket](https://book.cryointhecloud.com/how_tos/data_access/CryoCloudScratchBucket.html)
+* [Access Sentinel 2 data](https://book.cryointhecloud.com/how_tos/data_access/Cloud_Sentinel2_access.html)
+* [Access cloud-optimized Geotiff via HTTPS](https://book.cryointhecloud.com/external/Earthdata_Cloud__Single_File__HTTPS_Access_COG_Example.html)
+* [Cloud-optimized Geotiff via S3 Direct Access](https://book.cryointhecloud.com/external/Earthdata_Cloud__Single_File_Direct_S3_Access_COG_Example.html)
+* [Multiple cloud-optimized Geotiff via S3 Direct Access](https://book.cryointhecloud.com/external/Multi-File_Direct_S3_Access_COG_Example.html)
+* [NetCDF4/HDF5 via S3 Direct Access](https://book.cryointhecloud.com/external/Earthdata_Cloud__Single_File__Direct_S3_Access_NetCDF4_Example.html)
+* [Multiple NetCDF/HDF5 via S3 Direct Access](https://book.cryointhecloud.com/external/Multi-File_Direct_S3_Access_NetCDF_Example.html)

book/tutorials/NASA-Earthdata-Cloud-Access/4.icepyx.ipynb

@@ -5,7 +5,6 @@
    "id": "7fd4844a-aee8-4a9c-b22a-02688a8067f9",
    "metadata": {},
    "source": [
-    "# NASA Earthdata Cloud and data access using earthaccess and icepyx\n",
     "# Part 2: Using the `icepyx` python library to access ICESat-2 data\n",
     "\n",
     "## Tutorial Overview\n",