chore: fix spelling (#210)
diff --git a/website/blog/2021-01-21-run-ingress-apisix-on-amazon-eks.md b/website/blog/2021-01-21-run-ingress-apisix-on-amazon-eks.md
index 1243482..7deded9 100644
--- a/website/blog/2021-01-21-run-ingress-apisix-on-amazon-eks.md
+++ b/website/blog/2021-01-21-run-ingress-apisix-on-amazon-eks.md
@@ -5,7 +5,7 @@
authorImageURL: "https://avatars0.githubusercontent.com/u/10428333?s=60&v=4"
---
-> [@Chao Zhang](https://github.com/tokers), Apache APISIX Comitter from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/)
+> [@Chao Zhang](https://github.com/tokers), Apache APISIX Committer from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/)
>
> Source:
>
@@ -19,7 +19,7 @@
Amazon Elastic Kubernetes Service ([Amazon EKS](https://amazonaws-china.com/eks/?whats-new-cards.sort-by=item.additionalFields.postDateTime&whats-new-cards.sort-order=desc&eks-blogs.sort-by=item.additionalFields.createdDate&eks-blogs.sort-order=desc)) gives you the flexibility to start, run, and scale Kubernetes applications in the AWS cloud or on-premises. This article explains how to run Ingress APISIX on it.
-Ingress APISIX brings good features (traffic splitting, multiple protocols, authentication and etc) of Apache APISIX to Kubernetes, with a well-designed Controller componment to drive it, which helps users to achieve complex demands for the north-south traffic.
+Ingress APISIX brings good features (traffic splitting, multiple protocols, authentication and etc) of Apache APISIX to Kubernetes, with a well-designed Controller component to drive it, which helps users to achieve complex demands for the north-south traffic.
## Prerequisites
@@ -82,7 +82,7 @@
The ingress-apisix-base chart installed some basic dependencies for apisix-ingress-controller, such as ServiceAccount, its exclusive CRDs and etc.
-The ingress-apisix chart guides us how to install the controller itself, you can change the image tag to the desired release version, also the value of `ingressController.config.apisix.adminKey` in abovementioned commands should be filled according to your pratical usage (and be sure the admin key is same as the on in Apache APISIX deployment). See [value.yaml](https://github.com/apache/apisix-ingress-controller/blob/master/charts/ingress-apisix/values.yaml) to learn all the configuration items if you have other requirements.
+The ingress-apisix chart guides us how to install the controller itself, you can change the image tag to the desired release version, also the value of `ingressController.config.apisix.adminKey` in above mentioned commands should be filled according to your practical usage (and be sure the admin key is same as the on in Apache APISIX deployment). See [value.yaml](https://github.com/apache/apisix-ingress-controller/blob/master/charts/ingress-apisix/values.yaml) to learn all the configuration items if you have other requirements.
Now try to open your EKS console, choosing your cluster and clicking the Workloads tag, you shall see all pods of Apache APISIX, etcd and apisix-ingress-controller are ready.
@@ -139,7 +139,7 @@
}
```
-If the Serivce type is `ClusterIP,` you have to login to a pod in the EKS cluster, then accessing Apache APISIX with its `ClusterIP` or Service FQDN. If it was exposed (no matter `NodePort` or `LoadBalancer`), just accessing its outside reachable endpoint.
+If the Service type is `ClusterIP,` you have to login to a pod in the EKS cluster, then accessing Apache APISIX with its `ClusterIP` or Service FQDN. If it was exposed (no matter `NodePort` or `LoadBalancer`), just accessing its outside reachable endpoint.
## See Also
diff --git a/website/blog/2021-02-08-stable-product-delivery-with-cypress.md b/website/blog/2021-02-08-stable-product-delivery-with-cypress.md
index aebf0b1..2ce32e3 100644
--- a/website/blog/2021-02-08-stable-product-delivery-with-cypress.md
+++ b/website/blog/2021-02-08-stable-product-delivery-with-cypress.md
@@ -92,7 +92,7 @@
2. Extract the selector and data as public variables.
-To make it more intuitive for the user to understand the meaning of the test code, we extract selcector and data as public variables.
+To make it more intuitive for the user to understand the meaning of the test code, we extract a selector and data as public variables.
```javaScript
const data = {
@@ -111,7 +111,7 @@
3. Remove cy.wait(someTime)
-We used cy.wait(someTime) in the early days of Cypress, but found that cy.wait(someTime) relies too much on the network environment and the performance of the test machine, which can cause test cases to report errors when the network environment or machine performance is poor. The recommended practice is to use it in conjunction with cy.intercpet() to explicitly specify the network resources to wait for.
+We used cy.wait(someTime) in the early days of Cypress, but found that cy.wait(someTime) relies too much on the network environment and the performance of the test machine, which can cause test cases to report errors when the network environment or machine performance is poor. The recommended practice is to use it in conjunction with cy.intercept() to explicitly specify the network resources to wait for.
```javascript
cy.intercept("https://apisix.apache.org/").as("fetchURL");
diff --git a/website/events/2020-12-23-release-apache-apisix-ingress-controller-0.1.0.md b/website/events/2020-12-23-release-apache-apisix-ingress-controller-0.1.0.md
index 176f49e..b1874c9 100644
--- a/website/events/2020-12-23-release-apache-apisix-ingress-controller-0.1.0.md
+++ b/website/events/2020-12-23-release-apache-apisix-ingress-controller-0.1.0.md
@@ -17,7 +17,7 @@
## Test case
-- Add E2E test enviroment. [#101](https://github.com/apache/apisix-ingress-controller/pull/101)
+- Add E2E test environment. [#101](https://github.com/apache/apisix-ingress-controller/pull/101)
## Bugfix
diff --git a/website/events/2021-02-12-release-apache-apisix-dashboard-2.4.md b/website/events/2021-02-12-release-apache-apisix-dashboard-2.4.md
index 914762a..6b75de1 100644
--- a/website/events/2021-02-12-release-apache-apisix-dashboard-2.4.md
+++ b/website/events/2021-02-12-release-apache-apisix-dashboard-2.4.md
@@ -34,7 +34,7 @@
### Test Case
-- Use ginkgo framwork to do backend E2E testing. [#1319](https://github.com/apache/apisix-dashboard/pull/1319)
+- Use ginkgo framework to do backend E2E testing. [#1319](https://github.com/apache/apisix-dashboard/pull/1319)
- Add action to check the version for release. [#1418](https://github.com/apache/apisix-dashboard/pull/1418)
- Add test for make build. [#1421](https://github.com/apache/apisix-dashboard/pull/1421)
- Remove the etcd dependency in part of unit test. [#1169](https://github.com/apache/apisix-dashboard/pull/1469)
@@ -45,4 +45,4 @@
### Doc
-- Doc: add document for introducing bakend e2e test. [#1381](https://github.com/apache/apisix-dashboard/pull/1381)
+- Doc: add document for introducing backend e2e test. [#1381](https://github.com/apache/apisix-dashboard/pull/1381)
