diff --git a/docs/getting-started/2-javascript-and-gulpfiles.md b/docs/getting-started/2-javascript-and-gulpfiles.md
index b82193f33..6ccc8161a 100644
--- a/docs/getting-started/2-javascript-and-gulpfiles.md
+++ b/docs/getting-started/2-javascript-and-gulpfiles.md
@@ -28,8 +28,7 @@ Many users start by adding all logic to a gulpfile. If it ever grows too big, it
 
 Each task can be split into its own file, then imported into your gulpfile for composition. Not only does this keep things organized, but it allows you to test each task independently or vary composition based on conditions.
 
-Node's module resolution allows you to replace your `gulpfile.js` with a directory called `gulpfile` that contains an `index.js` file which is treated as a `gulpfile.js`.  This directory could then contain your individual modules for tasks.
-
+Node's module resolution allows you to replace your `gulpfile.js` file with a directory named `gulpfile.js` that contains an `index.js` file which is treated as a `gulpfile.js`. This directory could then contain your individual modules for tasks.
 
 [gulpfile-transpilation-advanced]: ../documentation-missing.md
 [ts-node-module]: https://www.npmjs.com/package/ts-node