summaryrefslogtreecommitdiff
path: root/docs/configuration
diff options
context:
space:
mode:
authorsrividya0208 <a.srividya@vyos.io>2022-06-27 14:46:17 -0400
committersrividya0208 <a.srividya@vyos.io>2022-06-27 14:46:17 -0400
commit743d89781f74afc30bfb6c10056b42bf32925059 (patch)
treeaa18da9b7ec648f173a99ddcea2b45fac25e227e /docs/configuration
parentac144475119d20328c3795f6d2031ce2b8f4a372 (diff)
downloadvyos-documentation-743d89781f74afc30bfb6c10056b42bf32925059.tar.gz
vyos-documentation-743d89781f74afc30bfb6c10056b42bf32925059.zip
syntax and grammar check
Modified the grammatical error and bgp syntax which is modified in the latest rolling version
Diffstat (limited to 'docs/configuration')
-rw-r--r--docs/configuration/interfaces/openvpn.rst2
-rw-r--r--docs/configuration/vrf/index.rst4
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/configuration/interfaces/openvpn.rst b/docs/configuration/interfaces/openvpn.rst
index 3fe6b1d4..ff32d869 100644
--- a/docs/configuration/interfaces/openvpn.rst
+++ b/docs/configuration/interfaces/openvpn.rst
@@ -332,7 +332,7 @@ before using under the openvpn interface configuration.
Now we need to specify the server network settings. In all cases we need to
specify the subnet for client tunnel endpoints. Since we want clients to access
-a specific network behind out router, we will use a push-route option for
+a specific network behind our router, we will use a push-route option for
installing that route on clients.
.. code-block:: none
diff --git a/docs/configuration/vrf/index.rst b/docs/configuration/vrf/index.rst
index 90d99c56..e58005e7 100644
--- a/docs/configuration/vrf/index.rst
+++ b/docs/configuration/vrf/index.rst
@@ -197,7 +197,7 @@ Example
VRF route leaking
-----------------
-The following example topology was build using EVE-NG.
+The following example topology was built using EVE-NG.
.. figure:: /_static/images/vrf-example-topology-01.png
:alt: VRF topology example
@@ -338,7 +338,7 @@ VRF Route Leaking
BGP routes may be leaked (i.e. copied) between a unicast VRF RIB and the VPN
SAFI RIB of the default VRF for use in MPLS-based L3VPNs. Unicast routes may
also be leaked between any VRFs (including the unicast RIB of the default BGP
-instanced). A shortcut syntax is also available for specifying leaking from
+instance). A shortcut syntax is also available for specifying leaking from
one VRF to another VRF using the default instance’s VPN RIB as the intemediary
. A common application of the VRF-VRF feature is to connect a customer’s
private routing domain to a provider’s VPN service. Leaking is configured from