[system-administrators-guide/21] Fixing Title Case

[stephenw]

commit cb0ddf639e54daeca1b2bd11e280914baec6f52b
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Fri Jan 16 15:32:43 2015 +0100

    Fixing Title Case

 en-US/TigerVNC.xml |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)
---
diff --git a/en-US/TigerVNC.xml b/en-US/TigerVNC.xml
index edf76e6..488972b 100644
--- a/en-US/TigerVNC.xml
+++ b/en-US/TigerVNC.xml
@@ -152,7 +152,7 @@ You can also enable the service to start automatically at system start. Then, wh
 At this point, other users are able to use a VNC viewer program to connect to the VNC server using the display number and password defined. Provided a graphical desktop is installed, an instance of that desktop will be displayed. It will not be the same instance as that currently displayed on the target machine. 
 	</para>
 	<section id="starting-vncserver-2displays">
-		<title>Configuring VNC Server for two users and two different displays</title>
+		<title>Configuring VNC Server for Two Users and Two Different Displays</title>
 	<para>
 For the two configured VNC servers, vncserver-USER_1 at .service and vncserver-USER_2 at .service,
 you can enable different display numbers. For example, the following commands will cause a VNC server for USER_1 to
@@ -165,7 +165,7 @@ start on display 3, and a VNC server for USER_2 to start on display 5:
 	</section>
   </section>
   <section id="terminating-vnc-session">
-  	<title>Terminating a VNC session</title>
+  	<title>Terminating a VNC Session</title>
 	<para>
 Similarly to enabling the <systemitem>vncserver</systemitem> service, you can disable
 the automatic start of the service at system start:
@@ -210,7 +210,7 @@ In order to do so, issue the <command>vncviewer</command> command in the followi
 Where <replaceable>address</replaceable> is an <systemitem class="protocol">IP</systemitem> or host name.
 		</para>
 <example id="connecting-to-vncserver">
-	<title>One Client Connecting to vncserver</title>
+	<title>One Client Connecting to VNC Server</title>
 	<para>
 With the <systemitem class="protocol">IP</systemitem> address <systemitem class="ipaddress">192.168.0.4</systemitem> and display number <emphasis>3</emphasis>
 the command looks as follows:
@@ -303,7 +303,7 @@ A port can be removed using the <command>firewall-cmd --zone=<replaceable>zone</
   </section>
   </section>
   <section id="s1-using_ssh">
-             <title>Connecting to VNC Server using SSH</title>
+             <title>Connecting to VNC Server Using SSH</title>
 		<para>
 <acronym>VNC</acronym> is a clear text network protocol with no security against possible attacks on the communication. To make the communication secure, you can encrypt your server-client connection by using the <option>-via</option> option. This will create an <systemitem class="protocol">SSH</systemitem> tunnel between the VNC server and the client.
 		</para>
@@ -314,7 +314,7 @@ The format of the command to encrypt a VNC server-client connection is as follow
 <command><computeroutput>~]$&nbsp;</computeroutput><userinput>vncviewer -via <replaceable>user</replaceable>@<replaceable>host</replaceable>:<replaceable>display_number</replaceable></userinput></command>
 </screen>
 	<example id="using-via">
-	<title>Using the -via option</title>
+	<title>Using the -via Option</title>
 
   <procedure>
   <step>
@@ -338,7 +338,7 @@ A window with a remote desktop appears on your screen.
   </procedure>
 	</example>
 
-    <bridgehead id="bh-Restricting_VNC_access">Restricting VNC access</bridgehead>
+    <bridgehead id="bh-Restricting_VNC_access">Restricting VNC Access</bridgehead>
 	<para>
 If you prefer only encrypted connections, you can prevent unencrypted connections
 altogether by using the <option>-localhost</option> option in the <systemitem class="service">systemd.service</systemitem>