Merge pull request #565 from srividya0208/proof-reading

vrf page: multiple typos and grammatical mistakes

2 files changed, 16 insertions, 12 deletions

diff --git a/docs/configuration/vrf/index.rst b/docs/configuration/vrf/index.rst
index ad0a70b9..a65f0073 100644
--- a/docs/configuration/vrf/index.rst
+++ b/docs/configuration/vrf/index.rst
@@ -1,3 +1,5 @@
+:lastproofread:2021-07-07
+
 .. _vrf:
 
 ###
@@ -23,7 +25,7 @@ then enslaved to a VRF device.
 
 .. cfgcmd:: set vrf name <name> table <id>
 
-   Configure use routing table `<id>` used by VRF `<name>`.
+   Configured routing table `<id>` is used by VRF `<name>`.
 
    .. note:: A routing table ID can not be modified once it is assigned. It can
       only be changed by deleting and re-adding the VRF instance.
@@ -62,14 +64,14 @@ Currently dynamic routing is supported for the following protocols:
 - :ref:`routing-ospf`
 - :ref:`routing-static`
 
-The CLI configuration the same as mentioned in above articles. The only
+The CLI configuration is same as mentioned in above articles. The only
 difference is, that each routing protocol used, must be prefixed with the `vrf
 name <name>` command.
 
 Example
 ^^^^^^^
 
-The following commands would be required to set options ofr a given dynamic
+The following commands would be required to set options for a given dynamic
 routing protocol inside a given vrf:
 
 - :ref:`routing-bgp`: ``set vrf name <name> protocols bgp ...``
@@ -81,11 +83,11 @@ Operation
 =========
 
 It is not sufficient to only configure a VRF but VRFs must be maintained, too.
-For VR Fmaintenance the followin operational commands are in place.
+For VRF maintenance the following operational commands are in place.
 
 .. opcmd:: show vrf
 
-   List VRFs that have been created
+   Lists VRFs that have been created
 
    .. code-block:: none
 
@@ -155,10 +157,10 @@ For VR Fmaintenance the followin operational commands are in place.
    will have an IP and ICMP header, followed by "struct timeval" and an
    arbitrary number of pad bytes used to fill out the packet.
 
-   When doing fault isolation with ping, your should first run it on the local
+   When doing fault isolation with ping, you should first run it on the local
    host, to verify that the local network interface is up and running. Then,
    continue with hosts and gateways further down the road towards your
-   destination. Round-trip times and packet loss statistics are computed.
+   destination. Round-trip time and packet loss statistics are computed.
 
    Duplicate packets are not included in the packet loss calculation, although
    the round-trip time of these packets is used in calculating the minimum/
@@ -180,10 +182,10 @@ For VR Fmaintenance the followin operational commands are in place.
 
 .. opcmd:: traceroute vrf <name> [ipv4 | ipv6] <host>
 
-   Displays the route packets take to a network host utilizing VRF instance
-   identified by `<name>`. When using the IPv4 or IPv6 option, display the route
-   packets take to the for the given hosts IP address family. This option is
-   useful when the host specified is a hostname rather than an IP address.
+   Displays the route packets taken to a network host utilizing VRF instance
+   identified by `<name>`. When using the IPv4 or IPv6 option, displays the 
+   route packets taken to the given hosts IP address family. This option is
+   useful when the host is specified as a hostname rather than an IP address.
 
 
 .. include:: /_include/common-references.txt
diff --git a/docs/operation/information.rst b/docs/operation/information.rst
index fea85feb..ad235210 100644
--- a/docs/operation/information.rst
+++ b/docs/operation/information.rst
@@ -1,3 +1,5 @@
+:lastproofread:2021-07-07
+
 .. _information:
 
 ***********
@@ -26,7 +28,7 @@ server connected but in addition also a serial backed :ref:`wwan-interface`.
 To overcome this issue and the fact that in almost 50% of all cheap USB to
 serial converters there is no serial number programmed, the USB to serial
 interface is now directly identified by the USB root bridge and bus it connects
-to. This somehow mimics the new network interface definitions we see in recend
+to. This somehow mimics the new network interface definitions we see in recent
 Linux distributions.
 
 For additional details you can refer to https://phabricator.vyos.net/T2490.