[deployment-guide: 129/185] fixed a number of typos across various chapters
Jaromir Hradilek
jhradile at fedoraproject.org
Sun May 15 21:22:02 UTC 2011
commit 659af3edfba92880a0add9f467077ba2acd52405
Author: Martin Prpic <mprpic at redhat.com>
Date: Fri Mar 18 12:29:24 2011 +0100
fixed a number of typos across various chapters
en-US/Automatic_Bug_Reporting_Tool_ABRT.xml | 4 ++--
en-US/Automating_System_Tasks.xml | 2 +-
en-US/Mail_Servers.xml | 4 ++--
en-US/OpenLDAP.xml | 2 +-
en-US/PackageKit.xml | 2 +-
en-US/Printer_Configuration.xml | 2 +-
en-US/RPM.xml | 2 +-
en-US/SSSD.xml | 2 +-
8 files changed, 10 insertions(+), 10 deletions(-)
---
diff --git a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
index ff57e20..1de73d6 100644
--- a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
+++ b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
@@ -582,7 +582,7 @@ export <varname>VISUAL</varname>=<userinput>emacs</userinput>
<section id="configuring">
<title>Configuring ABRT</title>
<para>
- <application>ABRT</application>'s main configuration file is <filename>/etc/abrt/abrt.conf</filename>. <application>ABRT</application> plugins can be configured through their config files, located in the <filename>/etc/abrt/plugins/</filename> directory.</para>
+ <application>ABRT</application>'s main configuration file is <filename>/etc/abrt/abrt.conf</filename>. <application>ABRT</application> plugins can be configured through their configuration files, located in the <filename>/etc/abrt/plugins/</filename> directory.</para>
<important>
<title>Important</title>
<para>After changing and saving the <filename>/etc/abrt/abrt.conf</filename> configuration file, you must restart the <systemitem class="daemon">abrtd</systemitem> daemon—as root—for the new settings to take effect:</para>
@@ -723,7 +723,7 @@ export <varname>VISUAL</varname>=<userinput>emacs</userinput>
<note>
<title>Note</title>
<para>
- When the <package>abrt-desktop</package> package is installed, it creates a new system user and and a group, both named <systemitem class="username">abrt</systemitem>. This user is used by the <systemitem class="daemon">abrtd</systemitem> daemon for various things, for example, as the owner:group of <filename>/var/spool/abrt/*</filename> directories.
+ When the <package>abrt-desktop</package> package is installed, it creates a new system user and a group, both named <systemitem class="username">abrt</systemitem>. This user is used by the <systemitem class="daemon">abrtd</systemitem> daemon for various things, for example, as the owner:group of <filename>/var/spool/abrt/*</filename> directories.
</para>
</note>
</listitem>
diff --git a/en-US/Automating_System_Tasks.xml b/en-US/Automating_System_Tasks.xml
index 6b366d6..4f7de76 100644
--- a/en-US/Automating_System_Tasks.xml
+++ b/en-US/Automating_System_Tasks.xml
@@ -23,7 +23,7 @@
</indexterm>
<para>Both, Cron and Anacron, are daemons that can be used to schedule the execution of recurring tasks according to a combination of the time, day of the month, month, day of the week, and week.</para>
<para>Cron assumes that the system is on continuously. If the system is not on when a job is scheduled, it is not executed. Cron allows jobs to be run as often as every minute. Anacron does not assume the system is always on, remembers every scheduled job, and executes it the next time the system is up. However, Anacron can only run a job once a day.
- To schedule reccurring jobs, refer to <xref linkend="s2-configuring-anacron-jobs"/> or <xref linkend="s2-configuring-cron-jobs"/>. To schedule one-time jobs, refer to <xref linkend="s1-autotasks-at-batch"/>.</para>
+ To schedule recurring jobs, refer to <xref linkend="s2-configuring-anacron-jobs"/> or <xref linkend="s2-configuring-cron-jobs"/>. To schedule one-time jobs, refer to <xref linkend="s1-autotasks-at-batch"/>.</para>
<para>To use the cron service, the <filename>cronie</filename> RPM package must be installed and the <command>crond</command> service must be running. <filename>anacron</filename> is a sub-package of <filename>cronie</filename>. To determine if these packages are installed, use the <command>rpm -q cronie cronie-anacron</command> command. </para>
<section id="s2-autotasks-cron-service">
<title>Starting and Stopping the Service</title>
diff --git a/en-US/Mail_Servers.xml b/en-US/Mail_Servers.xml
index 2e7863c..175c623 100644
--- a/en-US/Mail_Servers.xml
+++ b/en-US/Mail_Servers.xml
@@ -1570,11 +1570,11 @@ connect = 143
<primary>email</primary>
<secondary>additional resources</secondary>
<tertiary>related books</tertiary>
- </indexterm>
+ </indexterm
<itemizedlist>
<listitem>
<para>
- <citetitle>Sendmail Milters: A Guide for Fighting Spam</citetitle> by Bryan Costales and Marcia Flynt; Addison-Wesley — A good Sendmail guide that can help you customise your mail filters.</para>
+ <citetitle>Sendmail Milters: A Guide for Fighting Spam</citetitle> by Bryan Costales and Marcia Flynt; Addison-Wesley — A good Sendmail guide that can help you customize your mail filters.</para>
</listitem>
<listitem>
<para>
diff --git a/en-US/OpenLDAP.xml b/en-US/OpenLDAP.xml
index c36fe0b..9cfa6c6 100644
--- a/en-US/OpenLDAP.xml
+++ b/en-US/OpenLDAP.xml
@@ -23,7 +23,7 @@
<systemitem class="protocol">LDAP</systemitem> (Lightweight Directory Access Protocol) is a set of open protocols used to access centrally stored information over a network. It is based on the <systemitem class="protocol">X.500</systemitem> standard for directory sharing, but is less complex and resource-intensive. For this reason, LDAP is sometimes referred to as <quote>X.500 Lite</quote>.
</para>
<para>
- Like X.500, LDAP organizes information in a hierarchal manner using directories. These directories can store a variety of information such as names, addresses, or phone numbers, and can even be used in a manner similar to the <firstterm>Network Information Service</firstterm> (<acronym>NIS</acronym>), enabling anyone to access their account from any machine on the LDAP enabled network.
+ Like X.500, LDAP organizes information in a hierarchical manner using directories. These directories can store a variety of information such as names, addresses, or phone numbers, and can even be used in a manner similar to the <firstterm>Network Information Service</firstterm> (<acronym>NIS</acronym>), enabling anyone to access their account from any machine on the LDAP enabled network.
</para>
<para>
LDAP is commonly used for centrally managed users and groups, user authentication, or system configuration. It can also serve as a virtual phone directory, allowing users to easily access contact information for other users. Additionally, it can refer a user to other LDAP servers throughout the world, and thus provide an ad-hoc global repository of information. However, it is most frequently used within individual organizations such as universities, government departments, and private companies.
diff --git a/en-US/PackageKit.xml b/en-US/PackageKit.xml
index f0254d9..fe9ba7c 100644
--- a/en-US/PackageKit.xml
+++ b/en-US/PackageKit.xml
@@ -182,7 +182,7 @@
format="PNG" />
</imageobject>
<textobject>
- <para>viewing packagekit's add/remove softvware window</para>
+ <para>viewing packagekit's add/remove software window</para>
</textobject>
</mediaobject>
</figure>
diff --git a/en-US/Printer_Configuration.xml b/en-US/Printer_Configuration.xml
index c371f17..9a9a7f8 100644
--- a/en-US/Printer_Configuration.xml
+++ b/en-US/Printer_Configuration.xml
@@ -1145,7 +1145,7 @@ Ben-62 root 1024 Tue 08 Feb 2011 16:45:42 GMT
</indexterm>-->
<para>
- If you want to cancel a print job, find the job number of the request with the command <command>lpstat -o</command> and then use the command <command>cancel <replaceable>job number</replaceable></command>. For example, <command>cancel 60</command> would cancel the print job in <xref linkend="lpq-example"/>. You can not cancel print jobs that were started by other users with the <command>cancel</command> command. However, you can enforce deletion of such job by issuing the <command>cancel -U root <replaceable>job_number</replaceable></command> command. To prevent such cancelling change the printer operation policy to <literal>Authenticated</literal> to force root authentication.
+ If you want to cancel a print job, find the job number of the request with the command <command>lpstat -o</command> and then use the command <command>cancel <replaceable>job number</replaceable></command>. For example, <command>cancel 60</command> would cancel the print job in <xref linkend="lpq-example"/>. You can not cancel print jobs that were started by other users with the <command>cancel</command> command. However, you can enforce deletion of such job by issuing the <command>cancel -U root <replaceable>job_number</replaceable></command> command. To prevent such canceling change the printer operation policy to <literal>Authenticated</literal> to force root authentication.
</para>
<!-- <indexterm significance="normal">
<primary>printer configuration</primary>
diff --git a/en-US/RPM.xml b/en-US/RPM.xml
index 3a3fc3c..d93ccea 100644
--- a/en-US/RPM.xml
+++ b/en-US/RPM.xml
@@ -82,7 +82,7 @@
<varlistentry>
<term>Pristine Sources <indexterm><primary>packages</primary>
<secondary>RPM</secondary>
- <tertiary>prisitne sources</tertiary>
+ <tertiary>pristine sources</tertiary>
</indexterm>
</term>
<listitem>
diff --git a/en-US/SSSD.xml b/en-US/SSSD.xml
index 632d845..4076428 100644
--- a/en-US/SSSD.xml
+++ b/en-US/SSSD.xml
@@ -1317,7 +1317,7 @@ krb5_auth_timeout = 15
</listitem>
<listitem>
<para>
- Make the <filename>/etc/openldap/ldap.keytab</filename> file read-writeable for the <systemitem class="username">ldap</systemitem> user and readable for the <systemitem class="username">ldap</systemitem> group only.
+ Make the <filename>/etc/openldap/ldap.keytab</filename> file read-writable for the <systemitem class="username">ldap</systemitem> user and readable for the <systemitem class="username">ldap</systemitem> group only.
</para>
</listitem>
</orderedlist>
More information about the docs-commits
mailing list