aboutsummaryrefslogtreecommitdiffstats
path: root/docs/usecases/contiv
diff options
context:
space:
mode:
Diffstat (limited to 'docs/usecases/contiv')
-rw-r--r--docs/usecases/contiv/BUG_REPORTS.md2
-rw-r--r--docs/usecases/contiv/K8s_Overview.md2
-rw-r--r--docs/usecases/contiv/MANUAL_INSTALL.md6
-rw-r--r--docs/usecases/contiv/MULTI_NIC_SETUP.md2
-rw-r--r--docs/usecases/contiv/VPP_PACKET_TRACING_K8S.md2
5 files changed, 7 insertions, 7 deletions
diff --git a/docs/usecases/contiv/BUG_REPORTS.md b/docs/usecases/contiv/BUG_REPORTS.md
index 648e67f2422..5b9c3cf4875 100644
--- a/docs/usecases/contiv/BUG_REPORTS.md
+++ b/docs/usecases/contiv/BUG_REPORTS.md
@@ -283,7 +283,7 @@ Prerequisites:
access to sudo.
#### Setting up Prerequisites
-To enable looging into a node without a password, copy your public key to the following
+To enable logging into a node without a password, copy your public key to the following
node:
```
ssh-copy-id <user-id>@<node-name-or-ip-address>
diff --git a/docs/usecases/contiv/K8s_Overview.md b/docs/usecases/contiv/K8s_Overview.md
index e3d8e1a0d44..ba3a8e12524 100644
--- a/docs/usecases/contiv/K8s_Overview.md
+++ b/docs/usecases/contiv/K8s_Overview.md
@@ -3,7 +3,7 @@
## Overview
-Kubernates is a container orchestration system that efficiently manages Docker containers. The Docker containers and container platforms provide many advantages over traditional virtualization. Container isolation is done on the kernel level, which eliminates the need for a guest virtual operating system, and therefore makes containers much more efficient, faster, and lightweight. The containers in Contiv/VPP are referred to as PODs.
+Kubernetes is a container orchestration system that efficiently manages Docker containers. The Docker containers and container platforms provide many advantages over traditional virtualization. Container isolation is done on the kernel level, which eliminates the need for a guest virtual operating system, and therefore makes containers much more efficient, faster, and lightweight. The containers in Contiv/VPP are referred to as PODs.
Contiv/VPP is a Kubernetes network plugin that uses [FD.io VPP](https://fd.io/)
to provide network connectivity between PODs in a k8s cluster (k8s is an abbreviated reference for kubernates).
diff --git a/docs/usecases/contiv/MANUAL_INSTALL.md b/docs/usecases/contiv/MANUAL_INSTALL.md
index d91a83a610c..35506db0d16 100644
--- a/docs/usecases/contiv/MANUAL_INSTALL.md
+++ b/docs/usecases/contiv/MANUAL_INSTALL.md
@@ -1,9 +1,9 @@
# Manual Installation
-This document describes how to clone the Contiv respository and then use [kubeadm][1] to manually install Kubernetes
+This document describes how to clone the Contiv repository and then use [kubeadm][1] to manually install Kubernetes
with Contiv-VPP networking on one or more bare metal or VM hosts.
-## Clone the Contiv Respository
-To clone the Contiv respository enter the following command:
+## Clone the Contiv Repository
+To clone the Contiv repository enter the following command:
```
git clone https://github.com/contiv/vpp/<repository-name>
```
diff --git a/docs/usecases/contiv/MULTI_NIC_SETUP.md b/docs/usecases/contiv/MULTI_NIC_SETUP.md
index 5cbb031d290..cacbcbb464b 100644
--- a/docs/usecases/contiv/MULTI_NIC_SETUP.md
+++ b/docs/usecases/contiv/MULTI_NIC_SETUP.md
@@ -5,7 +5,7 @@ described [here](https://github.com/contiv/vpp/blob/master/docs/VPP_CONFIG.md#mu
* For each interface owned by Linux, you need to provide individual
configuration for each interface used by VPP in the Node Configuration
- for thenode in the `contiv-vpp.yaml`. For example, if both `ens3` and
+ for the node in the `contiv-vpp.yaml`. For example, if both `ens3` and
`ens4` are known to Linux, then put the following stanza into the node's
NodeConfig:
```
diff --git a/docs/usecases/contiv/VPP_PACKET_TRACING_K8S.md b/docs/usecases/contiv/VPP_PACKET_TRACING_K8S.md
index f7b6f4c19e8..740918197e2 100644
--- a/docs/usecases/contiv/VPP_PACKET_TRACING_K8S.md
+++ b/docs/usecases/contiv/VPP_PACKET_TRACING_K8S.md
@@ -113,7 +113,7 @@ wildcard-ip4-arp-publisher-pro event wait 0 0
`tapcli-rx` above is the node-level input queue for incoming packets into all the pods on the node. There is one `tapcli-rx` input queue for every node.
-The following are the input and output queueus for each pod and the node:
+The following are the input and output queues for each pod and the node:
```
tapcli-0-output