summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNagy Gabor <ngaba@bibl.u-szeged.hu>2009-05-22 01:06:33 +0200
committerDan McGee <dan@archlinux.org>2009-06-01 21:59:03 -0500
commit1b4135ca5d0654d18398d648ba48ecf14caa2289 (patch)
tree01814721fe91f3a912b24092d723e92c9e036e3a /doc
parent6360fe01007f34b1fa2285b6c741d2dffb81da28 (diff)
Change package to package(s) and file to file(s) in documentation
The pacman --help pages and the manual suggested that only one package can be upgraded/removed per transaction. Signed-off-by: Nagy Gabor <ngaba@bibl.u-szeged.hu> Signed-off-by: Dan McGee <dan@archlinux.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/pacman.8.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/pacman.8.txt b/doc/pacman.8.txt
index 4582be5f..5fa576bd 100644
--- a/doc/pacman.8.txt
+++ b/doc/pacman.8.txt
@@ -39,7 +39,7 @@ Operations
list. See <<QO,Query Options>> below.
*-R, \--remove*::
- Remove a package from the system. Groups can also be specified to be
+ Remove package(s) from the system. Groups can also be specified to be
removed, in which case every package in that group will be removed.
Files belonging to the specified package will be deleted, and the
database will be updated. Most configuration files will be saved
@@ -75,7 +75,7 @@ to determine which packages need upgrading. This behavior operates as follows:
1 < 1.0 < 1.1 < 1.1.1 < 1.2 < 2.0 < 3.0.0
*-U, \--upgrade*::
- Upgrade or add a package to the system. Either a URL or file path can be
+ Upgrade or add package(s) to the system. Either a URL or file path can be
specified. This is a ``remove-then-add'' process. See <<HCF,Handling Config
Files>> for an explanation on how pacman takes care of config files.