Merge branch 'gh-pages' into 1421-docs-clean

Author: ShubhamOulkar

_includes/api/en/4x/app-use.md

@@ -79,7 +79,8 @@ mounting middleware.
 <tr>
 <td>Path</td>
 <td markdown="1">
-This will match paths starting with `/abcd`:
+Matches the exact path `/abcd` and any sub-paths starting with `/abcd/` (for example, `/abcd/foo`):
+
 
 ```js
 app.use('/abcd', function (req, res, next) {

_includes/api/en/4x/res-clearCookie.md

@@ -1,6 +1,14 @@
 <h3 id='res.clearCookie'>res.clearCookie(name [, options])</h3>
 
-Clears the cookie specified by `name`. For details about the `options` object, see [res.cookie()](#res.cookie).
+Clears the cookie with the specified `name` by sending a `Set-Cookie` header that sets its expiration date in the past.
+This instructs the client that the cookie has expired and is no longer valid. For more information
+about available `options`, see [res.cookie()](#res.cookie).
+
+<div class="doc-box doc-warn" markdown="1">
+If the `maxAge` or `expires` options are set, the cookie may not be cleared depending on the time values provided,
+as Express does not ignore these options. It is therefore recommended to omit these options when calling this
+method. Passing these two options has been deprecated since Express v4.20.0.
+</div>
 
 <div class="doc-box doc-notice" markdown="1">
 Web browsers and other compliant clients will only clear the cookie if the given

_includes/api/en/5x/app-use.md

@@ -80,7 +80,8 @@ mounting middleware.
 <tr>
 <td>Path</td>
 <td markdown="1">
-This will match paths starting with `/abcd`:
+Matches the exact path `/abcd` and any sub-paths starting with `/abcd/` (for example, `/abcd/foo`):
+
 
 ```js
 app.use('/abcd', (req, res, next) => {

_includes/api/en/5x/res-clearCookie.md

@@ -1,11 +1,16 @@
 <h3 id='res.clearCookie'>res.clearCookie(name [, options])</h3>
 
-Clears the cookie specified by `name`. For details about the `options` object, see [res.cookie()](#res.cookie).
+Clears the cookie with the specified `name` by sending a `Set-Cookie` header that sets its expiration date in the past.
+This instructs the client that the cookie has expired and is no longer valid. For more information
+about available `options`, see [res.cookie()](#res.cookie).
+
+<div class="doc-box doc-notice" markdown="1">
+The `expires` and `max-age` options are being ignored completely.
+</div>
 
 <div class="doc-box doc-notice" markdown="1">
 Web browsers and other compliant clients will only clear the cookie if the given
-`options` is identical to those given to [res.cookie()](#res.cookie), excluding
-`expires` and `maxAge`.
+`options` is identical to those given to [res.cookie()](#res.cookie)
 </div>
 
 ```js

_includes/head.html

@@ -4,14 +4,14 @@
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link 
         rel="preload" 
-        href="/fonts/open-sans/woff2/OpenSans.woff2"
+        href="/fonts/open-sans/woff2/open-sans-latin-wght-normal.woff2"
         as="font" 
         type="font/woff2" 
         crossorigin 
     />
     <link 
         rel="preload" 
-        href="/fonts/open-sans/woff2/OpenSans-Italic.woff2" 
+        href="/fonts/open-sans/woff2/open-sans-latin-wght-italic.woff2" 
         as="font" 
         type="font/woff2" 
         crossorigin 

en/guide/using-middleware.md

@@ -10,7 +10,7 @@ redirect_from: "/guide/using-middleware.html"
 
 Express is a routing and middleware web framework that has minimal functionality of its own: An Express application is essentially a series of middleware function calls.
 
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/4x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/4x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
+_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
 
 Middleware functions can perform the following tasks:
 
@@ -34,7 +34,7 @@ You can also load a series of middleware functions together, which creates a sub
 
 <h2 id='middleware.application'>Application-level middleware</h2>
 
-Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/4x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
+Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
 
 This example shows a middleware function with no mount path. The function is executed every time the app receives a request.
 
@@ -249,9 +249,9 @@ functions that were previously included with Express are now in separate modules
 
 Express has the following built-in middleware functions:
 
-- [express.static](/en/4x/api.html#express.static) serves static assets such as HTML files, images, and so on.
-- [express.json](/en/4x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
-- [express.urlencoded](/en/4x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
+- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
+- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
+- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
 
 <h2 id='middleware.third-party'>Third-party middleware</h2>