fix: unrecognized language

Author: ArthurFlag

content/contribute/components/code-blocks.md

@@ -13,7 +13,7 @@ we use often.
 If your example contains a placeholder value that's subject to change,
 use the format `<[A-Z_]+>` for the placeholder value: `<MY_VARIABLE>`
 
-```none
+```text
 export name=<MY_NAME>
 ```
 

content/manuals/engine/daemon/troubleshoot.md

@@ -545,7 +545,7 @@ all other running containers as filesystems within the container which mounts
 `/var/lib/docker/`. When you attempt to remove any of these containers, the
 removal attempt may fail with an error like the following:
 
-```none
+```text
 Error: Unable to remove filesystem for
 74bef250361c7817bee19349c93139621b272bc8f654ae112dd4eb9652af9515:
 remove /var/lib/docker/containers/74bef250361c7817bee19349c93139621b272bc8f654ae112dd4eb9652af9515/shm:

content/manuals/engine/install/linux-postinstall.md

@@ -78,7 +78,7 @@ To create the `docker` group and add your user:
    If you initially ran Docker CLI commands using `sudo` before adding your user
    to the `docker` group, you may see the following error:
 
-   ```none
+   ```text
    WARNING: Error loading config file: /home/user/.docker/config.json -
    stat /home/user/.docker/config.json: permission denied
    ```

content/manuals/engine/logging/drivers/syslog.md

@@ -22,7 +22,7 @@ receiver can extract the following information:
 The format is defined in [RFC 5424](https://tools.ietf.org/html/rfc5424) and Docker's syslog driver implements the
 [ABNF reference](https://tools.ietf.org/html/rfc5424#section-6) in the following way:
 
-```none
+```text
                 TIMESTAMP SP HOSTNAME SP APP-NAME SP PROCID SP MSGID
                     +          +             +           |        +
                     |          |             |           |        |

content/manuals/engine/logging/log_tags.md

@@ -30,7 +30,7 @@ Docker supports some special template markup you can use when specifying a tag's
 
 For example, specifying a `--log-opt tag="{{.ImageName}}/{{.Name}}/{{.ID}}"` value yields `syslog` log lines like:
 
-```none
+```text
 Aug  7 18:33:19 HOSTNAME hello-world/foobar/5790672ab6a0[9103]: Hello from Docker.
 ```
 

content/manuals/engine/release-notes/prior-releases.md

@@ -328,7 +328,7 @@ If you are currently using the `--ipv6` option _without_ specifying the
 `--fixed-cidr-v6` option, the Docker daemon will refuse to start with the
 following message:
 
-```none
+```text
 Error starting daemon: Error initializing network controller: Error creating
                        default "bridge" network: failed to parse pool request
                        for address space "LocalDefault" pool " subpool ":
@@ -344,7 +344,7 @@ In a similar way, if you specify the `--ipv6` flag when creating a network
 with the default IPAM driver, without providing an IPv6 `--subnet`, network
 creation will fail with the following message:
 
-```none
+```text
 Error response from daemon: failed to parse pool request for address space
                             "LocalDefault" pool "" subpool "": could not find an
                             available, non-overlapping IPv6 address pool among
@@ -397,7 +397,7 @@ If you are currently using the `--ipv6` option _without_ specifying the
 `--fixed-cidr-v6` option, the Docker daemon will refuse to start with the
 following message:
 
-```none
+```text
 Error starting daemon: Error initializing network controller: Error creating
                        default "bridge" network: failed to parse pool request
                        for address space "LocalDefault" pool " subpool ":
@@ -413,7 +413,7 @@ In a similar way, if you specify the `--ipv6` flag when creating a network
 with the default IPAM driver, without providing an IPv6 `--subnet`, network
 creation will fail with the following message:
 
-```none
+```text
 Error response from daemon: failed to parse pool request for address space
                             "LocalDefault" pool "" subpool "": could not find an
                             available, non-overlapping IPv6 address pool among

content/manuals/engine/security/userns-remap.md

@@ -22,7 +22,7 @@ The remapping itself is handled by two files: `/etc/subuid` and `/etc/subgid`.
 Each file works the same, but one is concerned with the user ID range, and the
 other with the group ID range. Consider the following entry in `/etc/subuid`:
 
-```none
+```text
 testuser:231072:65536
 ```
 
@@ -93,7 +93,7 @@ avoid these situations.
     and a maximum number of UIDs or GIDs available to the user. For instance,
     given the following entry:
 
-    ```none
+    ```text
     testuser:231072:65536
     ```
 

content/manuals/engine/storage/drivers/device-mapper-driver.md

@@ -297,7 +297,7 @@ assumes that the Docker daemon is in the `stopped` state.
     The example below adds 20% more capacity when the disk usage reaches
     80%.
 
-    ```none
+    ```text
     activation {
       thin_pool_autoextend_threshold=80
       thin_pool_autoextend_percent=20

content/manuals/engine/swarm/admin_guide.md

@@ -221,7 +221,7 @@ the `docker node rm` command. If a node becomes unreachable, unresponsive, or
 compromised you can forcefully remove the node without shutting it down by
 passing the `--force` flag. For instance, if `node9` becomes compromised:
 
-```none
+```text
 $ docker node rm node9
 
 Error response from daemon: rpc error: code = 9 desc = node node9 is not down and can't be removed
@@ -338,7 +338,7 @@ If you lose the quorum of managers, you cannot administer the swarm. If you have
 lost the quorum and you attempt to perform any management operation on the swarm,
 an error occurs:
 
-```none
+```text
 Error response from daemon: rpc error: code = 4 desc = context deadline exceeded
 ```
 

content/manuals/engine/swarm/configs.md

@@ -216,7 +216,7 @@ real-world example, continue to
     to the config. The container ID is different, because the
     `service update` command redeploys the service.
 
-    ```none
+    ```text
     $ docker container exec -it $(docker ps --filter name=redis -q) cat /my-config
 
     cat: can't open '/my-config': No such file or directory
@@ -373,7 +373,7 @@ generate the site key and certificate, name the files `site.key` and
     the following contents into it. This constrains the root CA to only sign
     leaf certificates and not intermediate CAs.
 
-    ```none
+    ```text
     [root_ca]
     basicConstraints = critical,CA:TRUE,pathlen:1
     keyUsage = critical, nonRepudiation, cRLSign, keyCertSign
@@ -407,7 +407,7 @@ generate the site key and certificate, name the files `site.key` and
     certificate so that it can only be used to authenticate a server and
     can't be used to sign certificates.
 
-    ```none
+    ```text
     [server]
     authorityKeyIdentifier=keyid,issuer
     basicConstraints = critical,CA:FALSE
@@ -438,7 +438,7 @@ generate the site key and certificate, name the files `site.key` and
     In the current directory, create a new file called `site.conf` with the
     following contents:
 
-    ```none
+    ```text
     server {
         listen                443 ssl;
         server_name           localhost;
@@ -616,7 +616,7 @@ configuration file.
 1.  Edit the `site.conf` file locally. Add `index.php` to the `index` line, and
     save the file.
 
-    ```none
+    ```text
     server {
         listen                443 ssl;
         server_name           localhost;