Fix typos

algonell · algonell · commit 7251307b70fa · 2024-10-07T00:39:18.000+03:00
diff --git a/SoC-2014-Microprojects.md b/SoC-2014-Microprojects.md
@@ -28,7 +28,7 @@ and the implementation of that design were all reviewed and discussed,
 and after several iterations an improved version of the patch was
 accepted into our codebase.  As a GSoC student, you will be playing
 the role of the developer and engaging in a similar discussion.  Get
-familar with the flow, need for clarity on both sides (i.e. you need
+familiar with the flow, need for clarity on both sides (i.e. you need
 to clearly defend your design, and need to ask clarifications when
 questions/suggestions you are offered are not clear enough), the pace
 at which the discussion takes place, and the general tone of the
diff --git a/SoC-2015-Ideas.md b/SoC-2015-Ideas.md
@@ -77,7 +77,7 @@ look for the commit which fixed a bug. It is already possible using
 "git bisect", but the user has to type "good" to mean "the bug is
 there" and "bad" to mean "the bug is fixed", which isn't convenient.
 
-It would be nice to allow the user to explicitely say "git bisect
+It would be nice to allow the user to explicitly say "git bisect
 fixed" and "git bisect unfixed" instead. It is actually much harder
 than defining "fixed"/"unfixed" as aliases for "bad"/"good".
 
diff --git a/SoC-2015-Microprojects.md b/SoC-2015-Microprojects.md
@@ -28,7 +28,7 @@ and the implementation of that design were all reviewed and discussed,
 and after several iterations an improved version of the patch was
 accepted into our codebase.  As a GSoC student, you will be playing
 the role of the developer and engaging in a similar discussion.  Get
-familar with the flow, need for clarity on both sides (i.e. you need
+familiar with the flow, need for clarity on both sides (i.e. you need
 to clearly defend your design, and need to ask clarifications when
 questions/suggestions you are offered are not clear enough), the pace
 at which the discussion takes place, and the general tone of the
diff --git a/SoC-2016-Ideas.md b/SoC-2016-Ideas.md
@@ -267,7 +267,7 @@ compressed data from one packfile to another.
 
 This would involve looking at the code in git to copy over
 optimisations as well as figuring out what parts of libgit2 should be
-changed to accomodate these new capabilities.
+changed to accommodate these new capabilities.
 
 - Language: C
 - Difficulty: medium
diff --git a/SoC-2016-Microprojects.md b/SoC-2016-Microprojects.md
@@ -40,7 +40,7 @@ and the implementation of that design were all reviewed and discussed,
 and after several iterations an improved version of the patch was
 accepted into our codebase.  As a GSoC student, you will be playing
 the role of the developer and engaging in a similar discussion.  Get
-familar with the flow, need for clarity on both sides (i.e. you need
+familiar with the flow, need for clarity on both sides (i.e. you need
 to clearly defend your design, and need to ask clarifications when
 questions/suggestions you are offered are not clear enough), the pace
 at which the discussion takes place, and the general tone of the
@@ -272,7 +272,7 @@ When you find something you are interested to work on, please ask
 first on the mailing list if it's worth doing and if it's appropriate
 for a microproject before starting to work on what you find. Even if
 it looks straitforward, there could be hidden reasons why it is too
-difficult or just innappropriate.
+difficult or just inappropriate.
 
 ### Searching the code base itself
 
diff --git a/SoC-2017-Microprojects.md b/SoC-2017-Microprojects.md
@@ -33,7 +33,7 @@ and the implementation of that design were all reviewed and discussed,
 and after several iterations an improved version of the patch was
 accepted into our codebase.  As a GSoC student, you will be playing
 the role of the developer and engaging in a similar discussion.  Get
-familar with the flow, need for clarity on both sides (i.e. you need
+familiar with the flow, need for clarity on both sides (i.e. you need
 to clearly defend your design, and need to ask clarifications when
 questions/suggestions you are offered are not clear enough), the pace
 at which the discussion takes place, and the general tone of the
@@ -262,7 +262,7 @@ When you find something you are interested to work on, please ask
 first on the mailing list if it's worth doing and if it's appropriate
 for a microproject before starting to work on what you find. Even if
 it looks straitforward, there could be hidden reasons why it is too
-difficult or just innappropriate.
+difficult or just inappropriate.
 
 ### Searching the code base itself
 
diff --git a/SoC-2018-Microprojects.md b/SoC-2018-Microprojects.md
@@ -33,7 +33,7 @@ and the implementation of that design were all reviewed and discussed,
 and after several iterations an improved version of the patch was
 accepted into our codebase.  As a GSoC student, you will be playing
 the role of the developer and engaging in a similar discussion.  Get
-familar with the flow, need for clarity on both sides (i.e. you need
+familiar with the flow, need for clarity on both sides (i.e. you need
 to clearly defend your design, and need to ask clarifications when
 questions/suggestions you are offered are not clear enough), the pace
 at which the discussion takes place, and the general tone of the
diff --git a/SoC-2019-Ideas.md b/SoC-2019-Ideas.md
@@ -120,7 +120,7 @@ projects versus projects that implement new features though.
 Git has an old problem of duplicated implementations of some
 logic. For example, Git had at least 4 different implementations to
 format command output for different commands. Our previous GSoC
-students and Outreachy interns unified some of the formating logic
+students and Outreachy interns unified some of the formatting logic
 into [ref-filter](https://github.com/git/git/blob/master/ref-filter.h)
 and got rid of similar logic in some command specific files. Current
 task is to continue this work and reuse ref-filter formatting logic in
diff --git a/SoC-2019-Microprojects.md b/SoC-2019-Microprojects.md
@@ -33,7 +33,7 @@ and the implementation of that design were all reviewed and discussed,
 and after several iterations an improved version of the patch was
 accepted into our codebase.  As a GSoC student, you will be playing
 the role of the developer and engaging in a similar discussion.  Get
-familar with the flow, need for clarity on both sides (i.e. you need
+familiar with the flow, need for clarity on both sides (i.e. you need
 to clearly defend your design, and need to ask clarifications when
 questions/suggestions you are offered are not clear enough), the pace
 at which the discussion takes place, and the general tone of the
diff --git a/SoC-2020-Ideas.md b/SoC-2020-Ideas.md
@@ -27,7 +27,7 @@ page though.
 Git has an old problem of duplicated implementations of some
 logic. For example, Git had at least 4 different implementations to
 format command output for different commands. Our previous GSoC
-students and Outreachy interns unified some of the formating logic
+students and Outreachy interns unified some of the formatting logic
 into [ref-filter](https://github.com/git/git/blob/master/ref-filter.h)
 and got rid of similar logic in some command specific files. Current
 task is to continue this work and reuse ref-filter formatting logic in
diff --git a/SoC-2021-Ideas.md b/SoC-2021-Ideas.md
@@ -32,7 +32,7 @@ possible the same code and syntax as the ref-filter formats.
 Git used to have an old problem of duplicated implementations of some
 logic. For example, Git had at least 4 different implementations to
 format command output for different commands. Our previous GSoC
-students and Outreachy interns unified some of the formating logic
+students and Outreachy interns unified some of the formatting logic
 into [ref-filter](https://github.com/git/git/blob/master/ref-filter.h)
 and got rid of similar logic in some command specific files.
 
diff --git a/SoC-2022-Ideas.md b/SoC-2022-Ideas.md
@@ -83,7 +83,7 @@ logic. For example, Git had at least 4 different implementations to
 format command output for different commands.
 
 Our previous GSoC students and Outreachy interns unified some of the
-formating logic into
+formatting logic into
 [ref-filter](https://github.com/git/git/blob/master/ref-filter.h) and
 got rid of similar logic in some command specific files. Current task
 is to continue this work and reuse ref-filter formatting logic in
diff --git a/SoC-2023-Ideas.md b/SoC-2023-Ideas.md
@@ -77,7 +77,7 @@ logic. For example, Git had at least 4 different implementations to
 format command output for different commands.
 
 Our previous GSoC students and Outreachy interns unified some of the
-formating logic into
+formatting logic into
 [ref-filter](https://github.com/git/git/blob/master/ref-filter.h) and
 got rid of similar logic in some command specific files. Current task
 is to continue this work and reuse ref-filter formatting logic in
