diff --git a/doc/api/addons.md b/doc/api/addons.md
index 41b0fe31d301e3..08172a9ae9c51f 100644
--- a/doc/api/addons.md
+++ b/doc/api/addons.md
@@ -845,8 +845,8 @@ class MyObject : public node::ObjectWrap {
 ```
 
 In `myobject.cc`, implement the various methods that are to be exposed.
-Below, the method `plusOne()` is exposed by adding it to the constructor's
-prototype:
+In the following code, the method `plusOne()` is exposed by adding it to the
+constructor's prototype:
 
 ```cpp
 // myobject.cc
diff --git a/doc/api/modules.md b/doc/api/modules.md
index cbcdec7e870e7c..0de496debc09a2 100644
--- a/doc/api/modules.md
+++ b/doc/api/modules.md
@@ -42,7 +42,8 @@ In this example, the variable `PI` is private to `circle.js`.
 The `module.exports` property can be assigned a new value (such as a function
 or object).
 
-Below, `bar.js` makes use of the `square` module, which exports a Square class:
+In the following code, `bar.js` makes use of the `square` module, which exports
+a Square class:
 
 ```js
 const Square = require('./square.js');
@@ -123,7 +124,7 @@ enough to support reasonable directory structures. Package manager programs
 such as `dpkg`, `rpm`, and `npm` will hopefully find it possible to build
 native packages from Node.js modules without modification.
 
-Below we give a suggested directory structure that could work:
+In the following, we give a suggested directory structure that could work:
 
 Let's say that we wanted to have the folder at
 `/usr/lib/node/<some-package>/<some-version>` hold the contents of a