diff options
author | srividya0208 <a.srividya@vyos.io> | 2021-07-25 08:00:04 -0400 |
---|---|---|
committer | srividya0208 <a.srividya@vyos.io> | 2021-07-25 08:00:04 -0400 |
commit | 0b1de0a9ae4b993ca49dd22980986c3d05e558e1 (patch) | |
tree | 3e571c02f59a38d63fd300fb0fe487f97e6f1c84 | |
parent | cd34454b29b0bdcda1467037c5f7e9e631705aaf (diff) | |
download | vyos-documentation-0b1de0a9ae4b993ca49dd22980986c3d05e558e1.tar.gz vyos-documentation-0b1de0a9ae4b993ca49dd22980986c3d05e558e1.zip |
grammar correction
-rw-r--r-- | docs/installation/cloud/aws.rst | 4 | ||||
-rw-r--r-- | docs/installation/cloud/azure.rst | 26 | ||||
-rw-r--r-- | docs/installation/cloud/gcp.rst | 9 |
3 files changed, 25 insertions, 14 deletions
diff --git a/docs/installation/cloud/aws.rst b/docs/installation/cloud/aws.rst index d64aca82..62821093 100644 --- a/docs/installation/cloud/aws.rst +++ b/docs/installation/cloud/aws.rst @@ -25,7 +25,7 @@ Deploy VyOS on Amazon :abbr:`AWS (Amazon Web Services)` .. figure:: /_static/images/cloud-aws-04.png 5. Additional storage. You can remove additional storage ``/dev/sdb``. First - root device will be ``/dev/xvda``. You can skeep this step. + root device will be ``/dev/xvda``. You may skip this step. .. figure:: /_static/images/cloud-aws-05.png @@ -54,4 +54,4 @@ Deploy VyOS on Amazon :abbr:`AWS (Amazon Web Services)` References ---------- -https://console.aws.amazon.com/
\ No newline at end of file +https://console.aws.amazon.com/ diff --git a/docs/installation/cloud/azure.rst b/docs/installation/cloud/azure.rst index e19df986..11240fb5 100644 --- a/docs/installation/cloud/azure.rst +++ b/docs/installation/cloud/azure.rst @@ -7,7 +7,7 @@ Deploy VM Deploy VyOS on Azure. -1. Go to the Azure services and Click to **Add new Virtual machine** +1. Go to the Azure services and Click on **Add new Virtual machine** 2. Choose vm name, resource group, region and click **Browse all public and private images** @@ -26,7 +26,8 @@ Deploy VyOS on Azure. .. figure:: /_static/images/cloud-azure-04.png -6. Click ``Review + create``. After a few seconds your deployment will be complete +6. Click ``Review + create``. After a few seconds your deployment will be + completed .. figure:: /_static/images/cloud-azure-05.png @@ -45,8 +46,8 @@ Add interface ------------- If instance was deployed with one **eth0** ``WAN`` interface and want to add -new one. To add new interface an example **eth1** ``LAN`` you need shutdown the -instance. Attach the interface in the Azure portal and then start the instance. +new one, like **eth1** ``LAN`` you need to shutdown the instance first. Attach +the interface in the Azure portal and then start the instance. .. note:: Azure does not allow you attach interface when the instance in the **Running** state. @@ -54,18 +55,27 @@ instance. Attach the interface in the Azure portal and then start the instance. Absorbing Routes ---------------- -If using as a router, you will want your LAN interface to absorb some or all of the traffic from your VNET by using a route table applied to the subnet. +If using as a router, you will want your LAN interface to absorb some or all +of the traffic from your VNET by using a route table applied to the subnet. 1. Create a route table and browse to **Configuration** -2. Add one or more routes for networks you want to pass through the VyOS VM. Next hop type **Virtual Appliance** with the **Next Hop Address** of the VyOS ``LAN`` interface. +2. Add one or more routes for networks you want to pass through the VyOS VM. + Next hop type **Virtual Appliance** with the **Next Hop Address** of the + VyOS ``LAN`` interface. -.. note:: If you want to create a new default route for VMs on the subnet, use **Address Prefix** ``0.0.0.0/0`` Also note that if you want to use this as a typical edge device, you'll want masquerade NAT for the ``WAN`` interface. +.. note:: If you want to create a new default route for VMs on the subnet, use + **Address Prefix** ``0.0.0.0/0`` Also note that if you want to use this as + a typical edge device, you'll want to masquerade NAT for the ``WAN`` + interface. Serial Console -------------- -Azure has a way to access the serial console of a VM, but this needs to be configured on the VyOS. It's there by default, but keep it in mind if you are replacing config.boot and rebooting: ``set system console device ttyS0 speed '9600'`` +Azure has a way to access the serial console of a VM, but this needs to be +configured on the VyOS. It's there by default, but keep it in mind if you are +replacing config.boot and rebooting: ``set system console device ttyS0 speed +'9600'`` References ---------- diff --git a/docs/installation/cloud/gcp.rst b/docs/installation/cloud/gcp.rst index 07aecdbe..318c1872 100644 --- a/docs/installation/cloud/gcp.rst +++ b/docs/installation/cloud/gcp.rst @@ -1,3 +1,4 @@ + ##################### Google Cloud Platform ##################### @@ -17,8 +18,8 @@ To deploy VyOS on GCP (Google Cloud Platform) ssh-keygen -t rsa -f ~/.ssh/vyos_gcp -C "vyos@mypc" -.. note:: In name "vyos@mypc" The first value must be "**vyos**". Because - default user is vyos and google api uses this option. +.. note:: For name, type "vyos@mypc" as the first value must be "**vyos**". + Because default user is vyos and google api uses this option. 2. Open GCP console and navigate to the menu **Metadata**. Choose @@ -38,7 +39,7 @@ Click **Add item** and paste your public ssh key. Click ``Save``. .. figure:: /_static/images/cloud-gcp-03.png -4. After fiew seconds click to ``instance`` +4. After few seconds click on ``instance`` .. figure:: /_static/images/cloud-gcp-04.png @@ -55,4 +56,4 @@ Click **Add item** and paste your public ssh key. Click ``Save``. References ---------- -https://console.cloud.google.com/
\ No newline at end of file +https://console.cloud.google.com/ |