[release-notes] typos

John J. McDonough jjmcd at fedoraproject.org
Tue Oct 11 00:36:28 UTC 2011


commit 869d91783ea307c38f87ff105475709478b6076b
Author: John J. McDonough <jjmcd at fedoraproject.org>
Date:   Mon Oct 10 20:35:41 2011 -0400

    typos

 en-US/Database_Servers.xml |   18 +++++++++++-------
 en-US/System_Daemons.xml   |    2 +-
 2 files changed, 12 insertions(+), 8 deletions(-)
---
diff --git a/en-US/Database_Servers.xml b/en-US/Database_Servers.xml
index 435001e..afc1bd2 100644
--- a/en-US/Database_Servers.xml
+++ b/en-US/Database_Servers.xml
@@ -21,7 +21,7 @@
     </indexterm>
     
     <para>
-      MySQL and PostgreSQL have been updated to use native systemd unit files for startup, in place of the SysV-style init scripts.  This should eliminate various unfortunate problems that occurred in Fedora 15 due to systemd's rather poor handling of SysV scripts.  Also, handling of cases where the database server is slow to start up is significantly better than it ever was in the SysV scripts, since in systemd there is no reason not to wait until the server is really ready. 
+      MySQL and PostgreSQL have been updated to use native <package>systemd</package> unit files for startup, in place of the SysV-style init scripts.  This should eliminate various unfortunate problems that occurred in Fedora 15 due to <package>systemd</package>'s rather poor handling of SysV scripts.  Also, handling of cases where the database server is slow to start up is significantly better than it ever was in the SysV scripts, since in <package>systemd</package> there is no reason not to wait until the server is really ready. 
     </para>
   </section>
   <section>
@@ -32,25 +32,29 @@
     </indexterm>
     
     <para>
-      The "service postgresql initdb" and "service postgresql upgrade" actions that were supported by the SysV init script cannot be provided by the systemd unit file.  There is a new standalone script postgresql-setup that provides these functions.  For example, to initialize a new postgresql database, do something like 
+      The <command>service postgresql initdb</command> and <command>service postgresql upgrade</command> actions that were supported by the SysV init script cannot be provided by the <package>systemd</package> unit file.  There is a new standalone script, <filename>postgresql-setup</filename> that provides these functions.  For example, to initialize a new postgresql database, do something like 
     </para>
     
     <para>
 
-      <programlisting format="linespecific"> sudo postgresql-setup initdb </programlisting>
+<screen>
+sudo postgresql-setup initdb 
+</screen>
       
     </para>
     <para>
-    If you need to run more than one postgresql server on the same machine, you can duplicate and modify the <programlisting format="linespecific">postgresql.service</programlisting> file, as is customary with systemd services.  (Remember that custom service files should go into <programlisting format="linespecific">/etc/systemd/system/</programlisting> not <programlisting format="linespecific">/lib/systemd/system/</programlisting>.)  Notice that PGDATA and PGPORT settings for alternate servers must now be specified in the custom service files; there is no longer any use of files in <programlisting format="linespecific">/etc/sysconfig/pgsql/</programlisting>. </para>
-    <para>You can use postgresql-setup for an alternate server by adding the name of the new service file to the command, for instance </para>
+    If you need to run more than one postgresql server on the same machine, you can duplicate and modify the <filename>postgresql.service</filename> file, as is customary with <package>systemd</package> services.  (Remember that custom service files should go into <filename>/etc/systemd/system/</filename> not <filename>/lib/systemd/system/</filename>.)  Notice that PGDATA and PGPORT settings for alternate servers must now be specified in the custom service files; there is no longer any use of files in <filename>/etc/sysconfig/pgsql/</filename>. </para>
+    <para>You can use <filename>postgresql-setup</filename> for an alternate server by adding the name of the new service file to the command, for instance </para>
     
     <para>
 
-      <programlisting format="linespecific"> sudo postgresql-setup initdb myservice </programlisting>
+<screen>
+sudo postgresql-setup initdb myservice 
+</screen>
       
     </para>
     <para>
-    postgresql-setup will then extract the PGDATA setting from that service file instead of <programlisting format="linespecific">postgresql.service</programlisting>. </para>
+    <filename>postgresql-setup</filename> will then extract the PGDATA setting from that service file instead of <filename>postgresql.service</filename>. </para>
   </section>
 </section>
 
diff --git a/en-US/System_Daemons.xml b/en-US/System_Daemons.xml
index 8de1a61..8f0db8e 100644
--- a/en-US/System_Daemons.xml
+++ b/en-US/System_Daemons.xml
@@ -44,7 +44,7 @@
     </indexterm>
     
     <para>
-      Fedora 16 does not ship with the <package>HAL</package> daemon and <emphasis>libhal</emphasis>, which have been replaced with <emphasis>udisks</emphasis>, <emphasis>upower</emphasis> and <emphasis>libudev</emphasis>. If a specific application require libhal to function, please file a bug against it to be ported to the new technology. 
+      Fedora 16 does not ship with the <package>HAL</package> daemon and <emphasis>libhal</emphasis>, which have been replaced with <emphasis>udisks</emphasis>, <emphasis>upower</emphasis> and <emphasis>libudev</emphasis>. If a specific application requires libhal to function, please file a bug against it to be ported to the new technology. 
     </para>
   </section>
 </section>


More information about the docs-commits mailing list