Merge pull request honojs#553 from chaosi-zju/typos

fix typos error of documents

Author: karmada-bot

blog/2022-10-26-test-report/index.md

@@ -76,15 +76,15 @@ With reference to the SLI (Service Level Indicator)/SLO (Service Level Objective
 
 | Status  | SLI                                                                                                                      | SLO                                                                           |
 |---------|--------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|
-| Offical | P99 latency of Mutating API calls (including POST, PUT, DELETE, PATCH) to a single resource object in the last 5 minutes | P99 <= 1s                                                                     |
-| Offical | P99 latency of non-streaming read-only API calls (including GET and LIST) in the last 5 minutes                          | (a)Scope=resource, P99 <= 1s, (b)Scope=namespace or Scope=cluster, P99 <= 30s |
+| Official | P99 latency of Mutating API calls (including POST, PUT, DELETE, PATCH) to a single resource object in the last 5 minutes | P99 <= 1s                                                                     |
+| Official | P99 latency of non-streaming read-only API calls (including GET and LIST) in the last 5 minutes                          | (a)Scope=resource, P99 <= 1s, (b)Scope=namespace or Scope=cluster, P99 <= 30s |
 
 2. Resource Distribution Latency
 
 
 | Status  | SLI                                                                                                                                                                                                                                                                         | SLO       |
 |---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
-| Offical | After the user submits the resource template and delivers the policy on the federated control plane, the P99 delay from the time when the resource is created on the member cluster, regardless of the network fluctuation between the control plane and the member cluster | P99 <= 2s |
+| Official | After the user submits the resource template and delivers the policy on the federated control plane, the P99 delay from the time when the resource is created on the member cluster, regardless of the network fluctuation between the control plane and the member cluster | P99 <= 2s |
 
 3. Cluster Registration Latency
 
@@ -431,7 +431,7 @@ Based on this, the number of resources for the control plane does not depend on
 
 Karmada's arthrecture inherits the simplicity and scalability of Kubernetes. Karmada-apiserver as the entry point of the control plane is like kube-apiserver in Kubernetes. You can optimize the component in multi-cluster scenarios using the parameters you need in single cluster configuration.
 
-During the entire resource distribution process, API call latency is within a resonable range.
+During the entire resource distribution process, API call latency is within a reasonable range.
 
 ### Cluster Registry and Resource Distribution
 
@@ -465,7 +465,7 @@ In Pull mode, the main resource consumption of the control plane is concentrated
 From the qps of karmada-apiserver and the request latency of karmada-etcd, we can know that the number of requests to karmada-apiserver is kept at a high level.
 In Pull mode, karmada-agent of each member cluster needs to maintain a long connection with karmada-apiserver.
 We can easily conclude that the number of requests for karmada-apiserver will be N times that of configuration in karmada-agent(N=`#Num of clusters`).
-Therefore, in the scenario of a large number of Pull mode clusters, we recommand increasing the `--max-requests-inflight`, `--max-mutating-requests-inflight` in karmada-apiserver and `--quota-backend-bytes` in karmada-etcd to improve the throughout of the control plane.
+Therefore, in the scenario of a large number of Pull mode clusters, we recommend increasing the `--max-requests-inflight`, `--max-mutating-requests-inflight` in karmada-apiserver and `--quota-backend-bytes` in karmada-etcd to improve the throughout of the control plane.
 
 Now Karmada provides the ability named [cluster resource modeling](https://karmada.io/docs/next/userguide/scheduling/cluster-resources) to make scheduling decisions in scenario of dynamic replica assignment based on idle cluster resources.
 In the process of resource modeling, it will collect node and pod information from all clusters managed by Karmada. This imposes a considerable performance burden in large-scale scenarios.

docs/reference/karmada-api/common-definitions/quantity.md

@@ -16,7 +16,7 @@ auto_generated: true
 
 `import "k8s.io/apimachinery/pkg/api/resource"`
 
-Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.
+Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshalling in JSON and YAML, in addition to String() and AsInt64() accessors.
 
 The serialization format is:
 

docs/tutorials/access-service-across-clusters.md

@@ -1,5 +1,5 @@
 ---
-title: Access service acrosss clusters within native service
+title: Access service across clusters within native service
 ---
 
 In Karmada, the MultiClusterService can enable users to access services across clusters with the native service domain name, like `foo.svc`, with the aim of providing users with a seamless experience when accessing services across multiple clusters, as if they were operating within a single cluster.

i18n/zh/docusaurus-plugin-content-blog/2022-10-26-test-report/index.md

@@ -70,15 +70,15 @@ karmada-controller-manager运行着各种控制器，这些控制器watch着Karm
 
 | Status  | SLI                                                        | SLO                                                                           |
 |---------|------------------------------------------------------------|-------------------------------------------------------------------------------|
-| Offical | 最近5min对单个资源对象Mutating API调用（包括POST、PUT、DELETE、PATCH）的P99时延 | P99 <= 1s                                                                     |
-| Offical | 最近5min的non-streaming的只读API调用（包括GET和LIST）的P99时延             | (a)Scope=resource, P99 <= 1s, (b)Scope=namespace or Scope=cluster, P99 <= 30s |
+| Official | 最近5min对单个资源对象Mutating API调用（包括POST、PUT、DELETE、PATCH）的P99时延 | P99 <= 1s                                                                     |
+| Official | 最近5min的non-streaming的只读API调用（包括GET和LIST）的P99时延             | (a)Scope=resource, P99 <= 1s, (b)Scope=namespace or Scope=cluster, P99 <= 30s |
 
 2. Resource Distribution Latency
 
 
 | Status  | SLI                                                       | SLO       |
 |---------|-----------------------------------------------------------|-----------|
-| Offical | 用户在联邦控制面提交资源模板和下发策略后到资源在成员集群上被创建的P99时延，不考虑控制面与成员集群之间的网络波动 | P99 <= 2s |
+| Official | 用户在联邦控制面提交资源模板和下发策略后到资源在成员集群上被创建的P99时延，不考虑控制面与成员集群之间的网络波动 | P99 <= 2s |
 
 3. Cluster Registration Latency
 

i18n/zh/docusaurus-plugin-content-docs/current/reference/karmada-api/common-definitions/quantity.md

@@ -16,7 +16,7 @@ auto_generated: true
 
 `import "k8s.io/apimachinery/pkg/api/resource"`
 
-Quantity 是数字的定点表示。除了 String() 和 AsInt64() 的访问接口之外，此字段还在 JSON 和 YAML 中提供了方便的序列化（marshaling）和反序列化（unmarshaling）。
+Quantity 是数字的定点表示。除了 String() 和 AsInt64() 的访问接口之外，此字段还在 JSON 和 YAML 中提供了方便的序列化（marshaling）和反序列化（unmarshalling）。
 
 序列化格式如下：
 

i18n/zh/docusaurus-plugin-content-docs/current/tutorials/access-service-across-clusters.md

@@ -1,5 +1,5 @@
 ---
-title: Access service acrosss clusters within native service
+title: Access service across clusters within native service
 ---
 
 In Karmada, the MultiClusterService can enable users to access services across clusters with the native service domain name, like `foo.svc`, with the aim of providing users with a seamless experience when accessing services across multiple clusters, as if they were operating within a single cluster.

i18n/zh/docusaurus-plugin-content-docs/current/tutorials/autoscaling-with-resource-metrics.md

@@ -1,5 +1,5 @@
 ---
-title: Autoscaling across clusters with resoruce metrics
+title: Autoscaling across clusters with resource metrics
 ---
 In Karmada, a FederatedHPA scales up/down the workload's replicas across multiple clusters, with the aim of automatically scaling the workload to match the demand.
 

i18n/zh/docusaurus-plugin-content-docs/version-v1.8/reference/karmada-api/common-definitions/quantity.md

@@ -16,7 +16,7 @@ auto_generated: true
 
 `import "k8s.io/apimachinery/pkg/api/resource"`
 
-Quantity 是数字的定点表示。除了 String() 和 AsInt64() 的访问接口之外，此字段还在 JSON 和 YAML 中提供了方便的序列化（marshaling）和反序列化（unmarshaling）。
+Quantity 是数字的定点表示。除了 String() 和 AsInt64() 的访问接口之外，此字段还在 JSON 和 YAML 中提供了方便的序列化（marshaling）和反序列化（unmarshalling）。
 
 序列化格式如下：
 

i18n/zh/docusaurus-plugin-content-docs/version-v1.8/tutorials/autoscaling-with-resource-metrics.md

@@ -1,5 +1,5 @@
 ---
-title: Autoscaling across clusters with resoruce metrics
+title: Autoscaling across clusters with resource metrics
 ---
 In Karmada, a FederatedHPA scales up/down the workload's replicas across multiple clusters, with the aim of automatically scaling the workload to match the demand.
 

versioned_docs/version-v1.8/reference/karmada-api/common-definitions/quantity.md

@@ -16,7 +16,7 @@ auto_generated: true
 
 `import "k8s.io/apimachinery/pkg/api/resource"`
 
-Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.
+Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshalling in JSON and YAML, in addition to String() and AsInt64() accessors.
 
 The serialization format is: