[pacman-dev] [PATCH] Fix minor grammatical issues in doc/index.txt
Allan McRae
allan at archlinux.org
Thu Oct 31 21:41:24 EDT 2013
On 01/11/13 07:53, Jason St. John wrote:
> Signed-off-by: Jason St. John <jstjohn at purdue.edu>
> ---
> doc/index.txt | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/doc/index.txt b/doc/index.txt
> index 9916eab..02da213 100644
> --- a/doc/index.txt
> +++ b/doc/index.txt
> @@ -21,22 +21,22 @@ option) with a master server through the use of package databases. Prior to
> this, packages would have to be installed manually using the '\--add' and
> '\--upgrade' operations.
>
> -Version 3.0 was the switch to a two-part pacman- a backend named libalpm
> -(library for Arch Linux Package Management), and the familiar pacman frontend.
> +Version 3.0 was the switch to a two-part pacman- a back-end named libalpm
there should be a space between "pacman" and "-"
> +(library for Arch Linux Package Management), and the familiar pacman front-end.
> Speed in many cases was improved, along with dependency and conflict resolution
> being able to handle a much wider variety of cases. The switch to a
> library-based program should also make it easier in the future to develop
> alternative front ends.
>
> Version 4.0 added package signing and verification capabilities to the entire
> -makepkg/repo-add/pacman toolchain via GNUPG and GPGME.
> +makepkg/repo-add/pacman toolchain via GnuPG and GPGME.
>
> Documentation
> -------------
>
> -Manpages
> +Man Pages
> ~~~~~~~~
> -There are several manpages available for the programs, utilities, and
> +There are several man pages available for the programs, utilities, and
> configuration files dealing with pacman.
>
> * linkman:PKGBUILD[5]
> @@ -50,7 +50,7 @@ configuration files dealing with pacman.
> * linkman:repo-add[8]
> * linkman:vercmp[8]
>
> -Changelog
> +Change Log
I think this should stay one word. And I am going to cite wikipedia as
the definitive reference!
http://en.wikipedia.org/wiki/Changelog
> ~~~~~~~~~
> For a good idea of what is going on in pacman development, take a look at the
> link:https://projects.archlinux.org/pacman.git/[Git summary page] for the
> @@ -194,7 +194,7 @@ link:https://mailman.archlinux.org/pipermail/pacman-dev/[view the archives].
>
> Source Code
> ~~~~~~~~~~~
> -Development of pacman is currently done in GIT. The central repository is
> +Development of pacman is currently done in Git. The central repository is
> hosted by Arch Linux, although some of the developers have their own trees (ask
> on the above mailing lists if you are interested in finding the locations of
> these trees).
> @@ -238,7 +238,7 @@ Bugs
> ----
> If you find bugs (which is quite likely), please email them to the pacman-dev
> mailing last at mailto:pacman-dev at archlinux.org[] with specific information
> -such as your commandline, the nature of the bug, and even the package database
> +such as your command-line, the nature of the bug, and even the package database
> if it helps.
>
> You can also post a bug to the Arch Linux bug tracker
>
More information about the pacman-dev
mailing list