gitstats: Ran ispell on all non gitstats-* files in doc/

The same should be done for all the gitstats-* files in the
doc/ directory as well.

diff --git a/doc/metrics.txt b/doc/metrics.txt
index ce4d958..f1b17ea 100644 (file)
--- a/doc/metrics.txt
+++ b/doc/metrics.txt
@@ -8,7 +8,7 @@ The following metrics will be used to determine if something is a fix:
   there has to be a lower limit (say, the 'creation point'
   of the branch) from where on commits are seen as 'part of
   the maintenance branch'. This means that we need a
-  mechanism to determine whether a commic belongs on a
+  mechanism to determine whether a commit belongs on a
   branch or not. This can be done by determining how
   'diluted' the commit is at the head of a branch. Here we
   define 'diluting' as merging, if a commit is part of a
@@ -71,7 +71,7 @@ The following metrics will be used to determine if something is a fix:
   commit was a mistake, and as such the reverting commit is
   a fix. By first checking which commits touch the same
   files the commits that have to be checked can be reduced
-  to a feasable amount.
+  to a feasible amount.
 
 * If a commit touches nearly all the same lines as another commit
   

diff --git a/doc/use-cases.txt b/doc/use-cases.txt
index 3ce8219..660296e 100644 (file)
--- a/doc/use-cases.txt
+++ b/doc/use-cases.txt
@@ -26,8 +26,8 @@ cases. When referenced are made to a Contributor addressing another
 Contributor to adjust their behavior as the result of data mined, it
 should be kept in mind that the Contributor should foremost be the one 
 to do this. Using this information to, say, spend more time checking 
-one's own commits for bugs when working on a specific part of the 
-content on one's own accord is is often more effective then doing
+ones own commits for bugs when working on a specific part of the
+content on ones own accord is is often more effective then doing
 so only after being asked. </disclaimer>? :P
  
 Name: Finding a Contributor that is active in a specific bit of content.