diff --git a/docs/current/insights/agile.html b/docs/current/insights/agile.html
index 9c3b0eb..0502e36 100644
--- a/docs/current/insights/agile.html
+++ b/docs/current/insights/agile.html
@@ -39,7 +39,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/docs/current/insights/bias_lack_of_diversity.html b/docs/current/insights/bias_lack_of_diversity.html
index eda337e..6c269c4 100644
--- a/docs/current/insights/bias_lack_of_diversity.html
+++ b/docs/current/insights/bias_lack_of_diversity.html
@@ -39,7 +39,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/docs/current/insights/governance.html b/docs/current/insights/governance.html
index a3981e2..0de1622 100644
--- a/docs/current/insights/governance.html
+++ b/docs/current/insights/governance.html
@@ -39,7 +39,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
@@ -303,11 +303,9 @@ <h2 id="toc-title">Table of contents</h2>
    
   <ul>
   <li><a href="#pre-readings" id="toc-pre-readings" class="nav-link active" data-scroll-target="#pre-readings"><span class="header-section-number">8.1</span> Pre-Readings</a></li>
-  <li><a href="#how-do-open-source-projects-make-decisions" id="toc-how-do-open-source-projects-make-decisions" class="nav-link" data-scroll-target="#how-do-open-source-projects-make-decisions"><span class="header-section-number">9</span> How do open source projects make decisions?</a>
-  <ul class="collapse">
-  <li><a href="#recent-innovations-in-decision-making" id="toc-recent-innovations-in-decision-making" class="nav-link" data-scroll-target="#recent-innovations-in-decision-making"><span class="header-section-number">9.1</span> Recent innovations in decision making</a></li>
-  <li><a href="#exercise-note-taking-via-google-docs" id="toc-exercise-note-taking-via-google-docs" class="nav-link" data-scroll-target="#exercise-note-taking-via-google-docs"><span class="header-section-number">9.2</span> Exercise: Note-taking via google docs</a></li>
-  </ul></li>
+  <li><a href="#how-do-open-source-projects-make-decisions" id="toc-how-do-open-source-projects-make-decisions" class="nav-link" data-scroll-target="#how-do-open-source-projects-make-decisions"><span class="header-section-number">8.2</span> How do open source projects make decisions?</a></li>
+  <li><a href="#recent-innovations-in-decision-making" id="toc-recent-innovations-in-decision-making" class="nav-link" data-scroll-target="#recent-innovations-in-decision-making"><span class="header-section-number">8.3</span> Recent innovations in decision making</a></li>
+  <li><a href="#exercise-note-taking-via-google-docs" id="toc-exercise-note-taking-via-google-docs" class="nav-link" data-scroll-target="#exercise-note-taking-via-google-docs"><span class="header-section-number">8.4</span> Exercise: Note-taking via google docs</a></li>
   </ul>
 <div class="toc-actions"><ul><li><a href="https://github.com/howisonlab/open_source_software_course/blob/master/quarto_course/insights/governance.qmd" class="toc-action"><i class="bi bi-github"></i>View source</a></li></ul></div></nav>
     </div>
@@ -345,8 +343,8 @@ <h2 data-number="8.1" class="anchored" data-anchor-id="pre-readings"><span class
 </ol>
 <p>Extra optional reading: Podcast on “Learning from Open Source”: <a href="https://a16z.com/podcast/learning-from-open-source-communities/" class="uri">https://a16z.com/podcast/learning-from-open-source-communities/</a>. We will have readings from this later in the course, so useful to do now.</p>
 </section>
-<section id="how-do-open-source-projects-make-decisions" class="level1" data-number="9">
-<h1 data-number="9"><span class="header-section-number">9</span> How do open source projects make decisions?</h1>
+<section id="how-do-open-source-projects-make-decisions" class="level2" data-number="8.2">
+<h2 data-number="8.2" class="anchored" data-anchor-id="how-do-open-source-projects-make-decisions"><span class="header-section-number">8.2</span> How do open source projects make decisions?</h2>
 <p>Working in a project requires many decisions, e.g.,:</p>
 <ul>
 <li>Choosing a project name</li>
@@ -362,8 +360,9 @@ <h1 data-number="9"><span class="header-section-number">9</span> How do open sou
 <li>Corporate hierarchy</li>
 <li>Consensus</li>
 </ul>
-<section id="recent-innovations-in-decision-making" class="level2" data-number="9.1">
-<h2 data-number="9.1" class="anchored" data-anchor-id="recent-innovations-in-decision-making"><span class="header-section-number">9.1</span> Recent innovations in decision making</h2>
+</section>
+<section id="recent-innovations-in-decision-making" class="level2" data-number="8.3">
+<h2 data-number="8.3" class="anchored" data-anchor-id="recent-innovations-in-decision-making"><span class="header-section-number">8.3</span> Recent innovations in decision making</h2>
 <p>While we may think the process of creating new models of decision making in groups has stopped or slowed, recent innovations abound:</p>
 <ul>
 <li>Occupy Wall Street Hand signals used during discussion at <a href="https://en.wikipedia.org/wiki/General_assembly_(Occupy_movement)" class="uri">https://en.wikipedia.org/wiki/General_assembly_(Occupy_movement)</a></li>
@@ -375,8 +374,8 @@ <h2 data-number="9.1" class="anchored" data-anchor-id="recent-innovations-in-dec
 <p>Students and faculty at the University of Texas are involved with a project (and software) to <a href="https://constituteproject.org/topics?lang=en">compare the texts of Constitutions around the world.</a>. Including using <code>diffs</code> (just like git does) to understand changes. e.g., <a href="https://constituteproject.org/constitutions?lang=en&amp;status=in_force&amp;status=is_historic&amp;status=is_draft&amp;compare=Algeria_2016&amp;compare=Algeria_2020">changes in Algeria’s constitution (diff 1989 2020)</a>. “Constitute was developed by the Comparative Constitutions Project at the University of Texas at Austin and the University of Chicago, directed by <a href="https://liberalarts.utexas.edu/government/faculty/elkinszs">Zachary Elkins</a> and Tom Ginsburg.”</p>
 <p><!-- "OSS Watch Governance Models", --> <!--   "http://oss-watch.ac.uk/resources/governancemodels", --> <!--   "Governance", --> <!-- "Shah, S. K. (2006). Motivation, governance, and the viability of hybrid forms in open source software development. Management Science, 52(7), 1000–1014.", --> <!--   "https://doi.org/10.1287/mnsc.1060.0553", --> <!--   "Governance", --> <!-- "Chapter 4 \"Social and Political Infrastructure\" from Fogel, Karl (2018) \"Producing OSS: How to Run a Successful Free Software Project\"", --> <!--   "https://producingoss.com/en/social-infrastructure.html", --> <!--   "Governance", --> <!-- "Chapter 8 \"Managing Participants\" from from Fogel, Karl (2018) \"Producing OSS: How to Run a Successful Free Software Project\"", --> <!--   "https://producingoss.com/en/managing-participants.html", --> <!--   "Governance", --> <!-- "Optional (except for Doctoral and aspiring doctoral students) Shaikh, M., & Henfridsson, O. (2017). Governing open source software through coordination processes. Information and Organization, 27(2), 116–135.", --> <!--   "https://doi.org/10.1016/j.infoandorg.2017.04.001", --> <!--   "Governance", --></p>
 </section>
-<section id="exercise-note-taking-via-google-docs" class="level2" data-number="9.2">
-<h2 data-number="9.2" class="anchored" data-anchor-id="exercise-note-taking-via-google-docs"><span class="header-section-number">9.2</span> Exercise: Note-taking via google docs</h2>
+<section id="exercise-note-taking-via-google-docs" class="level2" data-number="8.4">
+<h2 data-number="8.4" class="anchored" data-anchor-id="exercise-note-taking-via-google-docs"><span class="header-section-number">8.4</span> Exercise: Note-taking via google docs</h2>
 <p>You will be placed into groups of 3 (not sitting near each other):</p>
 <ol type="1">
 <li>Create a google doc and share it</li>
@@ -401,7 +400,6 @@ <h2 data-number="9.2" class="anchored" data-anchor-id="exercise-note-taking-via-
 <!-- https://www.apache.org/foundation/voting.html -->
 
 
-</section>
 </section>
 
 </main> <!-- /main -->
diff --git a/docs/current/insights/licenses.html b/docs/current/insights/licenses.html
index 0a54378..58e6c0f 100644
--- a/docs/current/insights/licenses.html
+++ b/docs/current/insights/licenses.html
@@ -39,7 +39,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/docs/current/insights/motivations.html b/docs/current/insights/motivations.html
index b3afa6d..e8deb28 100644
--- a/docs/current/insights/motivations.html
+++ b/docs/current/insights/motivations.html
@@ -39,7 +39,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/docs/current/insights/paper_plane_innovation.html b/docs/current/insights/paper_plane_innovation.html
index 14ad356..f2135af 100644
--- a/docs/current/insights/paper_plane_innovation.html
+++ b/docs/current/insights/paper_plane_innovation.html
@@ -39,7 +39,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/docs/current/insights/stack_and_stream.html b/docs/current/insights/stack_and_stream.html
index a1d8281..1b13d22 100644
--- a/docs/current/insights/stack_and_stream.html
+++ b/docs/current/insights/stack_and_stream.html
@@ -39,7 +39,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/docs/current/insights/what_is_open_source.html b/docs/current/insights/what_is_open_source.html
index f8e3588..37cd39b 100644
--- a/docs/current/insights/what_is_open_source.html
+++ b/docs/current/insights/what_is_open_source.html
@@ -39,7 +39,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
@@ -392,24 +392,24 @@ <h2 data-number="4.2" class="anchored" data-anchor-id="where-is-open-source"><sp
 <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span class="header-section-number">4.3</span> What is “source”?</h2>
 <div class="cell">
 <div class="cell-output-display">
-<div id="aszsidwink" style="padding-left:0px;padding-right:0px;padding-top:10px;padding-bottom:10px;overflow-x:auto;overflow-y:auto;width:auto;height:auto;">
+<div id="akllrztqwe" style="padding-left:0px;padding-right:0px;padding-top:10px;padding-bottom:10px;overflow-x:auto;overflow-y:auto;width:auto;height:auto;">
 <style>@import url("https://fonts.googleapis.com/css2?family=Noto+Sans:ital,wght@0,100;0,200;0,300;0,400;0,500;0,600;0,700;0,800;0,900;1,100;1,200;1,300;1,400;1,500;1,600;1,700;1,800;1,900&display=swap");
-#aszsidwink table {
+#akllrztqwe table {
   font-family: 'Noto Sans', system-ui, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji';
   -webkit-font-smoothing: antialiased;
   -moz-osx-font-smoothing: grayscale;
 }
 
-#aszsidwink thead, #aszsidwink tbody, #aszsidwink tfoot, #aszsidwink tr, #aszsidwink td, #aszsidwink th {
+#akllrztqwe thead, #akllrztqwe tbody, #akllrztqwe tfoot, #akllrztqwe tr, #akllrztqwe td, #akllrztqwe th {
   border-style: none;
 }
 
-#aszsidwink p {
+#akllrztqwe p {
   margin: 0;
   padding: 0;
 }
 
-#aszsidwink .gt_table {
+#akllrztqwe .gt_table {
   display: table;
   border-collapse: collapse;
   line-height: normal;
@@ -435,12 +435,12 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   border-left-color: #D3D3D3;
 }
 
-#aszsidwink .gt_caption {
+#akllrztqwe .gt_caption {
   padding-top: 4px;
   padding-bottom: 4px;
 }
 
-#aszsidwink .gt_title {
+#akllrztqwe .gt_title {
   color: #333333;
   font-size: 125%;
   font-weight: initial;
@@ -452,7 +452,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   border-bottom-width: 0;
 }
 
-#aszsidwink .gt_subtitle {
+#akllrztqwe .gt_subtitle {
   color: #333333;
   font-size: 85%;
   font-weight: initial;
@@ -464,7 +464,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   border-top-width: 0;
 }
 
-#aszsidwink .gt_heading {
+#akllrztqwe .gt_heading {
   background-color: #F6F6F6;
   text-align: left;
   border-bottom-color: #F6F6F6;
@@ -476,13 +476,13 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   border-right-color: #D3D3D3;
 }
 
-#aszsidwink .gt_bottom_border {
+#akllrztqwe .gt_bottom_border {
   border-bottom-style: solid;
   border-bottom-width: 0px;
   border-bottom-color: #D3D3D3;
 }
 
-#aszsidwink .gt_col_headings {
+#akllrztqwe .gt_col_headings {
   border-top-style: solid;
   border-top-width: 1px;
   border-top-color: #40C5FF;
@@ -497,7 +497,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   border-right-color: #D3D3D3;
 }
 
-#aszsidwink .gt_col_heading {
+#akllrztqwe .gt_col_heading {
   color: #333333;
   background-color: #F6F6F6;
   font-size: 100%;
@@ -517,7 +517,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   overflow-x: hidden;
 }
 
-#aszsidwink .gt_column_spanner_outer {
+#akllrztqwe .gt_column_spanner_outer {
   color: #333333;
   background-color: #F6F6F6;
   font-size: 100%;
@@ -529,15 +529,15 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   padding-right: 4px;
 }
 
-#aszsidwink .gt_column_spanner_outer:first-child {
+#akllrztqwe .gt_column_spanner_outer:first-child {
   padding-left: 0;
 }
 
-#aszsidwink .gt_column_spanner_outer:last-child {
+#akllrztqwe .gt_column_spanner_outer:last-child {
   padding-right: 0;
 }
 
-#aszsidwink .gt_column_spanner {
+#akllrztqwe .gt_column_spanner {
   border-bottom-style: solid;
   border-bottom-width: 2px;
   border-bottom-color: #ECECEC;
@@ -549,11 +549,11 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   width: 100%;
 }
 
-#aszsidwink .gt_spanner_row {
+#akllrztqwe .gt_spanner_row {
   border-bottom-style: hidden;
 }
 
-#aszsidwink .gt_group_heading {
+#akllrztqwe .gt_group_heading {
   padding-top: 8px;
   padding-bottom: 8px;
   padding-left: 5px;
@@ -579,7 +579,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   text-align: left;
 }
 
-#aszsidwink .gt_empty_group_heading {
+#akllrztqwe .gt_empty_group_heading {
   padding: 0.5px;
   color: #333333;
   background-color: #F6F6F6;
@@ -594,15 +594,15 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   vertical-align: middle;
 }
 
-#aszsidwink .gt_from_md > :first-child {
+#akllrztqwe .gt_from_md > :first-child {
   margin-top: 0;
 }
 
-#aszsidwink .gt_from_md > :last-child {
+#akllrztqwe .gt_from_md > :last-child {
   margin-bottom: 0;
 }
 
-#aszsidwink .gt_row {
+#akllrztqwe .gt_row {
   padding-top: 4px;
   padding-bottom: 4px;
   padding-left: 5px;
@@ -621,7 +621,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   overflow-x: hidden;
 }
 
-#aszsidwink .gt_stub {
+#akllrztqwe .gt_stub {
   color: #333333;
   background-color: #F6F6F6;
   font-size: 100%;
@@ -634,7 +634,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   padding-right: 5px;
 }
 
-#aszsidwink .gt_stub_row_group {
+#akllrztqwe .gt_stub_row_group {
   color: #333333;
   background-color: #F6F6F6;
   font-size: 100%;
@@ -648,15 +648,15 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   vertical-align: top;
 }
 
-#aszsidwink .gt_row_group_first td {
+#akllrztqwe .gt_row_group_first td {
   border-top-width: 1px;
 }
 
-#aszsidwink .gt_row_group_first th {
+#akllrztqwe .gt_row_group_first th {
   border-top-width: 1px;
 }
 
-#aszsidwink .gt_summary_row {
+#akllrztqwe .gt_summary_row {
   color: #333333;
   background-color: #F6F6F6;
   text-transform: inherit;
@@ -666,16 +666,16 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   padding-right: 5px;
 }
 
-#aszsidwink .gt_first_summary_row {
+#akllrztqwe .gt_first_summary_row {
   border-top-style: solid;
   border-top-color: #D3D3D3;
 }
 
-#aszsidwink .gt_first_summary_row.thick {
+#akllrztqwe .gt_first_summary_row.thick {
   border-top-width: 2px;
 }
 
-#aszsidwink .gt_last_summary_row {
+#akllrztqwe .gt_last_summary_row {
   padding-top: 8px;
   padding-bottom: 8px;
   padding-left: 5px;
@@ -685,7 +685,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   border-bottom-color: #D3D3D3;
 }
 
-#aszsidwink .gt_grand_summary_row {
+#akllrztqwe .gt_grand_summary_row {
   color: #333333;
   background-color: #F6F6F6;
   text-transform: inherit;
@@ -695,7 +695,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   padding-right: 5px;
 }
 
-#aszsidwink .gt_first_grand_summary_row {
+#akllrztqwe .gt_first_grand_summary_row {
   padding-top: 8px;
   padding-bottom: 8px;
   padding-left: 5px;
@@ -705,7 +705,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   border-top-color: #D3D3D3;
 }
 
-#aszsidwink .gt_last_grand_summary_row_top {
+#akllrztqwe .gt_last_grand_summary_row_top {
   padding-top: 8px;
   padding-bottom: 8px;
   padding-left: 5px;
@@ -715,11 +715,11 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   border-bottom-color: #D3D3D3;
 }
 
-#aszsidwink .gt_striped {
+#akllrztqwe .gt_striped {
   background-color: #ECECEC;
 }
 
-#aszsidwink .gt_table_body {
+#akllrztqwe .gt_table_body {
   border-top-style: solid;
   border-top-width: 2px;
   border-top-color: #D3D3D3;
@@ -728,7 +728,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   border-bottom-color: #FFFFFF;
 }
 
-#aszsidwink .gt_footnotes {
+#akllrztqwe .gt_footnotes {
   color: #333333;
   background-color: #F6F6F6;
   border-bottom-style: none;
@@ -742,7 +742,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   border-right-color: #D3D3D3;
 }
 
-#aszsidwink .gt_footnote {
+#akllrztqwe .gt_footnote {
   margin: 0px;
   font-size: 90%;
   padding-top: 4px;
@@ -751,7 +751,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   padding-right: 5px;
 }
 
-#aszsidwink .gt_sourcenotes {
+#akllrztqwe .gt_sourcenotes {
   color: #333333;
   background-color: #F6F6F6;
   border-bottom-style: none;
@@ -765,7 +765,7 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   border-right-color: #D3D3D3;
 }
 
-#aszsidwink .gt_sourcenote {
+#akllrztqwe .gt_sourcenote {
   font-size: 12px;
   padding-top: 4px;
   padding-bottom: 4px;
@@ -773,72 +773,72 @@ <h2 data-number="4.3" class="anchored" data-anchor-id="what-is-source"><span cla
   padding-right: 5px;
 }
 
-#aszsidwink .gt_left {
+#akllrztqwe .gt_left {
   text-align: left;
 }
 
-#aszsidwink .gt_center {
+#akllrztqwe .gt_center {
   text-align: center;
 }
 
-#aszsidwink .gt_right {
+#akllrztqwe .gt_right {
   text-align: right;
   font-variant-numeric: tabular-nums;
 }
 
-#aszsidwink .gt_font_normal {
+#akllrztqwe .gt_font_normal {
   font-weight: normal;
 }
 
-#aszsidwink .gt_font_bold {
+#akllrztqwe .gt_font_bold {
   font-weight: bold;
 }
 
-#aszsidwink .gt_font_italic {
+#akllrztqwe .gt_font_italic {
   font-style: italic;
 }
 
-#aszsidwink .gt_super {
+#akllrztqwe .gt_super {
   font-size: 65%;
 }
 
-#aszsidwink .gt_footnote_marks {
+#akllrztqwe .gt_footnote_marks {
   font-size: 75%;
   vertical-align: 0.4em;
   position: initial;
 }
 
-#aszsidwink .gt_asterisk {
+#akllrztqwe .gt_asterisk {
   font-size: 100%;
   vertical-align: 0;
 }
 
-#aszsidwink .gt_indent_1 {
+#akllrztqwe .gt_indent_1 {
   text-indent: 5px;
 }
 
-#aszsidwink .gt_indent_2 {
+#akllrztqwe .gt_indent_2 {
   text-indent: 10px;
 }
 
-#aszsidwink .gt_indent_3 {
+#akllrztqwe .gt_indent_3 {
   text-indent: 15px;
 }
 
-#aszsidwink .gt_indent_4 {
+#akllrztqwe .gt_indent_4 {
   text-indent: 20px;
 }
 
-#aszsidwink .gt_indent_5 {
+#akllrztqwe .gt_indent_5 {
   text-indent: 25px;
 }
 
-#aszsidwink .katex-display {
+#akllrztqwe .katex-display {
   display: inline-flex !important;
   margin-bottom: 0.75em !important;
 }
 
-#aszsidwink div.Reactable > div.rt-table > div.rt-thead > div.rt-tr.rt-tr-group-header > div.rt-th-group:after {
+#akllrztqwe div.Reactable > div.rt-table > div.rt-thead > div.rt-tr.rt-tr-group-header > div.rt-th-group:after {
   height: 0px !important;
 }
 </style>
diff --git a/docs/current/search.json b/docs/current/search.json
index 79d416b..1b91335 100644
--- a/docs/current/search.json
+++ b/docs/current/search.json
@@ -406,8 +406,8 @@
     "objectID": "insights/governance.html#recent-innovations-in-decision-making",
     "href": "insights/governance.html#recent-innovations-in-decision-making",
     "title": "8  Governance",
-    "section": "9.1 Recent innovations in decision making",
-    "text": "9.1 Recent innovations in decision making\nWhile we may think the process of creating new models of decision making in groups has stopped or slowed, recent innovations abound:\n\nOccupy Wall Street Hand signals used during discussion at https://en.wikipedia.org/wiki/General_assembly_(Occupy_movement)\n\n\n\nNew constitutions written by countries. e.g., Chile’s new constitution process 2022\n\nStudents and faculty at the University of Texas are involved with a project (and software) to compare the texts of Constitutions around the world.. Including using diffs (just like git does) to understand changes. e.g., changes in Algeria’s constitution (diff 1989 2020). “Constitute was developed by the Comparative Constitutions Project at the University of Texas at Austin and the University of Chicago, directed by Zachary Elkins and Tom Ginsburg.”",
+    "section": "8.3 Recent innovations in decision making",
+    "text": "8.3 Recent innovations in decision making\nWhile we may think the process of creating new models of decision making in groups has stopped or slowed, recent innovations abound:\n\nOccupy Wall Street Hand signals used during discussion at https://en.wikipedia.org/wiki/General_assembly_(Occupy_movement)\n\n\n\nNew constitutions written by countries. e.g., Chile’s new constitution process 2022\n\nStudents and faculty at the University of Texas are involved with a project (and software) to compare the texts of Constitutions around the world.. Including using diffs (just like git does) to understand changes. e.g., changes in Algeria’s constitution (diff 1989 2020). “Constitute was developed by the Comparative Constitutions Project at the University of Texas at Austin and the University of Chicago, directed by Zachary Elkins and Tom Ginsburg.”",
     "crumbs": [
       "Insights",
       "<span class='chapter-number'>8</span>  <span class='chapter-title'>Governance</span>"
@@ -417,8 +417,8 @@
     "objectID": "insights/governance.html#exercise-note-taking-via-google-docs",
     "href": "insights/governance.html#exercise-note-taking-via-google-docs",
     "title": "8  Governance",
-    "section": "9.2 Exercise: Note-taking via google docs",
-    "text": "9.2 Exercise: Note-taking via google docs\nYou will be placed into groups of 3 (not sitting near each other):\n\nCreate a google doc and share it\n\nFor next 2 steps follow two rules:\n\nYou may not talk to each other\nYou may not write instructions to each other in the Google doc (or elsewhere, e.g., chat)\n\n\nWorking in this mode: produce a 2 page summary of:\n\nRoss Gardler & Gabriel Hanganu. (2013). Governance models. OSS-Watch.ac.uk. http://oss-watch.ac.uk/resources/governancemodels\n\nContinuing to work in this mode: include within your text three comparisons with the work linked below (comparisons could include that the work agrees, disagrees, extends, adds example, etc.):\n\nKarl Fogel. (2020). Chapter 8: Managing Participants. In “Producing OSS” Book. https://producingoss.com/en/managing-participants.html\n\nCreate a final heading, “Reflections on working without talking”. Move to sit next to each other. Ironically, you can talk to each other as you write down at least 3 bullet points about your experience doing this note-taking.",
+    "section": "8.4 Exercise: Note-taking via google docs",
+    "text": "8.4 Exercise: Note-taking via google docs\nYou will be placed into groups of 3 (not sitting near each other):\n\nCreate a google doc and share it\n\nFor next 2 steps follow two rules:\n\nYou may not talk to each other\nYou may not write instructions to each other in the Google doc (or elsewhere, e.g., chat)\n\n\nWorking in this mode: produce a 2 page summary of:\n\nRoss Gardler & Gabriel Hanganu. (2013). Governance models. OSS-Watch.ac.uk. http://oss-watch.ac.uk/resources/governancemodels\n\nContinuing to work in this mode: include within your text three comparisons with the work linked below (comparisons could include that the work agrees, disagrees, extends, adds example, etc.):\n\nKarl Fogel. (2020). Chapter 8: Managing Participants. In “Producing OSS” Book. https://producingoss.com/en/managing-participants.html\n\nCreate a final heading, “Reflections on working without talking”. Move to sit next to each other. Ironically, you can talk to each other as you write down at least 3 bullet points about your experience doing this note-taking.",
     "crumbs": [
       "Insights",
       "<span class='chapter-number'>8</span>  <span class='chapter-title'>Governance</span>"
@@ -1122,7 +1122,7 @@
     "href": "skills/packaging.html",
     "title": "23  Packages to distibute code",
     "section": "",
-    "text": "24 What is needed for package management?\nPackages are ways of distributing software. We discussed packages in the material on Stack, Streak and Ecosystem: Chapter 10\nPackages enable us to build on the work of others, when we install packages and import them into our code.\nBut eventually we will have code that we want to distribute to others, whether that be classmates or others within our organization, or perhaps the world at large.\nThere are a few ways that we can distribute code, all with pros and cons.\nCopy and paste. We can send code to others by simply copying and pasting, then sending perhaps by Slack or even through email. A slightly more advanced approach is to use a gist or pastebin such as https://gist.github.com/ or http://pastebin.com. Copy and pasting is quick but it is limited. We then have no way of updating the code, or of knowing where it is used.\nWe can, of course, share code via GitHub or GitLab. Here we can publish a repository, either publicly or within our Organization, and give people the URL. Then people can clone the code into their individual workspaces. At least then the potential user can re-visit for updates and our user would know where they could contact people for issues or even to share improvements.\nBut GitHub on its own does not offer much to manage the complexities of developing software and keeping things up to date over time. For that we must turn to packaging and to package distribution systems which provides the python packages that can be installed by pip. These offer much greater effectiveness: the package publisher can provide updates, bugfixes or improvements, and the user can get informed about when updates are available and have them automatically downloaded.\nPackages and package management offer a few other important advantages:\nPackaging can be thought about in four steps:\nDifferent languages and software ecosystems implement these steps themselves.\nIn Python, for examples, Encapsulation is done with directories, which have files inside with the code (“regular” some_code_name.py files. Metadata is done with additional files inside the directories. The tool pip handles both installation and dependency resolution. For the server that hosts the packages there is one broad public server called PyPI (which stands for the PYthon Package Index), but it is also possible for individual organizations to run a version “behind the firewall” to manage packages within their organization.\nIn R, encapsulation is also done thorugh directories, metadata through files. Package installation is done within the R base software. In R there are a few important central repositories, including CRAN (Comprehensive R Archive Network) and Bioconductor (a separate package manager focused on biology packages, an example of convergent evolution). There are lots of different mirrors for CRAN.\nPackage management “behind the firewall” is so important to firms, that the company that builds Rstudio now offers package management for both R and Python https://packagemanager.posit.co/client/#/ both publically and within companies. Similarly Anaconda a company based in Austin offers package management across an eve wider set of languages.",
+    "text": "23.1 What is needed for package management?\nPackages are ways of distributing software. We discussed packages in the material on Stack, Streak and Ecosystem: Chapter 10\nPackages enable us to build on the work of others, when we install packages and import them into our code.\nBut eventually we will have code that we want to distribute to others, whether that be classmates or others within our organization, or perhaps the world at large.\nThere are a few ways that we can distribute code, all with pros and cons.\nCopy and paste. We can send code to others by simply copying and pasting, then sending perhaps by Slack or even through email. A slightly more advanced approach is to use a gist or pastebin such as https://gist.github.com/ or http://pastebin.com. Copy and pasting is quick but it is limited. We then have no way of updating the code, or of knowing where it is used.\nWe can, of course, share code via GitHub or GitLab. Here we can publish a repository, either publicly or within our Organization, and give people the URL. Then people can clone the code into their individual workspaces. At least then the potential user can re-visit for updates and our user would know where they could contact people for issues or even to share improvements.\nBut GitHub on its own does not offer much to manage the complexities of developing software and keeping things up to date over time. For that we must turn to packaging and to package distribution systems which provides the python packages that can be installed by pip. These offer much greater effectiveness: the package publisher can provide updates, bugfixes or improvements, and the user can get informed about when updates are available and have them automatically downloaded.\nPackages and package management offer a few other important advantages:\nPackaging can be thought about in four steps:\nDifferent languages and software ecosystems implement these steps themselves.\nIn Python, for examples, Encapsulation is done with directories, which have files inside with the code (“regular” some_code_name.py files. Metadata is done with additional files inside the directories. The tool pip handles both installation and dependency resolution. For the server that hosts the packages there is one broad public server called PyPI (which stands for the PYthon Package Index), but it is also possible for individual organizations to run a version “behind the firewall” to manage packages within their organization.\nIn R, encapsulation is also done thorugh directories, metadata through files. Package installation is done within the R base software. In R there are a few important central repositories, including CRAN (Comprehensive R Archive Network) and Bioconductor (a separate package manager focused on biology packages, an example of convergent evolution). There are lots of different mirrors for CRAN.\nPackage management “behind the firewall” is so important to firms, that the company that builds Rstudio now offers package management for both R and Python https://packagemanager.posit.co/client/#/ both publically and within companies. Similarly Anaconda a company based in Austin offers package management across an eve wider set of languages.",
     "crumbs": [
       "Skills",
       "<span class='chapter-number'>23</span>  <span class='chapter-title'>Packages to distibute code</span>"
@@ -1132,8 +1132,8 @@
     "objectID": "skills/packaging.html#from-code-to-published-package-in-python",
     "href": "skills/packaging.html#from-code-to-published-package-in-python",
     "title": "23  Packages to distibute code",
-    "section": "24.1 From code to published package in Python",
-    "text": "24.1 From code to published package in Python\nFor these materials we will work through a Data Camp course (which you are welcome to finish), called Developing Python Packages.\nThe course shows how to take code and wrap it in a directory with special files, then how to publish it to PyPI (using a special repository just for testing).",
+    "section": "23.2 From code to published package in Python",
+    "text": "23.2 From code to published package in Python\nFor these materials we will work through a Data Camp course (which you are welcome to finish), called Developing Python Packages.\nThe course shows how to take code and wrap it in a directory with special files, then how to publish it to PyPI (using a special repository just for testing).",
     "crumbs": [
       "Skills",
       "<span class='chapter-number'>23</span>  <span class='chapter-title'>Packages to distibute code</span>"
@@ -1237,5 +1237,71 @@
       "Appendices",
       "<span class='chapter-number'>B</span>  <span class='chapter-title'>Glossary of Commands</span>"
     ]
+  },
+  {
+    "objectID": "skills/git_rebase.html#rebase-exercise",
+    "href": "skills/git_rebase.html#rebase-exercise",
+    "title": "19  Rebase for synchronizing work",
+    "section": "19.2 Rebase Exercise",
+    "text": "19.2 Rebase Exercise\nIn groups of three, a Maintainer and two contributors, begin by setting up the collaboration network (a new repo, forks, clones and setting upstream). Then work together to implement these steps:\n\nMaintainer makes two commits to the main branch, contributors use git pull upstream main to synchronize.\nEach contributor creates a feature branch, and adds two commits to a file with their name.\nContributors create PRs that the Maintainer sees on the upstream/sahred repository.\nMaintainer can accept one, merging to main.\nMaintainer then asks the other contributor to rebase their contribution.\nThe contributor doing the rebase first does a git pull upstream main to get the new work onto the main branch in their local git.\nThen the contributor uses rebase and squash (as above) and uses git push -f to get their fork syncrhonized with their rebase.\nMaintainer should then check the PR and they will find only a single commit (the two previous ones squashed together), now looking as though it branched off main after the first contributor’s work. Maintainer can then accept the rebased PR.\nBoth contributors should sychronize (git pull upstream main and then git push to sync their forks.)",
+    "crumbs": [
+      "Skills",
+      "<span class='chapter-number'>19</span>  <span class='chapter-title'>Rebase for synchronizing work</span>"
+    ]
+  },
+  {
+    "objectID": "skills/packaging.html#what-is-needed-for-package-management",
+    "href": "skills/packaging.html#what-is-needed-for-package-management",
+    "title": "23  Packages to distibute code",
+    "section": "",
+    "text": "Encapsulating code in a chunk that can be moved around\nMetadata that describes the package, including authorship, licensing and, crucially, dependencies.\nAn installation tool that can bring packages from the server into local environments, and check and manage dependencies.\nA server location to which packages can be published",
+    "crumbs": [
+      "Skills",
+      "<span class='chapter-number'>23</span>  <span class='chapter-title'>Packages to distibute code</span>"
+    ]
+  },
+  {
+    "objectID": "insights/governance.html#how-do-open-source-projects-make-decisions",
+    "href": "insights/governance.html#how-do-open-source-projects-make-decisions",
+    "title": "8  Governance",
+    "section": "8.2 How do open source projects make decisions?",
+    "text": "8.2 How do open source projects make decisions?\nWorking in a project requires many decisions, e.g.,:\n\nChoosing a project name\nDeciding whether to add a color scheme\nChoosing whether to use UK or US spelling rules\nDeciding when to release a new version\n\nProjects have a wide range of ways that they make these decisions (including avoiding having to make decisions!). We call these “governance models”.\nOutside open source there are also many governance models, including very well known ones:\n\nDemocracy (direct and representative)\nDictatorship\nCorporate hierarchy\nConsensus",
+    "crumbs": [
+      "Insights",
+      "<span class='chapter-number'>8</span>  <span class='chapter-title'>Governance</span>"
+    ]
+  },
+  {
+    "objectID": "skills/git_cherrypick_split_pr.html#learngitbranching-exercise",
+    "href": "skills/git_cherrypick_split_pr.html#learngitbranching-exercise",
+    "title": "18  Split a Pull Request",
+    "section": "18.2 LearnGitBranching exercise",
+    "text": "18.2 LearnGitBranching exercise\nWe can see an example of the overall workflow for splitting a PR using the LearnGitBranching Visualizer, I have created a level called Split Pull Request.",
+    "crumbs": [
+      "Skills",
+      "<span class='chapter-number'>18</span>  <span class='chapter-title'>Split a Pull Request</span>"
+    ]
+  },
+  {
+    "objectID": "skills/git_cherrypick_split_pr.html#cherry-pick-via-commandline-git",
+    "href": "skills/git_cherrypick_split_pr.html#cherry-pick-via-commandline-git",
+    "title": "18  Split a Pull Request",
+    "section": "18.3 Cherry-pick via commandline git",
+    "text": "18.3 Cherry-pick via commandline git\nYou can see a situation like this in this repo on GitHub. Bring that to your working space with:\ncd ~\ngit clone https://github.com/jameshowison/i320d-needs-split.git\ncd i320d-needs-split\nIf you then run our git viz command (see Section A.3 for how to set up a short cut for that)\nYou will see both our apple and orange edits all together on the main branch.\njlh5498@educcomp04:~/github_repos/i320d-needs-split$ git viz\n* c70df5a (HEAD -&gt; main) orange2\n* 423ad05 apple2\n* 4f1fe99 orange1\n* 91abdfb apple1\n* 8e35b12 branch here\n* ea4d580 main1\n* 252ff3f Initial commit\nWe eventually want this to look like our first graph above, with two new branches (apple_branch and orange_branch):\njlh5498@educcomp04:~/github_repos/i320d-needs-split$ git viz\n* 09d5482 (HEAD -&gt; orange_branch) orange2\n* 2137500 orange1\n| * c8fd64d (apple_branch) apple2\n| * 1a5ac49 apple1\n|/  \n* 158f2c4 (main) branch here\n* 96d65c3 main2\n* 7036c11 main 1\n* 252ff3f Initial commit\nTo get there we will take three steps:\n\nCreate a new branch, specifying the starting point\nMove the relevant commits to the new branch\nPush to the fork, create a new pull request\n\ngit checkout -b apple_branch 8e35b12\nThe 8e35b12 here is the commit id of the point at which we want the branch to start. Until now when we’ve created a branch we have done so while sitting at HEAD but git allows us to create a branch back in time. Git does this by adding metadata to the earlier commit (labeling it with a branch label).\nThen we can move the commits using git cherry-pick. Note that this doesn’t move them from the main branch, but creates new commits with the same content. This is very much like copying files from one directory into another directory (except we are moving commits from a branch to another branch).\ngit cherry-pick 91abdfb 423ad05\nAgain the strings 91abdfb and 423ad05 identify specific commits. We can provide a list (like above), just one, and it is also possible to provide a range if you want a full sequence of commits.\nAfter the cherry-pick we see:\njlh5498@educcomp04:~/github_repos/i320d-needs-split$ git cherry-pick 91abdfb 423ad05\n[apple_branch 9ca623a] apple1\n Date: Wed Mar 1 15:31:38 2023 -0600\n 1 file changed, 1 insertion(+)\n[apple_branch 2b82f41] apple2\n Date: Wed Mar 1 15:31:38 2023 -0600\n 1 file changed, 1 insertion(+)\njlh5498@educcomp04:~/github_repos/i320d-needs-split$ git viz\n* 2b82f41 (HEAD -&gt; apple_branch) apple2\n* 9ca623a apple1\n| * c70df5a (origin/main, origin/HEAD, main) orange2\n| * 423ad05 apple2\n| * 4f1fe99 orange1\n| * 91abdfb apple1\n|/  \n* 8e35b12 branch here\n* ea4d580 main1\n* 252ff3f Initial commit\nWe can then use git push as normal to push the apple_branch up to the fork and make a pull request.\n\n\n\n\n\n\nNote\n\n\n\nMoving around commits using cherry-pick shows us why it is so important to understand commits as full copies of the state of the working directory, as full snapshots of our files. If commits were just the changes (just a bunch of diffs) then we would have to apply them in the order they were created, otherwise we’d get nonsense results.\nBut because commits are full copies of everything, we can move them around without any logical problems. Think of reordering the trays with the paper planes we used in the first class.\nIn fact, all that git is doing is re-writing the parent for each commit.\nAnd branches are just like little post-its added to some commits, they are just metadata pointers. Neat, isn’t it?\nSee more about this on the GitHub blog https://github.blog/2020-12-17-commits-are-snapshots-not-diffs/",
+    "crumbs": [
+      "Skills",
+      "<span class='chapter-number'>18</span>  <span class='chapter-title'>Split a Pull Request</span>"
+    ]
+  },
+  {
+    "objectID": "skills/git_cherrypick_split_pr.html#exercises",
+    "href": "skills/git_cherrypick_split_pr.html#exercises",
+    "title": "18  Split a Pull Request",
+    "section": "18.4 Exercises",
+    "text": "18.4 Exercises\n\n18.4.1 Individual Exercises\n\nNow you work to get the orange_branch organized.\n\n\n\n18.4.2 Group Exercise\nGroups of 3. Nominate Maintainer, Contributor A, and Contributor B.\n\nMaintainer creates a repo on Github.\nMaintainer adds 2 commits and pushes.\nContributor A and Contributor B fork and clone (and add upstream).\nContributor A and Contributor B create a feature branch called will_need_split.\nContributor A and Contributor B add four commits of four files on will_need_split\nContributor A and Contributor B create a pull request to upstream from their will_need_split branch (including all four commits).\nMaintainer rejects the pull request, closing it and commenting “please split this up” (and direct which files go together, probably 2 in each.)\nContributor A and Contributor B follow procedure above to end up with two new branches split_branch_1 and split_branch_2 send through separate pull requests with only the right commits/files in them.\nMaintainer eventually accepts each of the four split up pull requests.",
+    "crumbs": [
+      "Skills",
+      "<span class='chapter-number'>18</span>  <span class='chapter-title'>Split a Pull Request</span>"
+    ]
   }
 ]
\ No newline at end of file
diff --git a/docs/current/skills/continuous_integration.html b/docs/current/skills/continuous_integration.html
index 195922d..20bf4ff 100644
--- a/docs/current/skills/continuous_integration.html
+++ b/docs/current/skills/continuous_integration.html
@@ -73,7 +73,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/docs/current/skills/git_basic_workflow.html b/docs/current/skills/git_basic_workflow.html
index b886443..c09550c 100644
--- a/docs/current/skills/git_basic_workflow.html
+++ b/docs/current/skills/git_basic_workflow.html
@@ -73,7 +73,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/docs/current/skills/git_cherrypick_split_pr.html b/docs/current/skills/git_cherrypick_split_pr.html
index 232a102..baef890 100644
--- a/docs/current/skills/git_cherrypick_split_pr.html
+++ b/docs/current/skills/git_cherrypick_split_pr.html
@@ -340,11 +340,13 @@
     <h2 id="toc-title">Table of contents</h2>
    
   <ul>
-  <li><a href="#split-before-submit" id="toc-split-before-submit" class="nav-link active" data-scroll-target="#split-before-submit"><span class="header-section-number">18.1</span> Split before submit</a>
+  <li><a href="#split-before-submit" id="toc-split-before-submit" class="nav-link active" data-scroll-target="#split-before-submit"><span class="header-section-number">18.1</span> Split before submit</a></li>
+  <li><a href="#learngitbranching-exercise" id="toc-learngitbranching-exercise" class="nav-link" data-scroll-target="#learngitbranching-exercise"><span class="header-section-number">18.2</span> LearnGitBranching exercise</a></li>
+  <li><a href="#cherry-pick-via-commandline-git" id="toc-cherry-pick-via-commandline-git" class="nav-link" data-scroll-target="#cherry-pick-via-commandline-git"><span class="header-section-number">18.3</span> Cherry-pick via commandline git</a></li>
+  <li><a href="#exercises" id="toc-exercises" class="nav-link" data-scroll-target="#exercises"><span class="header-section-number">18.4</span> Exercises</a>
   <ul class="collapse">
-  <li><a href="#learngitbranching-exercise" id="toc-learngitbranching-exercise" class="nav-link" data-scroll-target="#learngitbranching-exercise"><span class="header-section-number">18.1.1</span> LearnGitBranching exercise</a></li>
-  <li><a href="#cherry-pick-via-commandline-git" id="toc-cherry-pick-via-commandline-git" class="nav-link" data-scroll-target="#cherry-pick-via-commandline-git"><span class="header-section-number">18.1.2</span> Cherry-pick via commandline git</a></li>
-  <li><a href="#exercises" id="toc-exercises" class="nav-link" data-scroll-target="#exercises"><span class="header-section-number">18.1.3</span> Exercises</a></li>
+  <li><a href="#individual-exercises" id="toc-individual-exercises" class="nav-link" data-scroll-target="#individual-exercises"><span class="header-section-number">18.4.1</span> Individual Exercises</a></li>
+  <li><a href="#group-exercise" id="toc-group-exercise" class="nav-link" data-scroll-target="#group-exercise"><span class="header-section-number">18.4.2</span> Group Exercise</a></li>
   </ul></li>
   </ul>
 <div class="toc-actions"><ul><li><a href="https://github.com/howisonlab/open_source_software_course/blob/master/quarto_course/skills/git_cherrypick_split_pr.qmd" class="toc-action"><i class="bi bi-github"></i>View source</a></li></ul></div></nav>
@@ -448,12 +450,13 @@ <h2 data-number="18.1" class="anchored" data-anchor-id="split-before-submit"><sp
 </div>
 </div>
 </div>
-<section id="learngitbranching-exercise" class="level3" data-number="18.1.1">
-<h3 data-number="18.1.1" class="anchored" data-anchor-id="learngitbranching-exercise"><span class="header-section-number">18.1.1</span> LearnGitBranching exercise</h3>
+</section>
+<section id="learngitbranching-exercise" class="level2" data-number="18.2">
+<h2 data-number="18.2" class="anchored" data-anchor-id="learngitbranching-exercise"><span class="header-section-number">18.2</span> LearnGitBranching exercise</h2>
 <p>We can see an example of the overall workflow for splitting a PR using the LearnGitBranching Visualizer, I have created a level called <a href="https://learngitbranching.js.org/?gist_level_id=f7b4b63960ed80fa9a76728d853f2546">Split Pull Request</a>.</p>
 </section>
-<section id="cherry-pick-via-commandline-git" class="level3" data-number="18.1.2">
-<h3 data-number="18.1.2" class="anchored" data-anchor-id="cherry-pick-via-commandline-git"><span class="header-section-number">18.1.2</span> Cherry-pick via commandline git</h3>
+<section id="cherry-pick-via-commandline-git" class="level2" data-number="18.3">
+<h2 data-number="18.3" class="anchored" data-anchor-id="cherry-pick-via-commandline-git"><span class="header-section-number">18.3</span> Cherry-pick via commandline git</h2>
 <p>You can see a situation like this in this repo on GitHub. Bring that to your working space with:</p>
 <div class="sourceCode" id="cb1"><pre class="sourceCode sh code-with-copy"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="bu">cd</span> ~</span>
 <span id="cb1-2"><a href="#cb1-2" aria-hidden="true" tabindex="-1"></a><span class="fu">git</span> clone https://github.com/jameshowison/i320d-needs-split.git</span>
@@ -528,16 +531,16 @@ <h3 data-number="18.1.2" class="anchored" data-anchor-id="cherry-pick-via-comman
 </div>
 </div>
 </section>
-<section id="exercises" class="level3" data-number="18.1.3">
-<h3 data-number="18.1.3" class="anchored" data-anchor-id="exercises"><span class="header-section-number">18.1.3</span> Exercises</h3>
-<section id="individual-exercises" class="level4" data-number="18.1.3.1">
-<h4 data-number="18.1.3.1" class="anchored" data-anchor-id="individual-exercises"><span class="header-section-number">18.1.3.1</span> Individual Exercises</h4>
+<section id="exercises" class="level2" data-number="18.4">
+<h2 data-number="18.4" class="anchored" data-anchor-id="exercises"><span class="header-section-number">18.4</span> Exercises</h2>
+<section id="individual-exercises" class="level3" data-number="18.4.1">
+<h3 data-number="18.4.1" class="anchored" data-anchor-id="individual-exercises"><span class="header-section-number">18.4.1</span> Individual Exercises</h3>
 <ol type="1">
 <li>Now you work to get the <code>orange_branch</code> organized.</li>
 </ol>
 </section>
-<section id="group-exercise" class="level4" data-number="18.1.3.2">
-<h4 data-number="18.1.3.2" class="anchored" data-anchor-id="group-exercise"><span class="header-section-number">18.1.3.2</span> Group Exercise</h4>
+<section id="group-exercise" class="level3" data-number="18.4.2">
+<h3 data-number="18.4.2" class="anchored" data-anchor-id="group-exercise"><span class="header-section-number">18.4.2</span> Group Exercise</h3>
 <p>Groups of 3. Nominate <em>Maintainer</em>, <em>Contributor A</em>, and <em>Contributor B</em>.</p>
 <ol type="1">
 <li><em>Maintainer</em> creates a repo on Github.</li>
@@ -654,7 +657,6 @@ <h4 data-number="18.1.3.2" class="anchored" data-anchor-id="group-exercise"><spa
 <!-- The `revert` approach means messier history, but has the advantage that it doesn't disconnect anyone else. -->
 
 
-</section>
 </section>
 </section>
 
diff --git a/docs/current/skills/git_rebase.html b/docs/current/skills/git_rebase.html
index db727d5..a2dc67f 100644
--- a/docs/current/skills/git_rebase.html
+++ b/docs/current/skills/git_rebase.html
@@ -73,7 +73,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
@@ -341,7 +341,7 @@ <h2 id="toc-title">Table of contents</h2>
    
   <ul>
   <li><a href="#adding-squash" id="toc-adding-squash" class="nav-link active" data-scroll-target="#adding-squash"><span class="header-section-number">19.1</span> Adding squash</a></li>
-  <li><a href="#rebase-exercise" id="toc-rebase-exercise" class="nav-link" data-scroll-target="#rebase-exercise"><span class="header-section-number">20</span> Rebase Exercise</a></li>
+  <li><a href="#rebase-exercise" id="toc-rebase-exercise" class="nav-link" data-scroll-target="#rebase-exercise"><span class="header-section-number">19.2</span> Rebase Exercise</a></li>
   </ul>
 <div class="toc-actions"><ul><li><a href="https://github.com/howisonlab/open_source_software_course/blob/master/quarto_course/skills/git_rebase.qmd" class="toc-action"><i class="bi bi-github"></i>View source</a></li></ul></div></nav>
     </div>
@@ -599,8 +599,8 @@ <h2 data-number="19.1" class="anchored" data-anchor-id="adding-squash"><span cla
 <p>Ignore the remote branch (origin/pie_chart_branch), and focus only on the local branch (HEAD -&gt; pie_chart_branch). Instead of all three commits, we now only see a single commit (c367b8a).</p>
 <p>Note that in these examples we did not encounter any conflicts (because edits were all on different files). In reality, though, when commits are moved around, rebased, and squashed, sometimes those operations result in conflicts (just as happens with merge). In that case git add the conflict symbols (<code>&lt;&lt;&lt;&lt;&lt;&lt;</code> and <code>==========</code> and <code>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;</code>) which all need to be removed, then the files added and finally we run <code>git rebase --continue</code>. Git does provide useful messages through that process with guidance on the likely next steps.</p>
 </section>
-<section id="rebase-exercise" class="level1" data-number="20">
-<h1 data-number="20"><span class="header-section-number">20</span> Rebase Exercise</h1>
+<section id="rebase-exercise" class="level2" data-number="19.2">
+<h2 data-number="19.2" class="anchored" data-anchor-id="rebase-exercise"><span class="header-section-number">19.2</span> Rebase Exercise</h2>
 <p>In groups of three, a Maintainer and two contributors, begin by setting up the collaboration network (a new repo, forks, clones and setting upstream). Then work together to implement these steps:</p>
 <ol type="1">
 <li>Maintainer makes two commits to the main branch, contributors use <code>git pull upstream main</code> to synchronize.</li>
diff --git a/docs/current/skills/git_rewinding_work.html b/docs/current/skills/git_rewinding_work.html
index 87fec8a..ca4da59 100644
--- a/docs/current/skills/git_rewinding_work.html
+++ b/docs/current/skills/git_rewinding_work.html
@@ -73,7 +73,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/docs/current/skills/github_collaboration.html b/docs/current/skills/github_collaboration.html
index ac6f451..b0c554e 100644
--- a/docs/current/skills/github_collaboration.html
+++ b/docs/current/skills/github_collaboration.html
@@ -73,7 +73,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/docs/current/skills/github_solo.html b/docs/current/skills/github_solo.html
index 906edc9..608dcfe 100644
--- a/docs/current/skills/github_solo.html
+++ b/docs/current/skills/github_solo.html
@@ -73,7 +73,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script src="../site_libs/quarto-contrib/videojs/video.min.js"></script>
 <link href="../site_libs/quarto-contrib/videojs/video-js.css" rel="stylesheet">
 <script id="quarto-search-options" type="application/json">{
diff --git a/docs/current/skills/packaging.html b/docs/current/skills/packaging.html
index 8c3bdf7..a17763a 100644
--- a/docs/current/skills/packaging.html
+++ b/docs/current/skills/packaging.html
@@ -39,7 +39,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
@@ -302,10 +302,8 @@
     <h2 id="toc-title">Table of contents</h2>
    
   <ul>
-  <li><a href="#what-is-needed-for-package-management" id="toc-what-is-needed-for-package-management" class="nav-link active" data-scroll-target="#what-is-needed-for-package-management"><span class="header-section-number">24</span> What is needed for package management?</a>
-  <ul class="collapse">
-  <li><a href="#from-code-to-published-package-in-python" id="toc-from-code-to-published-package-in-python" class="nav-link" data-scroll-target="#from-code-to-published-package-in-python"><span class="header-section-number">24.1</span> From code to published package in Python</a></li>
-  </ul></li>
+  <li><a href="#what-is-needed-for-package-management" id="toc-what-is-needed-for-package-management" class="nav-link active" data-scroll-target="#what-is-needed-for-package-management"><span class="header-section-number">23.1</span> What is needed for package management?</a></li>
+  <li><a href="#from-code-to-published-package-in-python" id="toc-from-code-to-published-package-in-python" class="nav-link" data-scroll-target="#from-code-to-published-package-in-python"><span class="header-section-number">23.2</span> From code to published package in Python</a></li>
   </ul>
 <div class="toc-actions"><ul><li><a href="https://github.com/howisonlab/open_source_software_course/blob/master/quarto_course/skills/packaging.qmd" class="toc-action"><i class="bi bi-github"></i>View source</a></li></ul></div></nav>
     </div>
@@ -351,8 +349,8 @@ <h1 class="title"><span id="sec-packaging" class="quarto-section-identifier"><sp
 <li>Packages can provide an appropriate location for running tests</li>
 <li>Packages provide a way to scale up software. Data Scientists often develop code in a Notebook … which is very convenient for the analyst but not something that can be made into a web API which thousands of developers or products can use in real time. When we build packages they can be deployed in the cloud, and turned into <a href="https://en.wikipedia.org/wiki/Microservices">microservices</a> using services like Kubernetes.</li>
 </ul>
-<section id="what-is-needed-for-package-management" class="level1" data-number="24">
-<h1 data-number="24"><span class="header-section-number">24</span> What is needed for package management?</h1>
+<section id="what-is-needed-for-package-management" class="level2" data-number="23.1">
+<h2 data-number="23.1" class="anchored" data-anchor-id="what-is-needed-for-package-management"><span class="header-section-number">23.1</span> What is needed for package management?</h2>
 <p>Packaging can be thought about in four steps:</p>
 <ol type="1">
 <li>Encapsulating code in a chunk that can be moved around</li>
@@ -364,13 +362,13 @@ <h1 data-number="24"><span class="header-section-number">24</span> What is neede
 <p>In Python, for examples, Encapsulation is done with directories, which have files inside with the code (“regular” some_code_name.py files. Metadata is done with additional files inside the directories. The tool <code>pip</code> handles both installation and dependency resolution. For the server that hosts the packages there is one broad public server called <code>PyPI</code> (which stands for the <em>PY</em>thon <em>P</em>ackage <em>I</em>ndex), but it is also possible for individual organizations to run a version “behind the firewall” to manage packages within their organization.</p>
 <p>In R, encapsulation is also done thorugh directories, metadata through files. Package installation is done within the R base software. In R there are a few important central repositories, including CRAN (<em>C</em>omprehensive <em>R</em> <em>A</em>rchive <em>N</em>etwork) and Bioconductor (a separate package manager focused on biology packages, an example of convergent evolution). There are lots of different mirrors for CRAN.</p>
 <p>Package management “behind the firewall” is so important to firms, that the company that builds <code>Rstudio</code> now offers package management for both R and Python <a href="https://packagemanager.posit.co/client/#/" class="uri">https://packagemanager.posit.co/client/#/</a> both publically and within companies. Similarly <a href="https://www.anaconda.com/">Anaconda</a> a company based in Austin offers package management across an eve wider set of languages.</p>
-<section id="from-code-to-published-package-in-python" class="level2" data-number="24.1">
-<h2 data-number="24.1" class="anchored" data-anchor-id="from-code-to-published-package-in-python"><span class="header-section-number">24.1</span> From code to published package in Python</h2>
+</section>
+<section id="from-code-to-published-package-in-python" class="level2" data-number="23.2">
+<h2 data-number="23.2" class="anchored" data-anchor-id="from-code-to-published-package-in-python"><span class="header-section-number">23.2</span> From code to published package in Python</h2>
 <p>For these materials we will work through a Data Camp course (which you are welcome to finish), called <a href="https://campus.datacamp.com/courses/developing-python-packages">Developing Python Packages</a>.</p>
 <p>The course shows how to take code and wrap it in a directory with special files, then how to publish it to PyPI (using a special repository just for testing).</p>
 
 
-</section>
 </section>
 
 </main> <!-- /main -->
diff --git a/docs/current/skills/paper_planes_git.html b/docs/current/skills/paper_planes_git.html
index 573f759..0e499b5 100644
--- a/docs/current/skills/paper_planes_git.html
+++ b/docs/current/skills/paper_planes_git.html
@@ -39,7 +39,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/docs/current/skills/tests.html b/docs/current/skills/tests.html
index 60cede0..2e2e933 100644
--- a/docs/current/skills/tests.html
+++ b/docs/current/skills/tests.html
@@ -73,7 +73,7 @@
 <link href="../site_libs/quarto-html/quarto-syntax-highlighting-549806ee2085284f45b00abea8c6df48.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="../site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="../site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="../site_libs/bootstrap/bootstrap-854d42f42d0f6b455b86ad16a464e311.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
+<link href="../site_libs/bootstrap/bootstrap-f2151062440e71a1d76e61548d0dfb49.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
 <script id="quarto-search-options" type="application/json">{
   "location": "sidebar",
   "copy-button": false,
diff --git a/quarto_course/insights/governance.qmd b/quarto_course/insights/governance.qmd
index 6ef9310..570ab0b 100644
--- a/quarto_course/insights/governance.qmd
+++ b/quarto_course/insights/governance.qmd
@@ -15,7 +15,7 @@
 
 Extra optional reading: Podcast on "Learning from Open Source": <https://a16z.com/podcast/learning-from-open-source-communities/>.  We will have readings from this later in the course, so useful to do now.
 
-# How do open source projects make decisions? 
+## How do open source projects make decisions?
 
 Working in a project requires many decisions, e.g.,:
 
diff --git a/quarto_course/skills/git_cherrypick_split_pr.qmd b/quarto_course/skills/git_cherrypick_split_pr.qmd
index a435fcd..53f6987 100644
--- a/quarto_course/skills/git_cherrypick_split_pr.qmd
+++ b/quarto_course/skills/git_cherrypick_split_pr.qmd
@@ -63,11 +63,11 @@ gitGraph
   commit id: "orange2"
 ```
 
-### LearnGitBranching exercise
+## LearnGitBranching exercise
 
 We can see an example of the overall workflow for splitting a PR using the LearnGitBranching Visualizer, I have created a level called [Split Pull Request](https://learngitbranching.js.org/?gist_level_id=f7b4b63960ed80fa9a76728d853f2546).
 
-### Cherry-pick via commandline git
+## Cherry-pick via commandline git
 
 You can see a situation like this in this repo on GitHub. Bring that to your working space with:
 
@@ -164,13 +164,13 @@ And branches are just like little post-its added to some commits, they are just
 See more about this on the GitHub blog <https://github.blog/2020-12-17-commits-are-snapshots-not-diffs/>
 :::
 
-### Exercises
+## Exercises
 
-#### Individual Exercises
+### Individual Exercises
 
 1.  Now you work to get the `orange_branch` organized.
 
-#### Group Exercise
+### Group Exercise
 
 Groups of 3. Nominate *Maintainer*, *Contributor A*, and *Contributor B*.
 
diff --git a/quarto_course/skills/git_rebase.qmd b/quarto_course/skills/git_rebase.qmd
index 6955712..b6cad35 100644
--- a/quarto_course/skills/git_rebase.qmd
+++ b/quarto_course/skills/git_rebase.qmd
@@ -274,7 +274,7 @@ Ignore the remote branch (origin/pie_chart_branch), and focus only on the local
 
 Note that in these examples we did not encounter any conflicts (because edits were all on different files).  In reality, though, when commits are moved around, rebased, and squashed, sometimes those operations result in conflicts (just as happens with merge).  In that case git add the conflict symbols (`<<<<<<` and `==========` and `>>>>>>>>>`) which all need to be removed, then the files added and finally we run `git rebase --continue`.  Git does provide useful messages through that process with guidance on the likely next steps.
 
-# Rebase Exercise
+## Rebase Exercise
 
 In groups of three, a Maintainer and two contributors, begin by setting up the collaboration network (a new repo, forks, clones and setting upstream).  Then work together to implement these steps:
 
diff --git a/quarto_course/skills/packaging.qmd b/quarto_course/skills/packaging.qmd
index b4549d7..fd44440 100644
--- a/quarto_course/skills/packaging.qmd
+++ b/quarto_course/skills/packaging.qmd
@@ -25,7 +25,7 @@ Packages and package management offer a few other important advantages:
 - Packages can provide an appropriate location for running tests
 - Packages provide a way to scale up software. Data Scientists often develop code in a Notebook ... which is very convenient for the analyst but not something that can be made into a web API which thousands of developers or products can use in real time.  When we build packages they can be deployed in the cloud, and turned into [microservices](https://en.wikipedia.org/wiki/Microservices) using services like Kubernetes.
     
-# What is needed for package management?
+## What is needed for package management?
 
 Packaging can be thought about in four steps: