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>

2 files changed, 4 insertions, 4 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.
 
diff --git a/src/pacman/pacman.c b/src/pacman/pacman.c
index 72a72ba5..c542a989 100644
--- a/src/pacman/pacman.c
+++ b/src/pacman/pacman.c
@@ -65,8 +65,8 @@ static void usage(int op, const char * const myname)
 	/* prefetch some strings for usage below, which moves a lot of calls
 	 * out of gettext. */
 	char const * const str_opt = _("options");
-	char const * const str_file = _("file");
-	char const * const str_pkg = _("package");
+	char const * const str_file = _("file(s)");
+	char const * const str_pkg = _("package(s)");
 	char const * const str_usg = _("usage");
 	char const * const str_opr = _("operation");