Merge pull request #734 from algonell/master

Fix typos

Author: chriscool

General-Application-Information.md

@@ -247,7 +247,7 @@ earlier than you. This means that you might have to find a project
 idea that we haven't proposed in our idea list.
 
 The good side of this is that this project idea along with your
-enthousiasm for it and the skills you show might encourage Git
+enthusiasm for it and the skills you show might encourage Git
 developers to mentor you even if they weren't planning to mentor in
 the first place. It could also happen that someone, who was only
 planning to co-mentor, could agree to fully mentor you alone.

General-Microproject-Information.md

@@ -50,7 +50,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 contributor, or Outreachy intern,
 you will be playing the role of the developer and engaging in a
-similar discussion. Get familar with the flow, need for clarity on
+similar discussion. Get familiar with the flow, need for clarity on
 both sides (i.e. you need to clearly explain your design, and need to
 ask for clarifications when questions/suggestions you are offered are
 not clear enough), the pace at which the discussion takes place, and

Hacking-Git.md

@@ -62,9 +62,9 @@ suggest improvements. Thanks!
 
 * [Sending patches by email with git](https://flusp.ime.usp.br/git/sending-patches-by-email-with-git/) is Matheus' git send-email tutorial.
 
-* [lore.kernel.org/git](https://lore.kernel.org/git/) is our prefered mailing list archive.
+* [lore.kernel.org/git](https://lore.kernel.org/git/) is our preferred mailing list archive.
 
-* [public-inbox](https://public-inbox.org/README.html) is the software behing lore.kernel.org.
+* [public-inbox](https://public-inbox.org/README.html) is the software behind lore.kernel.org.
 
 * [lore+lei](https://people.kernel.org/monsieuricon/lore-lei-part-1-getting-started) helps take advantage of lore/public-inbox.
 

Outreachy-21-Microprojects.md

@@ -89,6 +89,6 @@ untracked file in the submodule directory.  This is inconsistent with
 what `git describe --dirty` says when run in the submodule directory in
 that state.
 
-Fix `git diff` to use the same definition of dirtyness for such a
+Fix `git diff` to use the same definition of dirtiness for such a
 submodule directory (or the other way around).
 [[cf](https://lore.kernel.org/git/[email protected])]

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

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".
 

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

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

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
 

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