summaryrefslogtreecommitdiffstats
path: root/crawl-ref/docs
diff options
context:
space:
mode:
Diffstat (limited to 'crawl-ref/docs')
-rw-r--r--crawl-ref/docs/aptitudes.txt2
-rw-r--r--crawl-ref/docs/patch_guide.txt4
2 files changed, 3 insertions, 3 deletions
diff --git a/crawl-ref/docs/aptitudes.txt b/crawl-ref/docs/aptitudes.txt
index 20e08a1c35..2751ae4c02 100644
--- a/crawl-ref/docs/aptitudes.txt
+++ b/crawl-ref/docs/aptitudes.txt
@@ -12,7 +12,7 @@ If you consider figuring out such things yourself to be fun, stop reading
now. Otherwise, just go ahead. The lower a value, the better the aptitude.
100 is the Human standard. Please note that many things affect how quick a
character will actually learn a skill. Thus the numbers below are good
-enough for comparisons among specis, but not necessarily among skills.
+enough for comparisons among species, but not necessarily among skills.
The abbreviations used for the skills are:
diff --git a/crawl-ref/docs/patch_guide.txt b/crawl-ref/docs/patch_guide.txt
index 34679dff84..2ecc4fab2e 100644
--- a/crawl-ref/docs/patch_guide.txt
+++ b/crawl-ref/docs/patch_guide.txt
@@ -125,9 +125,9 @@ out, so I grep the source (*.h and *.cc) for all occurences and have a look
at all files this turns up. And so on.
Evaluating and prioritising the findings takes some experience with the source
-code but even if you have no idea what the files are likely to contain using
+code but even if you have no idea what the files are likely to contain, using
grep still greatly reduces the number of files you have to look at. To find
-the code you're interested in search the files for the same keyword you used
+the code you're interested in, search the files for the same keyword you used
for grepping.
Good luck with your patch! If you have any questions, don't hesitate to ask.