From a06ae28c69526aaa7dc12e7abd1cbf9281e3e87f Mon Sep 17 00:00:00 2001 From: Hugo Locurcio Date: Tue, 24 Apr 2018 17:45:51 +0200 Subject: [PATCH] Improve grammar in the programmatic Composer installation page --- doc/faqs/how-to-install-composer-programmatically.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/faqs/how-to-install-composer-programmatically.md b/doc/faqs/how-to-install-composer-programmatically.md index f075df65c..02ca21d2b 100644 --- a/doc/faqs/how-to-install-composer-programmatically.md +++ b/doc/faqs/how-to-install-composer-programmatically.md @@ -2,9 +2,9 @@ As noted on the download page, the installer script contains a signature which changes when the installer code changes and as such -it should not be relied upon long term. +it should not be relied upon in the long term. -An alternative is to use this script which only works with unix utils: +An alternative is to use this script which only works with UNIX utilities: ```bash #!/bin/sh @@ -29,8 +29,8 @@ exit $RESULT The script will exit with 1 in case of failure, or 0 on success, and is quiet if no error occurs. -Alternatively if you want to rely on an exact copy of the installer you can fetch -a specific version from github's history. The commit hash should be enough to +Alternatively, if you want to rely on an exact copy of the installer, you can fetch +a specific version from GitHub's history. The commit hash should be enough to give it uniqueness and authenticity as long as you can trust the GitHub servers. For example: