From 467747d55f9fa38bfdacc7908dd396859206f2d7 Mon Sep 17 00:00:00 2001 From: Rob Morgan Date: Mon, 11 Apr 2011 12:24:38 +0800 Subject: Fixing typos in the README.md file --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 17b38de6c..dfc3b9af5 100644 --- a/README.md +++ b/README.md @@ -63,7 +63,7 @@ As the source code is handled by the version control system Git, it's useful to ### Submodules ### -The repository uses submodules, which normally are handles directly by the Makefile, but sometimes you want to +The repository uses submodules, which normally are handled directly by the Makefile, but sometimes you want to be able to work with them manually. Following are the steps to manually get the submodules: @@ -86,7 +86,7 @@ If you want to work inside a submodule, it is possible, but first you need to ch 1. `cd src/sizzle` 2. `git checkout master` -After you've commited your changes to the submodule, you'll update the jquery project to point to the new commit, +After you've committed your changes to the submodule, you'll update the jquery project to point to the new commit, but remember to push the submodule changes before pushing the new jquery commit: 1. `cd src/sizzle` @@ -99,12 +99,12 @@ The makefile has some targets to simplify submodule handling: #### `make update_submodules` #### -checks out the commit pointed to byu jquery, but merges your local changes, if any. This target is executed +checks out the commit pointed to by jquery, but merges your local changes, if any. This target is executed when you are doing a normal `make`. #### `make pull_submodules` #### -updates the content of the submoduels to what is probably the latest upstream code +updates the content of the submodules to what is probably the latest upstream code #### `make pull` #### -- cgit v1.2.3