summaryrefslogtreecommitdiffstats
path: root/crawl-ref/docs/patch_guide.txt
diff options
context:
space:
mode:
authorj-p-e-g <j-p-e-g@c06c8d41-db1a-0410-9941-cceddc491573>2009-07-28 22:38:25 +0000
committerj-p-e-g <j-p-e-g@c06c8d41-db1a-0410-9941-cceddc491573>2009-07-28 22:38:25 +0000
commit771896e7091c766da22380885247f13d094096c0 (patch)
treefee8b13ef2e2da2e7f29d39f125da8fe4e1681ce /crawl-ref/docs/patch_guide.txt
parent410ce3feb72d7c7635d884749bcc31736225d1e9 (diff)
downloadcrawl-ref-771896e7091c766da22380885247f13d094096c0.tar.gz
crawl-ref-771896e7091c766da22380885247f13d094096c0.zip
Tweak some docs, and add Airstrike to the list of spells that don't
require a range check. git-svn-id: https://crawl-ref.svn.sourceforge.net/svnroot/crawl-ref/branches/stone_soup-0.5@10458 c06c8d41-db1a-0410-9941-cceddc491573
Diffstat (limited to 'crawl-ref/docs/patch_guide.txt')
-rw-r--r--crawl-ref/docs/patch_guide.txt4
1 files changed, 2 insertions, 2 deletions
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.