[anjuta] manual: bgo#664058 - couple of spelling fixes

[Johannes Schmid <jhs src gnome org>]

commit 0152e62101a480ef8bead5803329176b6a73f7f2
Author: Christian Kirchbach <Christian Kirbach googlemail com>
Date:   Sun Nov 20 14:16:54 2011 +0100

    manual: bgo#664058 - couple of spelling fixes

 manuals/anjuta-manual/C/autotools-build-clean.page |   10 +++++-----
 .../anjuta-manual/C/autotools-build-compile.page   |    2 +-
 .../C/autotools-build-configure-dialog.page        |    2 +-
 .../anjuta-manual/C/autotools-build-install.page   |    2 +-
 .../C/autotools-build-preferences-dialog.page      |   10 +++++-----
 manuals/anjuta-manual/C/run-parameters-dialog.page |    6 +++---
 6 files changed, 16 insertions(+), 16 deletions(-)
---
diff --git a/manuals/anjuta-manual/C/autotools-build-clean.page b/manuals/anjuta-manual/C/autotools-build-clean.page
index 7f5c837..7fd86a5 100644
--- a/manuals/anjuta-manual/C/autotools-build-clean.page
+++ b/manuals/anjuta-manual/C/autotools-build-clean.page
@@ -19,16 +19,16 @@
 
   <title>Clean targets</title>
 
-  <p>It can be useful to delete all files created by the build process. By
-  example if the all dependencies are not taken into account and
+  <p>It can be useful to delete all files created by the build process. For
+  example, if all dependencies are not taken into account and
   a modified file does not trigger a recompiling as it should, deleting
-  all files will fix this. There are several way to do this</p>
+  all files will fix this. There are several ways to do this</p>
   <steps>
     <item>
       <p>
         From the <gui>main menu</gui>, select <guiseq><gui>Build</gui>
-        <gui>Clean</gui></guiseq> to delete all files build in the
-        same directory than the current edited file.
+        <gui>Clean</gui></guiseq> to delete all files built in the
+        same directory as the current edited file.
       </p>
     </item>
   </steps>
diff --git a/manuals/anjuta-manual/C/autotools-build-compile.page b/manuals/anjuta-manual/C/autotools-build-compile.page
index 49e0aa4..2102e17 100644
--- a/manuals/anjuta-manual/C/autotools-build-compile.page
+++ b/manuals/anjuta-manual/C/autotools-build-compile.page
@@ -20,7 +20,7 @@
   <title>Compile files</title>
 
     <p>
-      Most programming language allow you to compile an individual source file.
+      Most programming languages allow you to compile an individual source file.
       It reads the file, checks for errors and convert into an intermediate
       object file. Most errors happens in this step, so it is useful to compile a file
       after modifying it to check for errors. There are several ways to do it.
diff --git a/manuals/anjuta-manual/C/autotools-build-configure-dialog.page b/manuals/anjuta-manual/C/autotools-build-configure-dialog.page
index dc9fd95..b24c82e 100644
--- a/manuals/anjuta-manual/C/autotools-build-configure-dialog.page
+++ b/manuals/anjuta-manual/C/autotools-build-configure-dialog.page
@@ -48,7 +48,7 @@
     <item>
       <title><gui>Build Directory</gui></title>
       <p>
-        Select here the build directory, it can be the project directory
+        Select here the build directory. It can be the project directory
         or a subdirectory. This is particularly useful when switching between
         different configurations to avoid rebuilding the whole project.
       </p>
diff --git a/manuals/anjuta-manual/C/autotools-build-install.page b/manuals/anjuta-manual/C/autotools-build-install.page
index e0da55a..1fc8f32 100644
--- a/manuals/anjuta-manual/C/autotools-build-install.page
+++ b/manuals/anjuta-manual/C/autotools-build-install.page
@@ -33,7 +33,7 @@
       <p>
         From the <gui>main menu</gui>, select <guiseq><gui>Build</gui>
         <gui>Install</gui></guiseq> to install all files in the
-        same directory than the current edited file.
+        same directory as the current edited file.
       </p>
     </item>
   </steps>
diff --git a/manuals/anjuta-manual/C/autotools-build-preferences-dialog.page b/manuals/anjuta-manual/C/autotools-build-preferences-dialog.page
index 2a1ea51..5f8483d 100644
--- a/manuals/anjuta-manual/C/autotools-build-preferences-dialog.page
+++ b/manuals/anjuta-manual/C/autotools-build-preferences-dialog.page
@@ -26,7 +26,7 @@
     <item>
       <title><gui>Run several commands at a time</gui></title>
       <p><app>make</app> is able to run several compilations at the same time.
-      It decrease the build time when having a multi-core processor but could
+      It decreases build time when having a multi-core processor but could
       trigger some issues so this can be enabled or disabled with this check box.</p>
     </item>
     <item>
@@ -40,20 +40,20 @@
       <p>By default errors and warnings message are translated. It has two
       drawbacks though. In order to recognize errors and warnings the
       translation of <app>Anjuta</app> and the compiler should perfectly match.
-      Moreover, it is often more difficult to find help on internet when
+      Moreover, it is often more difficult to find help on the internet when
       searching translated messages as they are much less common. Unchecking
       this check box allows to disable translation.</p>
     </item>
     <item>
       <title><gui>Highlight build warnings and errors in editor</gui></title>
       <p>Errors and warnings during the build are displayed and highlighted in
-      the message window. By checking this option, they are higlighted in the
+      the message window. By checking this option, they are highlighted in the
       editor too.</p>
     </item>
     <item>
       <title><gui>Install as root</gui></title>
-      <p>Installing a program needs to copy files in system directory which are
-      often not writable by the user. If this check box is checked, you can choose
+      <p>Installing a program needs to copy files into system directories which are
+      often not writable by users. If this check box is checked, you can choose
       to use <cmd>sudo</cmd> or <cmd>su</cmd> before installing the files
       to acquire enough right to do it.</p>
     </item>
diff --git a/manuals/anjuta-manual/C/run-parameters-dialog.page b/manuals/anjuta-manual/C/run-parameters-dialog.page
index d7bff75..2fc8c10 100644
--- a/manuals/anjuta-manual/C/run-parameters-dialog.page
+++ b/manuals/anjuta-manual/C/run-parameters-dialog.page
@@ -44,8 +44,8 @@
     <item>
       <title><gui>Environment Variables</gui></title>
       <p>You can click on the drop-down section, to display all environment
-      variables those will be accessible by your program. By default, it
-      includes all the current environment variables, they are display in light
+      variables that will be accessible by your program. By default, it
+      includes all the current environment variables, they are displayed in light
       gray.</p>
       <p>You can click on the <gui>New</gui> button to add a new
       environment variable.</p>
@@ -53,7 +53,7 @@
       of the selected environment variable.</p>
       <p>You can click on the <gui>Delete</gui> button to remove the
       selected environment variable.</p>
-      <p>When a variable has not the same value than in the current
+      <p>When a variable has not the same value as in the current
       environment, it is displayed in black.</p>
     </item>
     <item>