Fix a few typos

configuration/network-bridge-support.md

@@ -11,9 +11,9 @@ redirect_from:
 Network Bridge Support (EXPERIMENTAL and UNSUPPORTED)
 =====================================================
 
-The Qubes developpement team does not support bridging the network interfaces found in NetVM and don't plan to support it at all. Several reasons for that:
+The Qubes development team does not support bridging the network interfaces found in NetVM and don't plan to support it at all. Several reasons for that:
 
--   Using a bridged VM is almost only necessary for developpers testing or working on OSI layer 2 or layer 3 tools (MAC or routing protocols). If not for testing, such tools are almost only used directly on routers ...).
+-   Using a bridged VM is almost only necessary for developers testing or working on OSI layer 2 or layer 3 tools (MAC or routing protocols). If not for testing, such tools are almost only used directly on routers ...).
 -   Most of these tools can be anyway used directly inside the NetVM, which has direct access to the network card.
 -   It is also possible to use a secondary network card plugged into a specific development VM.
 -   Such a setup could break security features of Qubes such as AppVM firewalling.
@@ -23,7 +23,7 @@ Now if you really want to work with OSI layer2 / layer 3 tools, that you don't h
 Qubes manager patch (Qubes R2B2)
 --------------------------------
 
-The following patches can be applied to the Qubes Manager GUI in order to add an option to easily bridge a VM. Use it at your own risk. If the patch breaks the Qubes Manager, you can try to restore the qubes packages:
+The following patches can be applied to the Qubes Manager GUI in order to add an option to easily bridge a VM. Use it at your own risk. If the patch breaks the Qubes Manager, you can try to restore the Qubes packages:
 
 ~~~
 # qubes-dom-update qubes-core-dom0 qubes-manager
@@ -75,7 +75,7 @@ Modify manually the Template you use for your NetVM (not the NetVM itself). This
     -A FORWARD -j DROP
     ~~~
 
-Ensure that the IP addresses used by default in qubes are in the form 10.137.1.\* or 10.137.2.\* by running ifconfig. Of course, this setup won't work with IPv6.
+Ensure that the IP addresses used by default in Qubes are in the form 10.137.1.\* or 10.137.2.\* by running ifconfig. Of course, this setup won't work with IPv6.
 
 Now you need to restart the NetVM and FirewallVM or only iptables in both VMs if you prefer:
 

configuration/postfix.md

@@ -18,7 +18,7 @@ Installation
 
 `yum install postfix procmail make`
 
-Procmail is not strictly neccessary, but is useful to sort your incoming mail, for example to put each mailing list in its own directory. Make is also not neccessary, but is used to keep Postfix lookup tables. You should also check `alternatives` command, to see if it is the default `mta`. It probably is not. You may need to `yum remove ssmtp` or something.
+Procmail is not strictly necessary, but is useful to sort your incoming mail, for example to put each mailing list in its own directory. Make is also not necessary, but is used to keep Postfix lookup tables. You should also check `alternatives` command, to see if it is the default `mta`. It probably is not. You may need to `yum remove ssmtp` or something.
 
 Configuration
 -------------
@@ -104,7 +104,7 @@ your.mail@exmaple.com         [mail.example.com]:submission
 your.other@mail.com         [smtp.mail.com]:smtp
 ~~~
 
-`/usr/local/etc/postfix/saslpass`. Here you put passwords to abovementioned servers. It depends on provider if you need to put whole email as username or just the part before `@`.
+`/usr/local/etc/postfix/saslpass`. Here you put passwords to above mentioned servers. It depends on provider if you need to put whole email as username or just the part before `@`.
 
 ~~~
 [mail.example.com]:submission     your.mail:y0urP4ssw0rd
@@ -118,7 +118,7 @@ spamdomain1.com       DISCARD
 spamdomain2.com     DISCARD
 ~~~
 
-Now run `make` in `/usr/local/etc/postfix`. It will hopefully compile four abovementioned lookup tables (`generic.db`, `sender_relay.db`, `saslpass.db` and `sender_access`).
+Now run `make` in `/usr/local/etc/postfix`. It will hopefully compile four above mentioned lookup tables (`generic.db`, `sender_relay.db`, `saslpass.db` and `sender_access`).
 
 ### procmail
 

configuration/resize-disk-image.md

@@ -11,8 +11,7 @@ redirect_from:
 Resize Disk Image
 -----------------
 
-There are several disk images which can be easily extended.
- But pay attention to the overall consumed space of your sparse disk images.
+There are several disk images which can be easily extended. But pay attention to the overall consumed space of your sparse disk images.
 
 ### Private disk image
 

configuration/rxvt.md

@@ -21,7 +21,7 @@ Installation
 Xresources
 ----------
 
-In TemplateVM create file `/etc/X11/Xresources.urxvt` and paste config below. `!`-lines are comments and may be left out. `#`-lines are directives to CPP (C preprocessor) and are neccessary. This shouldn't go to `/etc/X11/Xresources`, because that file is not preprocessed by default.
+In TemplateVM create file `/etc/X11/Xresources.urxvt` and paste config below. `!`-lines are comments and may be left out. `#`-lines are directives to CPP (C preprocessor) and are necessary. This shouldn't go to `/etc/X11/Xresources`, because that file is not preprocessed by default.
 
 ~~~
 ! CGA colour palette

configuration/salt/index.md

@@ -50,7 +50,7 @@ A *module* is a Python extension to salt that is responsible for actually
 enforcing the state in a particular area. It exposes some *imperative* functions
 for administrator. For example there is `system` module that has `system.halt`
 function that, when issued, will immediately halt the computer. There is another
-function called `state.highstate` which will synchronise the state of the system
+function called `state.highstate` which will synchronize the state of the system
 with the administrator's will.