diff --git a/docs/index.md b/docs/index.md
index c256ab5ce..ed1d6743e 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -1160,7 +1160,7 @@ It("panics in a goroutine", func() {
 })
 ```
 
-You must remember follow this pattern when making assertions in goroutines - however, if uncaught, Ginkgo's panic will include a helpful error to remind you to add `defer GinkgoRecover()` to your goroutine.
+You must remember to follow this pattern when making assertions in goroutines - however, if uncaught, Ginkgo's panic will include a helpful error to remind you to add `defer GinkgoRecover()` to your goroutine.
 
 When a failure occurs Ginkgo marks the current spec as failed and moves on to the next spec.  If, however, you'd like to stop the entire suite when the first failure occurs you can run `ginkgo --fail-fast`.
 
@@ -4543,4 +4543,4 @@ There are a set of [completions](https://github.com/onsi/ginkgo-sublime-completi
 
 IDE authors can set the `GINKGO_EDITOR_INTEGRATION` environment variable to any non-empty value to enable coverage to be displayed for focused specs. By default, Ginkgo will fail with a non-zero exit code if specs are focused to ensure they do not pass in CI.
 
-{% endraw  %}
\ No newline at end of file
+{% endraw  %}