Publish refs/heads/master

linux-kernel-labs · Apr 10, 2024 · d78b056 · d78b056
1 parent a29a931
commit d78b056
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/refs/heads/master/_sources/so2/assign-collaboration.rst.txt b/refs/heads/master/_sources/so2/assign-collaboration.rst.txt
@@ -121,7 +121,7 @@ Follow the seven rules of writing a good commit message: https://cbea.ms/git-com
 Add `TODOs` with each team member tasks. Try to split the work evenly.
 
 Before starting to code, make a plan. On top of your skeleton file, add TODOs with each member tasks. Agree on global
-structures and the overlall driver design. Then start coding.
+structures and the overall driver design. Then start coding.
 
 5. Do reviews
 -------------

diff --git a/refs/heads/master/searchindex.js b/refs/heads/master/searchindex.js
diff --git a/refs/heads/master/so2/assign-collaboration.html b/refs/heads/master/so2/assign-collaboration.html
@@ -277,7 +277,7 @@ <h2>3. Add a commit for each individual change<a class="headerlink" href="#add-a
 <h2>4. Split the work inside the team<a class="headerlink" href="#split-the-work-inside-the-team" title="Permalink to this headline">¶</a></h2>
 <p>Add <cite>TODOs</cite> with each team member tasks. Try to split the work evenly.</p>
 <p>Before starting to code, make a plan. On top of your skeleton file, add TODOs with each member tasks. Agree on global
-structures and the overlall driver design. Then start coding.</p>
+structures and the overall driver design. Then start coding.</p>
 </div>
 <div class="section" id="do-reviews">
 <h2>5. Do reviews<a class="headerlink" href="#do-reviews" title="Permalink to this headline">¶</a></h2>