diff --git a/TestingGuidelines.wiki b/TestingGuidelines.wiki
index af3f453..d008693 100644
--- a/TestingGuidelines.wiki
+++ b/TestingGuidelines.wiki
@@ -109,7 +109,7 @@
 Any non-trivial change requires an accompanying test, in the same patch as
 the proposed change.  These guidelines need to be followed:
 
- * There should be always be a test whenever adding new behavior or changing existing behavior in any way (and the test code should be in the same [ContributionReviews#Patches patch] as the code change).
+ * There should always be a test whenever adding new behavior or changing existing behavior in any way (and the test code should be in the same [ContributionReviews#Patches patch] as the code change).
  * Refactorings do not require new tests, so long as the code being refactored is already covered by tests (and those tests pass after the refactoring). Refactorings should make no non-trivial changes to tests, since the tests are instrumental in validating that the refactoring did not break anything.
  * Emergency patches (perhaps quick fixes by the release packager) do not require tests immediately, but a test should be included in a new patch accompanying the follow-up [ContributionReviews#Patches code review].
  * You need to add tests if changing a section of code that does not currently have them.
@@ -118,7 +118,7 @@
 
 All patches should pass the [TestingGuidelines#Smoke_tests smoke test suite]
 before being submitted for review.  So as not to waste other contributors'
-time, please insure that the smoke tests pass before requesting a code
+time, please ensure that the smoke tests pass before requesting a code
 review of a patch, and after any `svn update` or `svn merge` that might
 change the code being
 [ContributionReviews#Branches reviewed in a development branch].
@@ -142,7 +142,7 @@
 continuous build is up and running, this will be checked manually by having
 the release packager run the test suites explicitly.)
 
-== No nondeterministic tests ==
+== No non-deterministic tests ==
 
 Please do not allow any non-deterministic tests to be added to the test
 suites, and please fix any tests that are detected to be non-deterministic
@@ -174,7 +174,7 @@
 
 A long-term goal is the ability to acquire automated test coverage.  Tools
 exist for measuring test coverage of Python code.  At some point, these will
-be incorporated into a Melange continous build.
+be incorporated into a Melange continuous build.
 
 ----
 _Copyright 2008 Google Inc._