6 files changed, 19 insertions, 19 deletions

diff --git a/manual/getting_started/h10_install.tex b/manual/getting_started/h10_install.tex
index 81661deb6a..bb212a6504 100644
--- a/manual/getting_started/h10_install.tex
+++ b/manual/getting_started/h10_install.tex
@@ -4,7 +4,7 @@ The \playertype{} can be connected to a computer in two different modes:
   \item Universal Mass Storage (UMS): In this mode, it will appear on your computer as a regular disk. This mode works with all major operating systems, including Windows, Linux and Mac OS X.
   \item Media Transfer Protocol (MTP): In this mode, it will appear on your computer as a Media Device. MTP was created by Microsoft for use with DAPs and only works with Windows XP and Media Player 10.
 \end{itemize}
-The \playerlongtype{} is \opt{h10}{only available as a MTP device, but}\opt{h10_5gb}{available as both a MTP and as a UMS device, depending on where and when you bought it. You can tell which you have by how it appears when you connect it to a computer. If it appears as a regular disk then it is UMS. If it appears as a Media Device on Windows XP, or if it doesn't appear at all on other operating systems, then it is MTP. Even if you have a MTP \dap{}, it} can be forced into UMS mode using the UMS trick.
+The \playerlongtype{} is \opt{h10}{only available as a MTP device, but}\opt{h10_5gb}{available as both a MTP and as a UMS device, depending on where and when you bought it. You can tell which you have by how it appears when you connect it to a computer. If it appears as a regular disk then it is UMS. If it appears as a Media Device on Windows XP, or if it does not appear at all on other operating systems, then it is MTP. Even if you have a MTP \dap{}, it} can be forced into UMS mode using the UMS trick.
 
 \subsubsection{UMS mode and the UMS trick}
 It is possible to force a MTP \playertype{} to start up in UMS mode using the following procedure:
@@ -28,9 +28,9 @@ It is possible to force a MTP \playertype{} to start up in UMS mode using the fo
     \end{itemize}}
   \item Connect your \playertype{} to the computer using UMS mode and the UMS trick\opt{h10_5gb}{ if necessary}.
   \item Rename the \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}} file to \fname{OF.mi4} in the \fname{System} directory on your \playertype{}.
-    \opt{h10_5gb}{\note{If you have a Pure model \playertype{} (which doesn't have a FM radio) it is possible that this file will be called \fname{H10EMP.mi4} instead. If so, rename the \fname{H10.mi4} you downloaded in step 1 to \fname{H10EMP.mi4}.}}
+    \opt{h10_5gb}{\note{If you have a Pure model \playertype{} (which does not have a FM radio) it is possible that this file will be called \fname{H10EMP.mi4} instead. If so, rename the \fname{H10.mi4} you downloaded in step 1 to \fname{H10EMP.mi4}.}}
     \note{You should keep a safe backup of this file for use if you ever wish to switch back to the \playerman{} firmware.}
-    \note{If you can't see the \fname{System} directory, you will need to make sure your operating system is configured to show hidden files and directories.}
+    \note{If you cannot see the \fname{System} directory, you will need to make sure your operating system is configured to show hidden files and directories.}
 
   \item Copy the \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4} (or \fname{H10EMP.mi4} if you have a \playertype{} Pure)} file you downloaded to the System directory on your \dap{}.
 \end{enumerate}
diff --git a/manual/getting_started/installation.tex b/manual/getting_started/installation.tex
index 3e2611638c..fcb431b96a 100644
--- a/manual/getting_started/installation.tex
+++ b/manual/getting_started/installation.tex
@@ -13,7 +13,7 @@
 There are two ways of installing Rockbox: automated and manual. While the
 manual way is older, more tested and proven to work correctly, the
 automated installation is based on a nice graphical application that does
-almost everything that's needed for you. It is still important that you have
+almost everything that is needed for you. It is still important that you have
 an overview of the installation process to be able to select the correct
 installation options.
 
@@ -169,7 +169,7 @@ filesystem.}
         detected value, especially if you experience problems with Rockbox.}}
 
 \note{Rockbox Utility currently lacks some guiding messages. Please have a
-        look at the manual installation instructions if you're stuck
+        look at the manual installation instructions if you are stuck
         during installation.}
 
 \subsection{Manual Installation}
@@ -346,7 +346,7 @@ use.
 }
 
 \section{Updating Rockbox}
-Updating Rockbox is easy even if you don't use the Rockbox Utility.
+Updating Rockbox is easy even if you do not use the Rockbox Utility.
 Download a Rockbox build.
 (The latest release of the Rockbox software will always be available from
 \url{http://www.rockbox.org/download/}). Unzip the build to the root directory
@@ -361,9 +361,9 @@ The new build will be installed over your current build.
 \subsection{Automatic Uninstallation}
 You can uninstall Rockbox automatically by using Rockbox Utility. If you
 installed Rockbox manually you can still use Rockbox Utility for uninstallation
-but won't be able to do this selectively.
+but will not be able to do this selectively.
 
-\opt{h1xx,h300}{\note{Rockbox Utility can't uninstall the bootloader due to
+\opt{h1xx,h300}{\note{Rockbox Utility cannot uninstall the bootloader due to
 the fact that it requires a flashing procedure. To uninstall the bootloader
 completely follow the manual uninstallation instructions below.}}
 
diff --git a/manual/getting_started/ipod_install.tex b/manual/getting_started/ipod_install.tex
index 5a019b5403..97b13bfd71 100644
--- a/manual/getting_started/ipod_install.tex
+++ b/manual/getting_started/ipod_install.tex
@@ -67,7 +67,7 @@ should see the message ``[INFO] Bootloader installed successfully.'' Press
 ENTER again to exit ipodpatcher and then quit the Terminal application.
 
 \item \warn{If you received a ``Resource busy'' error from 
-ipodpatcher, then this means you didn't complete step 
+ipodpatcher, then this means you did not complete step 
 \ref{subsec:macos_umount}. Go back to Disk Utility, unmount your
 \dap{} and then run ipodpatcher again.}
 
@@ -92,7 +92,7 @@ package -- see \reference{sec:installing_fonts} for more information.
 \download{bootloader/ipod/ipodpatcher/linux32x86/ipodpatcher} (32-bit x86 
 binary) or \download{bootloader/ipod/ipodpatcher/linux64amd64/ipodpatcher} 
 (64-bit amd64 binary). You can save this anywhere you wish, but the next 
-steps will assume you've saved it in your home directory.
+steps will assume you have saved it in your home directory.
 
 \item Attach your \dap{} to your computer.
 
diff --git a/manual/getting_started/iriver_install.tex b/manual/getting_started/iriver_install.tex
index de3c8c0552..f1ee1b69e2 100644
--- a/manual/getting_started/iriver_install.tex
+++ b/manual/getting_started/iriver_install.tex
@@ -96,7 +96,7 @@
   damaged). The screen will simply display the text ``bootloader USB mode''.
   After you disconnect the \dap{} from USB the bootloader will
   continue booting Rockbox. As in bootloader USB mode the firmware
-  itself hasn't been loaded this is also a simple way of updating Rockbox.
+  itself has not been loaded this is also a simple way of updating Rockbox.
   After the disconnect the bootloader will load the updated version of
   Rockbox.
 }
diff --git a/manual/getting_started/main.tex b/manual/getting_started/main.tex
index 92576dde68..fdaf2a45f8 100644
--- a/manual/getting_started/main.tex
+++ b/manual/getting_started/main.tex
@@ -32,7 +32,7 @@ firmware. There is, however, more help available.  The Rockbox website at
 written by members of the Rockbox community and this should be your first port
 of call when looking for further help.
 
-If you can't find the information you're searching for on the Rockbox
+If you cannot find the information you are searching for on the Rockbox
 website there are a number of support channels you should have a look at.
 You can try the Rockbox forums located at \url{http://forums.rockbox.org/}.
 Another option are the mailing lists which can be found at
@@ -74,15 +74,15 @@ are used:
   or indicate a possible ``weirdness'' in rockbox that would be explained.
 }
 \warn{This is a warning. In contrast to notes mentioned above, a warning
-  should be taken more seriously. While ignoring notes won't cause any serious
-  damage ignoring warnings \emph{could} cause serious damage. If you're new to
+  should be taken more seriously. While ignoring notes will not cause any serious
+  damage ignoring warnings \emph{could} cause serious damage. If you are new to
   rockbox you should really read the warnings before doing anything that is
   warned about.
 }
 \blind{This icon marks a section that are intended especially for the blind
-  and visually impaired. As they can't
-  read the manual in the same way sighted people can do we've added some
-  additional descriptions. If you aren't blind or visually impaired you most
+  and visually impaired. As they cannot
+  read the manual in the same way sighted people can do we have added some
+  additional descriptions. If you are not blind or visually impaired you most
   likely can completely skip these blocks. To make this easier, there is an
   icon shown in the margin on the right.
 }
diff --git a/manual/getting_started/sansa_install.tex b/manual/getting_started/sansa_install.tex
index 989878e36a..8b333e3ab2 100644
--- a/manual/getting_started/sansa_install.tex
+++ b/manual/getting_started/sansa_install.tex
@@ -60,7 +60,7 @@ should see the message ``[INFO] Bootloader installed successfully.'' Press
 ENTER again to exit sansapatcher and then quit the Terminal application.
 
 \item \warn{If you received a ``Resource busy'' error from 
-sansapatcher, then this means you didn't complete step 
+sansapatcher, then this means you did not complete step 
 \ref{subsec:macos_umount}. Go back to Disk Utility, unmount your
 \dap{} and then run sansapatcher again.}
 
@@ -77,7 +77,7 @@ Wait for it to connect, and then eject and unplug it in the normal way.
 \download{bootloader/sandisk-sansa/sansapatcher/linux32x86/sansapatcher} (32-bit x86 
 binary) or \download{bootloader/sandisk-sansa/sansapatcher/linux64amd64/sansapatcher} 
 (64-bit amd64 binary). You can save this anywhere you wish, but the next 
-steps will assume you've saved it in your home directory.
+steps will assume you have saved it in your home directory.
 
 \item Attach your \dap{} to your computer.