fix setup guide typo (#9537)

docs/en/protocols/Trace-Data-Protocol-v3.md

@@ -140,10 +140,10 @@ message SpanObject {
     SpanType spanType = 8;
     // Span layer represent the component tech stack, related to the network tech.
     SpanLayer spanLayer = 9;
-    // Component id is a predefinited number id in the SkyWalking.
+    // Component id is a predefined number id in the SkyWalking.
     // It represents the framework, tech stack used by this tracked span, such as Spring.
     // All IDs are defined in the https://github.com/apache/skywalking/blob/master/oap-server/server-bootstrap/src/main/resources/component-libraries.yml
-    // Send a pull request if you want to add languages, components or mapping defintions,
+    // Send a pull request if you want to add languages, components or mapping definitions,
     // all public components could be accepted.
     // Follow this doc for more details, https://github.com/apache/skywalking/blob/master/docs/en/guides/Component-library-settings.md
     int32 componentId = 10;

docs/en/setup/backend/backend-docker.md

@@ -1,12 +1,12 @@
 # How to use the Docker images
 
-## Start a `standlone` container with `H2` storage
+## Start a `standalone` container with `H2` storage
 
 ```shell
 docker run --name oap --restart always -d apache/skywalking-oap-server:9.0.0
 ```
 
-## Start a `standlone` container with ElasticSearch 7 as storage whose address is `elasticsearch:9200`
+## Start a `standalone` container with ElasticSearch 7 as storage whose address is `elasticsearch:9200`
 
 ```shell
 docker run --name oap --restart always -d -e SW_STORAGE=elasticsearch -e SW_STORAGE_ES_CLUSTER_NODES=elasticsearch:9200 apache/skywalking-oap-server:9.0.0

docs/en/setup/backend/dynamic-config-apollo.md

@@ -19,7 +19,7 @@ Single configs in Apollo are key/value pairs:
 
 | Key | Value |
 |-----|-----|
-| configKey | configVaule |
+| configKey | configValue |
 
 e.g. The config is:
 ```

docs/en/setup/backend/dynamic-config-configmap.md

@@ -1,4 +1,4 @@
-# Dynamic Configuration Kuberbetes Configmap Implementation
+# Dynamic Configuration Kubernetes Configmap Implementation
 
 [configmap](https://kubernetes.io/docs/concepts/configuration/configmap/) is also supported as a Dynamic Configuration Center (DCC). To use it, please configure it as follows:
 

docs/en/setup/backend/dynamic-config.md

@@ -21,7 +21,7 @@ configuration:
 ## Single Configuration
 Single Configuration is a config key that corresponds to a specific config value. The logic structure is:
 ```
-{configKey}:{configVaule}
+{configKey}:{configValue}
 ```
 For example:
 ```
@@ -67,5 +67,5 @@ Supported configurations are as follows:
 - [Etcd Implementation](./dynamic-config-etcd.md)
 - [Consul Implementation](./dynamic-config-consul.md)
 - [Apollo Implementation](./dynamic-config-apollo.md)
-- [Kuberbetes Configmap Implementation](./dynamic-config-configmap.md)
+- [Kubernetes Configmap Implementation](./dynamic-config-configmap.md)
 - [Nacos Implementation](./dynamic-config-nacos.md)

docs/en/setup/backend/dynamical-logging.md

@@ -10,7 +10,7 @@ The key of the configuration item is `core.default.log4j-xml`, and you can selec
 to store the content of `log4j.xml`. In the booting phase, once the core module gets started, `core.default.log4j-xml`
 would come into the OAP log4j context.
 
-If the configuration is changed after the OAP startup, you have to wait for a while for the changes to be applied. The default value is `60` seconds, which you could change through `configuration.<configuration implement>.peroid` in `application.yaml`.
+If the configuration is changed after the OAP startup, you have to wait for a while for the changes to be applied. The default value is `60` seconds, which you could change through `configuration.<configuration implement>.period` in `application.yaml`.
 
 If you remove `core.default.log4j-xml` from the configuration center or disable the configuration module, `log4j.xml` in the `config` directory would be affected.
 

docs/en/setup/backend/endpoint-grouping-rules.md

@@ -272,7 +272,7 @@ components:
 
 Here are some use cases:
 
-   | Incoming Endpiont | Incoming Service | x-sw-service-name | x-sw-endpoint-name-match-rule | x-sw-endpoint-name-format | Matched | Grouping Result |
+   | Incoming Endpoint | Incoming Service | x-sw-service-name | x-sw-endpoint-name-match-rule | x-sw-endpoint-name-format | Matched | Grouping Result |
    |-----|-----|-----|-----|-----|-----|-----|
    | `GET:/products` | serviceB | default | default | default | true | `GET:/products` |
    | `GET:/products/123` | serviceB | default | default | default |  true | `GET:/products{id}` |