Merge pull request #4 from ItsFrankieD/patch-1

Update README.md

Author: rsanzante

README.md

@@ -3,21 +3,21 @@
 This script sets the permissions and ownership of the files of a Drupal
 installation.
 
-This is loosely based on the information provided by Drupal documentation page
+This is loosely based on the information provided by the Drupal documentation page
 "[Securing file permissions and ownership](https://www.drupal.org/node/244924)".
 
 ## Details
 
 For security reasons, the code files of a website should not be writable. At the
 same time, the website should be able to create files (for example, when a user
-uploads an image). This means that there two types of files and folders: content
+uploads an image). This means that there are two types of files and folders: content
 and code.
 
-There will be two users involved: a regular UNIX user, we'll call they the
+There will be two users involved: a regular UNIX user, we'll call them the
 deploy user, that is in charge of managing the code (typically deploying new
 releases), and the user under which the web server process is running.
 
-This scripts tries to secure the site using the following scheme:
+This script tries to secure the site using the following scheme:
 
   - Code is owned by the deploy user and by the web server's
     group. Deploy user can write, web server group only read.
@@ -40,9 +40,9 @@ In UNIX terms:
 
 ## Installation
 
-Clone or donwload the repository content to your server.
+Clone or download the repository content to your server.
 
-Link to `drupal_fix_permissions.sh` in the `/usr/local/bin` or another folder present in users' PATH.
+Link to `drupal_fix_permissions.sh` in the `/usr/local/bin` or another folder present in the user's PATH.
 
 If you are using `autofix-drupal-perms.sh`, link it as well. Because it expects `drupal_fix_permissions.sh` to be at `/usr/local/bin` make sure that path exists or edit the autofix script.
 
@@ -71,10 +71,10 @@ folder and using `deploy` as the deploy user.
 
 ## Strategy
 
-The scripts checks if the target folder is a Drupal installation and stops if
+The script checks if the target folder is a Drupal installation and stops if
 it is not detected.
 
-Once checked, it fixes the ownership of all folder and files (because it is the
+Once checked, it fixes the ownership of all folders and files (because it is the
 same for content and code). Then, it fixes the code and later the content.
 
 The script assumes that `files` and `private` folders under `sites` are content
@@ -91,8 +91,8 @@ folder and fixes permissions accordingly: it fixes ownership (owner: deploy
 user, group: web server) and removes any permissions for other users.
 
 It doesn't apply standard permissions of code files because in `vendor` folders
-there are some files that needs to be executable. It would be hard to detect all
-the cases that needs executable permissions so the script doesn't handle
+some files need to be executable. It would be hard to detect all
+the cases that need executable permissions so the script doesn't handle
 permissions for the owner or the group and just removes all permissions for
 other users.
 
@@ -103,15 +103,15 @@ run again to remove all permissions on other users.
 
 ## Performance
 
-The script only changes the files and folder with the wrong permissions or
+The script only changes the files and folders with the wrong permissions or
 ownership, making it very fast when only a few files or folders need a fix. For
 really big installations this is very important as other scripts apply the
 permissions and ownership regardless are needed o not.
 
 ## Root permissions
 
-Giving root permissions to regular user is dangerous. Luckily, there's a simple
-script, `autofix-drupal-perms.sh`, to allow regular users fix their sites
+Giving root permissions to regular users is dangerous. Luckily, there's a simple
+script, `autofix-drupal-perms.sh`, to allow regular users to fix their sites
 without risking the security.
 
 This script has no parameters, so it can be easily added to the sudoers. When