diff --git a/pages/docs/manual/latest/interop-with-js-build-systems.mdx b/pages/docs/manual/latest/interop-with-js-build-systems.mdx
index 958614838..e043504b9 100644
--- a/pages/docs/manual/latest/interop-with-js-build-systems.mdx
+++ b/pages/docs/manual/latest/interop-with-js-build-systems.mdx
@@ -14,7 +14,7 @@ If you come from JS, chances are that you already have a build system in your ex
 
 The JS ecosystem uses a few build systems: [browserify](http://browserify.org/), [rollup](https://github.com/rollup/rollup), [webpack](https://webpack.js.org/), etc. The latter's probably the most popular of the three (as of 2019 =P). These build systems do both the compilation and the linking (aka, bundling many files into one or few files).
 
-`rescript` only take care of the compilation step; it maps one `.res`/`.resi` file into one JS output file. As such, in theory, no build system integration is needed from our side. From e.g. the webpack watcher's perspective, the JS files ReScript generates are almost equivalent to your hand-written JS files. We also recommend **that you initially check in those ReScript-generated JS files**, as this workflow means:
+`rescript` only takes care of the compilation step; it maps one `.res`/`.resi` file into one JS output file. As such, in theory, no build system integration is needed from our side. From e.g. the webpack watcher's perspective, the JS files ReScript generates are almost equivalent to your hand-written JS files. We also recommend **that you initially check in those ReScript-generated JS files**, as this workflow means:
 
 - You can introduce ReScript silently into your codebase without disturbing existing infra.
 - You have a **visual** diff of the performance & correctness of your JS file when you update the `.res` files and the JS artifacts change.