[yum-commits] docs/yum.8 docs/yum.conf.5

[zpavlas at osuosl.org]

 docs/yum.8      |   10 +++++-----
 docs/yum.conf.5 |    4 ++--
 2 files changed, 7 insertions(+), 7 deletions(-)

New commits:
commit c6289927f1136779b817d8708e56abe4c85b9714
Author: Jan Pokorný <jpokorny at redhat.com>
Date:   Tue Jun 11 09:49:21 2013 +0200

    Fix superfluous dots after "via" preposition in man pages
    
    Related: rhbz#972764
    
    Signed-off-by: Jan Pokorný <jpokorny at redhat.com>

diff --git a/docs/yum.8 b/docs/yum.8
index 76bbdd5..1c6a27b 100644
--- a/docs/yum.8
+++ b/docs/yum.8
@@ -288,9 +288,9 @@ meaning of these markers is:
 .br
 "+" = Package isn't installed, but will be the next time you run "yum upgrade" or "yum group upgrade foo"
 .br
-" " = Package is installed, but wasn't installed via. the group (so "group remove foo" won't remove it).
+" " = Package is installed, but wasn't installed via the group (so "group remove foo" won't remove it).
 .br
-"=" = Package is installed, and was installed via. the group.
+"=" = Package is installed, and was installed via the group.
 
 "\fBgroup summary\fP" is used to give a quick summary of how many groups
 are installed and available.
@@ -499,7 +499,7 @@ transactions, "last" refers to transaction 250, and "last-4" refers to
 transaction 246).
 The redo command can also take some optional arguments before you specify the
 transaction. "force-reinstall" tells it reinstall any packages that were
-installed in that transaction (via. install, upgrade or downgrade).
+installed in that transaction (via install, upgrade or downgrade).
 "force-remove" tells it to forcibly remove any packages that were updated or
 downgraded.
 
@@ -522,7 +522,7 @@ The sync commands allows you to change the rpmdb/yumdb data stored for any
 installed packages, to whatever is in the current rpmdb/yumdb (this is mostly
 useful when this data was not stored when the package went into the history DB).
 
-In "history list" you can change the behaviour of the 2nd column via. the
+In "history list" you can change the behaviour of the 2nd column via the
 configuration option history_list_view.
 
 In "history list" output the Altered column also gives some extra information
@@ -551,7 +551,7 @@ end of the package column in the packages-list command).
 This command will re-load a saved yum transaction file, this allows you to
 run a transaction on one machine and then use it on another.
 The two common ways to get a saved yum transaction file are from
-"yum -q history addon-info last saved_tx" or via. the automatic saves in
+"yum -q history addon-info last saved_tx" or via the automatic saves in
 $TMPDIR/yum_save_tx.* when a transaction is solved but not run.
 
 Running the command without an argument, or a directory as an argument will
diff --git a/docs/yum.conf.5 b/docs/yum.conf.5
index 39c2769..d8d60a5 100644
--- a/docs/yum.conf.5
+++ b/docs/yum.conf.5
@@ -64,7 +64,7 @@ options are: 'critical', 'emergency', 'error', 'warn' and 'debug'.
 .IP
 \fBprotected_packages\fR
 This is a list of packages that yum should never completely remove. They are
-protected via. Obsoletes as well as user/plugin removals.
+protected via Obsoletes as well as user/plugin removals.
 
 The default is: yum glob:/etc/yum/protected.d/*.conf
 So any packages which should be protected can do so by including a file in 
@@ -180,7 +180,7 @@ will also apply to kernel-debug-devel, etc.
 Number of packages listed in installonlypkgs to keep installed at the same
 time. Setting to 0 disables this feature. Default is '0'. Note that this
 functionality used to be in the "installonlyn" plugin, where this option was
-altered via. tokeep.
+altered via tokeep.
 Note that as of version 3.2.24, yum will now look in the yumdb for a installonly
 attribute on installed packages. If that attribute is "keep", then they will
 never be removed.