diff --git a/_includes/api/en/4x/express.json.md b/_includes/api/en/4x/express.json.md
index ffc460193d..70f0b7cbe2 100644
--- a/_includes/api/en/4x/express.json.md
+++ b/_includes/api/en/4x/express.json.md
@@ -39,4 +39,4 @@ The following table describes the properties of the optional `options` object.
| `type` | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `json`), a mime type (like `application/json`), or a mime type with a wildcard (like `*/*` or `*/json`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed | `"application/json"` |
| `verify` | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error. | Function | `undefined` |
-
\ No newline at end of file
+
diff --git a/_includes/api/en/4x/express.static.md b/_includes/api/en/4x/express.static.md
index b92c2d7b36..4b532ca652 100644
--- a/_includes/api/en/4x/express.static.md
+++ b/_includes/api/en/4x/express.static.md
@@ -93,3 +93,4 @@ var options = {
app.use(express.static('public', options))
```
+
diff --git a/en/guide/using-middleware.md b/en/guide/using-middleware.md
index ad5b80ca25..5115484bb6 100644
--- a/en/guide/using-middleware.md
+++ b/en/guide/using-middleware.md
@@ -253,6 +253,18 @@ Express has the following built-in middleware functions:
- [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+**
+Here is an example of using the `express.json` middleware with a custom limit:
+
+```js
+const express = require('express')
+const app = express()
+
+// Apply a 5MB limit for /upload requests
+app.use('/upload', express.json({ limit: '5mb' }))
+
+// Use default limit for all other routes
+app.use(express.json())
+```
Third-party middleware
Use third-party middleware to add functionality to Express apps.
diff --git a/zh-tw/guide/using-middleware.md b/zh-tw/guide/using-middleware.md
index 95a92eb0e9..0a76226b94 100644
--- a/zh-tw/guide/using-middleware.md
+++ b/zh-tw/guide/using-middleware.md
@@ -36,67 +36,6 @@ You can also load a series of middleware functions together, which creates a sub
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.
-
-```js
-const express = require('express')
-const app = express()
-
-app.use((req, res, next) => {
- console.log('Time:', Date.now())
- next()
-})
-```
-
-This example shows a middleware function mounted on the `/user/:id` path. The function is executed for any type of
-HTTP request on the `/user/:id` path.
-
-```js
-app.use('/user/:id', (req, res, next) => {
- console.log('Request Type:', req.method)
- next()
-})
-```
-
-This example shows a route and its handler function (middleware system). The function handles GET requests to the `/user/:id` path.
-
-```js
-app.get('/user/:id', (req, res, next) => {
- res.send('USER')
-})
-```
-
-Here is an example of loading a series of middleware functions at a mount point, with a mount path.
-It illustrates a middleware sub-stack that prints request info for any type of HTTP request to the `/user/:id` path.
-
-```js
-app.use('/user/:id', (req, res, next) => {
- console.log('Request URL:', req.originalUrl)
- next()
-}, (req, res, next) => {
- console.log('Request Type:', req.method)
- next()
-})
-```
-
-Route handlers enable you to define multiple routes for a path. The example below defines two routes for GET requests to the `/user/:id` path. The second route will not cause any problems, but it will never get called because the first route ends the request-response cycle.
-
-本例顯示中介軟體子堆疊,它處理了指向 `/user/:id` 路徑的 GET 要求。
-
-```js
-app.get('/user/:id', (req, res, next) => {
- console.log('ID:', req.params.id)
- next()
-}, (req, res, next) => {
- res.send('User Info')
-})
-
-// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', (req, res, next) => {
- res.send(req.params.id)
-})
-```
-
To skip the rest of the middleware functions from a router middleware stack, call `next('route')` to pass control to the next route.
{% capture next-function %}