Fix typos in some docs

Signed-off-by: Lan Luo <luola@vmware.com>
antrea-io · Aug 20, 2024 · 6dcbd83 · 6dcbd83
1 parent 7d8d4b1
commit 6dcbd83
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/docs/antrea-network-policy.md b/docs/antrea-network-policy.md
@@ -743,7 +743,7 @@ Also, each rule has an optional `name` field, which should be unique within
 the policy describing the intention of this rule. If `name` is not provided for
 a rule, it will be auto-generated by Antrea. The rule name auto-generation process
 is the same as ingress rules.
-A ClusterGroup name can be set in the `group` field of a egress `to` section in place
+A ClusterGroup name can be set in the `group` field of an egress `to` section in place
 of stand-alone selectors to allow traffic to workloads/ipBlocks set in the ClusterGroup.
 `toServices` field contains a list of combinations of Service Namespace and Service Name
 to match traffic to this Service.

diff --git a/docs/contributors/docker-desktop-alternatives.md b/docs/contributors/docker-desktop-alternatives.md
@@ -22,7 +22,7 @@ following Docker Desktop alternatives.
 
 [Colima](https://github.com/abiosoft/colima) is a UI built with
 [Lima](https://github.com/lima-vm/lima). It supports running a container runtime
-(docker, containerd or kuberneters) on macOS, inside a Lima VM. Major benefits
+(docker, containerd or kubernetes) on macOS, inside a Lima VM. Major benefits
 of Colima include its ability to be used as a drop-in replacement for Docker
 Desktop and its ability to coexist with Docker Desktop on the same macOS
 machine.

diff --git a/docs/kubernetes-installers.md b/docs/kubernetes-installers.md
@@ -27,7 +27,7 @@ work with that Antrea version.
 | v1.11.0 | Kubeadm v1.25.5 | N/A | openEuler 22.03 LTS, containerd://1.6.18 | 10GB RAM | | |
 | v1.15.0 | Talos v1.5.5 | Docker provisioner | Talos | 2 vCPUs, 2.1 GB RAM | Pass | Requires Antrea v1.15 or above |
 | - | - | QEMU provisioner | Talos | 2 vCPUs, 2.1 GB RAM | Pass | Requires Antrea v1.15 or above |
-| v2.0 | Rancher v2.7.0, RKE2, K8s v1.24.10 | vSphere | Ubuntu 22.04.1 LTS (5.15.0-57-generic) amd64, docker://20.10.21 | 4 vCPUs, 4GB RAM |  | ANTREA CI |
+| v2.0 | Rancher v2.7.0, RKE2, K8s v1.24.10 | vSphere | Ubuntu 22.04.1 LTS (5.15.0-57-generic) amd64, docker://20.10.21 | 4 vCPUs, 4GB RAM |  | Antrea CI |
 
 ## Installer-specific instructions
 

diff --git a/docs/secondary-network.md b/docs/secondary-network.md
@@ -68,7 +68,7 @@ data:
 ```
 
 At the moment, Antrea supports only a single OVS bridge for secondary networks,
-and supports upto eight physical interfaces on the bridge. The physical
+and supports up to eight physical interfaces on the bridge. The physical
 interfaces cannot be the Node's management interface, otherwise the Node's
 management network connectivity can be broken after `antrea-agent` creates the
 OVS bridge and moves the management interface to the bridge.
@@ -99,7 +99,7 @@ spec:
 ```
 
 `antrea-agent` will connect Pod secondary interfaces belonging to a VLAN network
-to the secondary OVS bridge on the Node. If a non-zero VLAN is speficied in the
+to the secondary OVS bridge on the Node. If a non-zero VLAN is specified in the
 network's `config`, `antrea-agent` will configure the VLAN ID on the OVS port,
 so the interface's traffic will be isolated within the VLAN. And before the
 traffic is forwarded out of the Node via the secondary bridge's physical