diff --git a/.nojekyll b/.nojekyll
index 7ba6bfa..e340b45 100644
--- a/.nojekyll
+++ b/.nojekyll
@@ -1 +1 @@
-144c66a5
\ No newline at end of file
+a4c06b20
\ No newline at end of file
diff --git a/approach/tooling.html b/approach/tooling.html
index 76d490b..5e8971c 100644
--- a/approach/tooling.html
+++ b/approach/tooling.html
@@ -492,13 +492,14 @@ <h3 class="anchored" data-anchor-id="channel-definitions">Channel definitions</h
 <section id="slack-integration-with-github" class="level3">
 <h3 class="anchored" data-anchor-id="slack-integration-with-github">Slack integration with GitHub</h3>
 <p>We’d love for most resource sharing and conversations to happen in the open and in a more persistent location than Slack. Places like GitHub Discussions are great for this. Thanks to <a href="https://github.com/MattF-NSIDC">Matt Fisher</a> for getting us started with Slack notifications for GitHub Discussions.</p>
-<p>We can set a Slack channel to subscribe to one repo, and one type of event. Subscribing a channel looks like:<br>
-<code>/github subscribe NASA-Openscapes/earthdata-cloud-cookbook discussions</code></p>
-<p>This will subscribe to the default notifications + discussions. We then have to unsubscribe from the defaults to quiet it down:<br>
-<code>/github unsubscribe NASA-Openscapes/earthdata-cloud-cookbook issues pulls commits releases deployments</code></p>
-<p>This can be repeated on any channel and we can add/remove repos and events at will.</p>
-<p><strong>Example:</strong> The Slack #nasa-mentors channel is set to get notified of new and answered <a href="https://github.com/NASA-Openscapes/earthdata-cloud-cookbook/discussions">discussions</a> for just the <a href="https://github.com/NASA-Openscapes/earthdata-cloud-cookbook">Earthdata Cloud Cookbook GitHub repo</a>.</p>
-<p>In Slack, we can run <code>/github help</code> to get some more info on the command to modify subscriptions. Full <a href="https://github.com/integrations/slack/blob/master/README.md">documentation</a></p>
+<p>We can subscribe Slack channels by repository and event types we’re interested in. In Slack, we can run <code>/github help</code> to get some more info on the command to modify subscriptions. <a href="https://github.com/integrations/slack/blob/master/README.md">Full documentation</a>.</p>
+<section id="example" class="level4">
+<h4 class="anchored" data-anchor-id="example">Example</h4>
+<p>The Slack <code>#nasa-mentors</code> channel is set to get notified of new and answered <a href="https://github.com/NASA-Openscapes/earthdata-cloud-cookbook/discussions">discussions</a> for just the <a href="https://github.com/NASA-Openscapes/earthdata-cloud-cookbook">Earthdata Cloud Cookbook GitHub repo</a>. The subscription process was started with this command:</p>
+<pre><code>/github subscribe NASA-Openscapes/earthdata-cloud-cookbook discussions</code></pre>
+<p>The above will subscribe to “discussions” in addition to undesirable <a href="https://github.com/integrations/slack/blob/master/README.md#customize-your-notifications">default notifications</a>. We can unsubscribe from the defaults to quiet it down with another comment:</p>
+<pre><code>/github unsubscribe NASA-Openscapes/earthdata-cloud-cookbook issues pulls commits releases deployments</code></pre>
+</section>
 </section>
 </section>
 <section id="sec-zenodo" class="level2">
diff --git a/search.json b/search.json
index 9d06fef..5858011 100644
--- a/search.json
+++ b/search.json
@@ -193,7 +193,7 @@
     "href": "approach/tooling.html#slack",
     "title": "Tooling",
     "section": "Slack",
-    "text": "Slack\nAre you inviting someone to join Openscapes Slack? Send them the link to this section.\nHave you received an invitation to join Openscapes Slack? Here’s some information to help you get comfortable.\nOpenscapes uses the free Slack plan. This means we can all see message history for the previous 90 days.\nHow do I use it? Slack can feel like a daunting new tool, especially when we’re introducing lots of new tools during Champions Cohorts. There are both technical and etiquette aspects to getting comfortable. For technical tips see Getting started for new members and How to use Slack. This Slack quick start guide Woodley and Pratt (2020) from the Center for Scientific Collaboration and Community Engagement includes 1) configuring your account; 2) channels and notifications; 3) communicating.\nAbout Openscapes Slack: We use Slack as a way to build community by hosting a space for people to connect with each other around Openscapes-relevant topics. We want it to be a supportive, trust-based community of folks doing data intensive science. Members include, but are not limited to, people who have participated in a Champions Program, NASA Openscapes Framework, Pathways to Open Science, Reflections, NASA Cloud Cookbook Hackdays, or other Openscapes programs. Current Slack members can invite others to join - an informal sponsorship approach.\nWhen you join, you’ll automatically land in several channels: #welcome, #cool-finds, #events, #general, #random, #seaside-chats, #shared-joy 🌈. You can browse other channels and choose to join them. People are invariably friendly and open to asking and answering questions. You can get a feel for how things work by “listening” to the discussions, then jump right in!\nIf you’re part of a cohort for an Openscapes program you’ll also be invited to a private cohort channel. Open isn’t all or nothing; being open with this cohort you’re getting to know is a good way to start getting comfortable with the Slack community more broadly.\nThe #welcome channel is a place for new members to introduce themselves and for the rest of us to help them feel welcome by adding an emoji or saying “I work on sea turtles too!”. Here’s a short read on The Value of #Welcome.\n\nChannel definitions\nThese definitions are meant to help people know where to post or ask questions. They are listed in the Slack channel Topic and Description (because the Topic preview is easily visible in the channel, while the Description, not so much).\nWhen people join, they automatically land in #welcome #general #seaside-chats #events #cool-finds #shared-joy #random.\n#welcome: A place for people new to our community to introduce themselves and for the rest of us to make them feel welcome; the default channel that members cannot leave if they leave all other channels\n#general: Openscapes team posts Openscapes announcements\n#seaside-chats: A place to discuss ongoing progress. Friendly Q & A about good enough practices, team culture, tools …\n#events: Events that might be of interest to others in our community. Openscapes events go in #general\n#cool-finds: Posts, datasets, podcasts, repos, papers, videos, packages, …things you found that are cool\n#jobs: Job opportunities, seeking work, offers to connect people with those “on the inside”\n#shared-joy: Sharing joy of any shape or size\n#random: Non-work banter and water cooler conversation\n\n\nSlack integration with GitHub\nWe’d love for most resource sharing and conversations to happen in the open and in a more persistent location than Slack. Places like GitHub Discussions are great for this. Thanks to Matt Fisher for getting us started with Slack notifications for GitHub Discussions.\nWe can set a Slack channel to subscribe to one repo, and one type of event. Subscribing a channel looks like:\n/github subscribe NASA-Openscapes/earthdata-cloud-cookbook discussions\nThis will subscribe to the default notifications + discussions. We then have to unsubscribe from the defaults to quiet it down:\n/github unsubscribe NASA-Openscapes/earthdata-cloud-cookbook issues pulls commits releases deployments\nThis can be repeated on any channel and we can add/remove repos and events at will.\nExample: The Slack #nasa-mentors channel is set to get notified of new and answered discussions for just the Earthdata Cloud Cookbook GitHub repo.\nIn Slack, we can run /github help to get some more info on the command to modify subscriptions. Full documentation"
+    "text": "Slack\nAre you inviting someone to join Openscapes Slack? Send them the link to this section.\nHave you received an invitation to join Openscapes Slack? Here’s some information to help you get comfortable.\nOpenscapes uses the free Slack plan. This means we can all see message history for the previous 90 days.\nHow do I use it? Slack can feel like a daunting new tool, especially when we’re introducing lots of new tools during Champions Cohorts. There are both technical and etiquette aspects to getting comfortable. For technical tips see Getting started for new members and How to use Slack. This Slack quick start guide Woodley and Pratt (2020) from the Center for Scientific Collaboration and Community Engagement includes 1) configuring your account; 2) channels and notifications; 3) communicating.\nAbout Openscapes Slack: We use Slack as a way to build community by hosting a space for people to connect with each other around Openscapes-relevant topics. We want it to be a supportive, trust-based community of folks doing data intensive science. Members include, but are not limited to, people who have participated in a Champions Program, NASA Openscapes Framework, Pathways to Open Science, Reflections, NASA Cloud Cookbook Hackdays, or other Openscapes programs. Current Slack members can invite others to join - an informal sponsorship approach.\nWhen you join, you’ll automatically land in several channels: #welcome, #cool-finds, #events, #general, #random, #seaside-chats, #shared-joy 🌈. You can browse other channels and choose to join them. People are invariably friendly and open to asking and answering questions. You can get a feel for how things work by “listening” to the discussions, then jump right in!\nIf you’re part of a cohort for an Openscapes program you’ll also be invited to a private cohort channel. Open isn’t all or nothing; being open with this cohort you’re getting to know is a good way to start getting comfortable with the Slack community more broadly.\nThe #welcome channel is a place for new members to introduce themselves and for the rest of us to help them feel welcome by adding an emoji or saying “I work on sea turtles too!”. Here’s a short read on The Value of #Welcome.\n\nChannel definitions\nThese definitions are meant to help people know where to post or ask questions. They are listed in the Slack channel Topic and Description (because the Topic preview is easily visible in the channel, while the Description, not so much).\nWhen people join, they automatically land in #welcome #general #seaside-chats #events #cool-finds #shared-joy #random.\n#welcome: A place for people new to our community to introduce themselves and for the rest of us to make them feel welcome; the default channel that members cannot leave if they leave all other channels\n#general: Openscapes team posts Openscapes announcements\n#seaside-chats: A place to discuss ongoing progress. Friendly Q & A about good enough practices, team culture, tools …\n#events: Events that might be of interest to others in our community. Openscapes events go in #general\n#cool-finds: Posts, datasets, podcasts, repos, papers, videos, packages, …things you found that are cool\n#jobs: Job opportunities, seeking work, offers to connect people with those “on the inside”\n#shared-joy: Sharing joy of any shape or size\n#random: Non-work banter and water cooler conversation\n\n\nSlack integration with GitHub\nWe’d love for most resource sharing and conversations to happen in the open and in a more persistent location than Slack. Places like GitHub Discussions are great for this. Thanks to Matt Fisher for getting us started with Slack notifications for GitHub Discussions.\nWe can subscribe Slack channels by repository and event types we’re interested in. In Slack, we can run /github help to get some more info on the command to modify subscriptions. Full documentation.\n\nExample\nThe Slack #nasa-mentors channel is set to get notified of new and answered discussions for just the Earthdata Cloud Cookbook GitHub repo. The subscription process was started with this command:\n/github subscribe NASA-Openscapes/earthdata-cloud-cookbook discussions\nThe above will subscribe to “discussions” in addition to undesirable default notifications. We can unsubscribe from the defaults to quiet it down with another comment:\n/github unsubscribe NASA-Openscapes/earthdata-cloud-cookbook issues pulls commits releases deployments"
   },
   {
     "objectID": "approach/tooling.html#sec-zenodo",
diff --git a/sitemap.xml b/sitemap.xml
index 48516ea..4b2163a 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2,118 +2,118 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://openscapes.github.io/approach-guide/contributing/inspiration.html</loc>
-    <lastmod>2023-11-15T17:46:16.233Z</lastmod>
+    <lastmod>2023-11-15T18:21:44.923Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/contributing/index.html</loc>
-    <lastmod>2023-11-15T17:46:15.409Z</lastmod>
+    <lastmod>2023-11-15T18:21:44.103Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/contributing/resources.html</loc>
-    <lastmod>2023-11-15T17:46:14.793Z</lastmod>
+    <lastmod>2023-11-15T18:21:43.499Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/mentors-framework/index.html</loc>
-    <lastmod>2023-11-15T17:46:14.073Z</lastmod>
+    <lastmod>2023-11-15T18:21:42.791Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/mentors-framework/nasa-openscapes.html</loc>
-    <lastmod>2023-11-15T17:46:13.173Z</lastmod>
+    <lastmod>2023-11-15T18:21:41.863Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/LICENSE.html</loc>
-    <lastmod>2023-11-15T17:46:12.425Z</lastmod>
+    <lastmod>2023-11-15T18:21:41.099Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/code-of-conduct.html</loc>
-    <lastmod>2023-11-15T17:46:11.757Z</lastmod>
+    <lastmod>2023-11-15T18:21:40.423Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/tooling.html</loc>
-    <lastmod>2023-11-15T17:46:10.961Z</lastmod>
+    <lastmod>2023-11-15T18:21:39.623Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/seaside-chats.html</loc>
-    <lastmod>2023-11-15T17:46:09.765Z</lastmod>
+    <lastmod>2023-11-15T18:21:38.431Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/partners.html</loc>
-    <lastmod>2023-11-15T17:46:08.833Z</lastmod>
+    <lastmod>2023-11-15T18:21:37.471Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/lessons.html</loc>
-    <lastmod>2023-11-15T17:46:07.917Z</lastmod>
+    <lastmod>2023-11-15T18:21:36.559Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/design.html</loc>
-    <lastmod>2023-11-15T17:46:07.145Z</lastmod>
+    <lastmod>2023-11-15T18:21:35.779Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/pre-cohort-engage.html</loc>
-    <lastmod>2023-11-15T17:46:06.309Z</lastmod>
+    <lastmod>2023-11-15T18:21:34.923Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/cohort-planning.html</loc>
-    <lastmod>2023-11-15T17:46:04.865Z</lastmod>
+    <lastmod>2023-11-15T18:21:33.507Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/pre-cohort-tech.html</loc>
-    <lastmod>2023-11-15T17:46:03.153Z</lastmod>
+    <lastmod>2023-11-15T18:21:31.799Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/leading-cohort-calls.html</loc>
-    <lastmod>2023-11-15T17:46:04.489Z</lastmod>
+    <lastmod>2023-11-15T18:21:33.131Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/about.html</loc>
-    <lastmod>2023-11-15T17:46:05.161Z</lastmod>
+    <lastmod>2023-11-15T18:21:33.803Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/index.html</loc>
-    <lastmod>2023-11-15T17:46:06.725Z</lastmod>
+    <lastmod>2023-11-15T18:21:35.339Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/champions/post-cohort-followup.html</loc>
-    <lastmod>2023-11-15T17:46:07.529Z</lastmod>
+    <lastmod>2023-11-15T18:21:36.171Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/qual-assessment.html</loc>
-    <lastmod>2023-11-15T17:46:08.513Z</lastmod>
+    <lastmod>2023-11-15T18:21:37.155Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/index.html</loc>
-    <lastmod>2023-11-15T17:46:09.213Z</lastmod>
+    <lastmod>2023-11-15T18:21:37.879Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/onboarding.html</loc>
-    <lastmod>2023-11-15T17:46:10.137Z</lastmod>
+    <lastmod>2023-11-15T18:21:38.799Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/documentation.html</loc>
-    <lastmod>2023-11-15T17:46:11.349Z</lastmod>
+    <lastmod>2023-11-15T18:21:40.015Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/approach/calendar.html</loc>
-    <lastmod>2023-11-15T17:46:12.069Z</lastmod>
+    <lastmod>2023-11-15T18:21:40.727Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/mentors-framework/engage.html</loc>
-    <lastmod>2023-11-15T17:46:12.709Z</lastmod>
+    <lastmod>2023-11-15T18:21:41.383Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/mentors-framework/onboarding.html</loc>
-    <lastmod>2023-11-15T17:46:13.753Z</lastmod>
+    <lastmod>2023-11-15T18:21:42.487Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/index.html</loc>
-    <lastmod>2023-11-15T17:46:14.505Z</lastmod>
+    <lastmod>2023-11-15T18:21:43.195Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/contributing/workflow.html</loc>
-    <lastmod>2023-11-15T17:46:15.089Z</lastmod>
+    <lastmod>2023-11-15T18:21:43.799Z</lastmod>
   </url>
   <url>
     <loc>https://openscapes.github.io/approach-guide/contributing/setup.html</loc>
-    <lastmod>2023-11-15T17:46:15.717Z</lastmod>
+    <lastmod>2023-11-15T18:21:44.399Z</lastmod>
   </url>
 </urlset>