fixup: address review comments

Author: gireeshpunathil

_includes/api/en/5x/req-query.md

@@ -1,7 +1,7 @@
 <h3 id='req.query'>req.query</h3>
 
 This property is an object containing a property for each query string parameter in the route.
-When disabled, the `req.query` will be an empty object (`{}`). Else, the result of configured query parser.
+When [`query parser`](#app.settings.table) is set to disabled, it is an empty object `{}`, otherwise it is the result of the configured query parser.
 
 <div class="doc-box doc-warn" markdown="1">
 As `req.query`'s shape is based on user-controlled input, all properties and values in this object are untrusted and should be validated before trusting. For example, `req.query.foo.toString()` may fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString` may not be a function and instead a string or other user-input.
@@ -26,3 +26,5 @@ console.dir(req.query.shoe.type)
 console.dir(req.query.color)
 // => [blue, black, red]
 ```
+
+{% include api/en/5x/app-settings.md %}

en/guide/migrating-5.md

@@ -124,8 +124,6 @@ In Express 4, the `req.host` function incorrectly stripped off the port number i
 
 In Express 4.7 and Express 5 onwards, the query parser option can accept `false` to disable query string parsing when you want to use your own function for query string parsing logic.
 
-When disabled, the `req.query` will be an empty object (`{}`). Else, the result of configured query parser.
-
 <h3>Improvements</h3>
 
 <h4 id="res.render">res.render()</h4>