diff options
| author |   Paul Vinciguerra <pvinci@vinciconsulting.com> | 2019-11-05 15:34:36 -0500 |
|---|---|---|
| committer |   Dave Barach <openvpp@barachs.net> | 2019-11-06 17:53:42 +0000 |
| commit | 340c15c6ed34ce60c821b5260fec3eb11d65dcb7 (patch) | |
| tree | e791acb487279b7273cdbe753a2d46ccd982f5ea /docs/usecases/ConnectingVPC.rst | |
| parent | 4d11b6cecaa9c1be20aa149bc8779f197f6393ed (diff) | |
docs: add spellcheck to 'make docs' sphinx docs
The CI gate will fail if there are typos in the docs.
writing output... [ 21%] events/Summits/OpensourceSummit...
writing output... [ 22%] events/Summits/UKNO/2017_04_30_...
featuresbyrelease/vpp16.06.rst:34:Rasberry:vpp16.06
writing output... [100%] usecases/vppinazure
Spelling checker messages written to /vpp/docs/_build/html/output.txt
Warning, treated as error:
Found 1 misspelled words
Makefile:31: recipe for target 'html' failed
make[1]: *** [html] Error 2
make[1]: Leaving directory '/vpp/docs'
If you introduce a term that is not recognized,
please add it to custom dictionary at
docs/spelling_wordlist.txt.
Type: feature
Change-Id: Id49be4fbee617f544f1ab8e78e7de8a4df36448b
Signed-off-by: Paul Vinciguerra <pvinci@vinciconsulting.com>
Diffstat (limited to 'docs/usecases/ConnectingVPC.rst')
| -rw-r--r-- | docs/usecases/ConnectingVPC.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/usecases/ConnectingVPC.rst b/docs/usecases/ConnectingVPC.rst index cc8c927b2cb..f5b2c5dc9ae 100644 --- a/docs/usecases/ConnectingVPC.rst +++ b/docs/usecases/ConnectingVPC.rst @@ -25,7 +25,7 @@ In our VPC we will have two instances: one, in which we will install VPP and the Figure 2: Example of the resources present inside our VPC -Notice that the following example works with two VPCs, where in each of them there are a VM with VPP and a VM. Hence, you will have to execute the same commands also in the other VPC to make the connection between the two VPC possibile. +Notice that the following example works with two VPCs, where in each of them there are a VM with VPP and a VM. Hence, you will have to execute the same commands also in the other VPC to make the connection between the two VPC possible. Now, create a new VM instance (you can use same setting as before (Ubuntu Server 16.04 and m5 type)) and attach a NIC. Remember that the two Client/Server machine's NICs should stay in two different IPv4 Subnet. Afterwards, on the VM's terminal execute these commands: |