Merge lp:~ted-m-cox/serverguide/virtualization_punctuation into lp:serverguide/trunk

[Ted Cox]

[Doug Smythies (dsmythies)]

O.K. thanks.

Ted: Please consider to not make long lines.

review: Approve

=== modified file 'serverguide/C/virtualization.xml'
--- serverguide/C/virtualization.xml	2014-12-18 23:05:34 +0000
+++ serverguide/C/virtualization.xml	2015-05-07 04:56:37 +0000
@@ -112,9 +112,9 @@
 
       <para>Yet another way to install an Ubuntu virtual machine is to use
       <application>uvtool</application>.
-      This application, available as of 14.04  allows you to set up
+      This application, available as of 14.04, allows you to set up
       specific VM options, execute custom post-install scripts, etc. For
-      details see <xref linkend="cloud-images-and-uvtool"/></para>
+      details see <xref linkend="cloud-images-and-uvtool"/>.</para>
 
       <para>Libvirt can also be configured work with
       <application>Xen</application>. For details, see the Xen Ubuntu
@@ -198,7 +198,7 @@
 
       <para>After launching <application>virt-install</application> you can
       connect to the virtual machine's console either locally using a GUI (if
-      your server has a GUI), or via a remote VNC client from a GUI based
+      your server has a GUI), or via a remote VNC client from a GUI-based
       computer.</para>
     </sect2>
 
@@ -433,7 +433,7 @@
         </listitem>
 
         <listitem>
-          <para>The <ulink url="http://virt-manager.et.redhat.com/">Virtual
+          <para>The <ulink url="http://virt-manager.org/">Virtual
           Machine Manager</ulink> site has more information on
           <application>virt-manager</application> development.</para>
         </listitem>
@@ -466,8 +466,7 @@
     <sect2 id="cloud-image-introduction" status="review">
       <title>Introduction</title>
 
-      <para>With Ubuntu being one of the most used operating systems on most of
-      the cloud platforms, the availability of stable and secure cloud images
+      <para>With Ubuntu being one of the most used operating systems on many cloud platforms, the availability of stable and secure cloud images
       has become very important. As of 12.04 the utilization of cloud
       images outside of a cloud infrastructure has been improved. It is now
       possible to use those images to create a virtual machine without the
@@ -486,7 +485,7 @@
       <sect3>
         <title>Uvtool packages</title>
 
-        <para>The following packages and their dependancies will be required 
+        <para>The following packages and their dependencies will be required 
         in order to use uvtool:</para>
 
         <para/>
@@ -502,8 +501,7 @@
 
         </itemizedlist>
         
-<para>Installation of <application>uvtool</application> is done the same as 
-for any other application by using apt-get:</para>
+<para>To install <application>uvtool</application>, run:</para>
 <programlisting>$ apt-get -y install uvtool</programlisting>
 
 <para>This will install uvtool's main commands: </para>
@@ -523,7 +521,7 @@
 
         <programlisting>$ uvt-simplestreams-libvirt sync arch=amd64</programlisting>
         
-<para>After an amount of time required to download all the images from the internet, you will have 
+<para>After an amount of time required to download all the images from the Internet, you will have 
 a complete set of cloud images stored locally. To see what has been downloaded use the following 
 command:</para>
 
@@ -545,9 +543,7 @@
       <sect3>
         <title>Create the VM using uvt-kvm</title>
 
-<para>In order to be able to connect to the virtual machine once it has been created, it is necessary to have a 
-valid SSH key available for the ubuntu user.  If your environment does not have a ssh key, you can easily create 
-one using the following command:</para>
+<para>In order to connect to the virtual machine once it has been created, you must have a valid SSH key available for the Ubuntu user.  If your environment does not have an SSH key, you can easily create one using the following command:</para>
 
 <programlisting>
 $ ssh-keygen
@@ -572,18 +568,17 @@
 |             E   |
 +-----------------+
 </programlisting>
-        <para>The creation of a new virtual machine using uvtool is easy.  In its simplest form, 
-        you only need to do:</para>
+        <para>To create of a new virtual machine using uvtool, run the following in a terminal:</para>
 
 <programlisting>$ uvt-kvm create firsttest</programlisting>
 
 <para>This will create a VM named <emphasis role="bold">firsttest</emphasis> using the current LTS cloud image available locally.
-If you want to specify a release to be used to create the VM, you need to use the <emphasis role="bold">release=</emphasis> filter</para>
+If you want to specify a release to be used to create the VM, you need to use the <emphasis role="bold">release=</emphasis> filter:</para>
 
 <programlisting>$ uvt-kvm create secondtest release=trusty</programlisting>
 
-<para>The <application>uvt-kvm wait {name}</application> can be used to wait until the creation of 
-the VM has completed</para>
+<para><application>uvt-kvm wait</application> can be used to wait until the creation of 
+the VM has completed:</para>
 
 <programlisting>$ uvt-kvm wait secondttest --insecure
 Warning: secure wait for boot-finished not yet implemented; use --insecure.
@@ -591,16 +586,14 @@
 </sect3>
 
 <sect3><title>Connect to the running VM</title>
-<para>Once the virtual machine creation is completed, you can connect to it using ssh:
+<para>Once the virtual machine creation is completed, you can connect to it using SSH:
 </para>
 
 <programlisting>$ uvt-kvm ssh secondtest --insecure</programlisting>
 
-<para>For the time being, the <emphasis role="bold">--insecure</emphasis> is required so you should be
-using this mechanism to connect to your VM only if you completely trust your network infrastructure</para>
+<para>For the time being, the <emphasis role="bold">--insecure</emphasis> is required, so use this mechanism to connect to your VM only if you completely trust your network infrastructure.</para>
 
-<para>You can also connect to your VM using a regular ssh session using the IP address of the VM. The address
-can be queried using the following command: </para>
+<para>You can also connect to your VM using a regular SSH session using the IP address of the VM. The address can be queried using the following command:</para>
 
 <programlisting>
 $ uvt-kvm ip secondtest
@@ -629,7 +622,7 @@
 </sect3>
 
 <sect3><title>Get the list of running VMs</title>
-<para>You can get the list of VM running on your system with this command:</para>
+<para>You can get the list of VMs running on your system with this command:</para>
 
 <programlisting>$ uvt-kvm list
 secondtest
@@ -637,29 +630,28 @@
 </sect3>
 
 <sect3><title>Destroy your VM</title>
-<para>Once you are done with your VM, you can proceed to destroy it with: </para>
+<para>Once you are done with your VM, you can destroy it with:</para>
 
 <programlisting>$ uvt-kvm destroy secondtest</programlisting>
 </sect3>
 <sect3><title>More uvt-kvm options</title>
 
-<para>The following options can be used to change some of the characteristics of 
-the virtual memory that you are creating</para>
+<para>The following options can be used to change some of the characteristics of the VM that you are creating:</para>
 
 <itemizedlist mark="bullet">
-<listitem><para>--memory : Amount of RAM in megabytes. Default: 512</para></listitem>
-<listitem><para>--disk : Size of the OS disk in gigabytes. Default: 8</para></listitem>
-<listitem><para>--cpu : Number of CPU cores. Default: 1</para></listitem>
+<listitem><para>--memory : Amount of RAM in megabytes. Default: 512.</para></listitem>
+<listitem><para>--disk : Size of the OS disk in gigabytes. Default: 8.</para></listitem>
+<listitem><para>--cpu : Number of CPU cores. Default: 1.</para></listitem>
 </itemizedlist>
 
-<para>Some other parameters will have an impact on the cloud-init configuration</para>
+<para>Some other parameters will have an impact on the cloud-init configuration:</para>
 <itemizedlist mark="bullet">
-<listitem><para>--password password : Allow login to the VM using the ubuntu account and this provided password</para></listitem>
+<listitem><para>--password password : Allow login to the VM using the Ubuntu account and this provided password.</para></listitem>
 <listitem><para>--run-script-once script_file : Run  script_file  as  root on the VM the first time it is booted, but never again.</para></listitem>
 <listitem><para>--packages package_list : Install the comma-separated packages specified in package_list on first boot.</para></listitem>
 </itemizedlist>
 
-<para>A complete description of all available modifiers is available in the manpage of uvt-kvm</para>
+<para>A complete description of all available modifiers is available in the manpage of uvt-kvm.</para>
 </sect3>
 </sect2>
 
@@ -846,7 +838,7 @@
       <sect3>
       <title>Basic privileged usage</title>
       <para>
-      To create a privileged container, you can simply to
+      To create a privileged container, you can simply do:
       </para>
 <screen>
 <command>
@@ -1027,7 +1019,7 @@
     </para>
     <para>
       <filename>lxc.conf</filename> and <filename>default.conf</filename> are
-      exist both under <filename>/etc/lxc</filename> and <filename>$HOME/.config/lxc</filename>,
+      both under <filename>/etc/lxc</filename> and <filename>$HOME/.config/lxc</filename>,
       while <filename>lxc-usernet.conf</filename> is only host-wide.
     </para>
     <para>
@@ -1130,7 +1122,7 @@
 	   </para>
          </listitem>
 	 <listitem>
-	  <para><filename>/etc/init/lxc-instance.conf:</filename>
+	  <para><filename>/etc/init/lxc-instance.conf</filename>
 	  is used by <filename>/etc/init/lxc.conf</filename>
 	  to autostart a container.
 	  </para>
@@ -1312,7 +1304,7 @@
 	If you wish to use libvirt inside containers, then you will need
 	to edit that policy (which is defined in
 	<filename>/etc/apparmor.d/lxc/lxc-default-with-nesting</filename>)
-	to uncomment the following line
+	by uncommenting the following line:
 	<screen>
 mount fstype=cgroup -> /sys/fs/cgroup/**,
 	</screen>
@@ -1452,7 +1444,7 @@
 </command>
 </screen>
 
-	<para>A snapshot can be created using</para>
+	<para>A snapshot can be created using:</para>
 <screen>
 <command>
 sudo lxc-clone -s -o C1 -n C2
@@ -1588,7 +1580,7 @@
         specified by the <command>lxc.tty</command> variable, and is usually
         set to 4. Those consoles are shown on <filename>/dev/ttyN</filename>
         (for 1 &lt;= N &lt;= 4). To log into console 3 from the host,
-        use</para>
+        use:</para>
 
         <screen>
 <command>