fix spelling

doc/org.eclipse.cdt.doc.user/concepts/cdt_c_outlineview.htm

@@ -15,7 +15,7 @@
 <p>The Outline view displays an outline of a structured C/C++ file that is currently 
 open in the editor area, by listing the structural elements. </p>
 
-<img src="../images/outlineView.png"  alt="Editor View highlighting corrisponding element in the Outline View"></li>
+<img src="../images/outlineView.png"  alt="Editor View highlighting corresponding element in the Outline View"></li>
 
 <p>The Outline view shows the following elements in the source file in the order 
 in which they occur:</p>

doc/org.eclipse.cdt.doc.user/concepts/cdt_c_search.htm

@@ -219,17 +219,17 @@ your last search.</p>
 <h2>Search Concepts</h2>
 
 <h3>Declarations</h3>
-<p>According to the ANSI C++ Spec, a declaration is a statement that “introduces a name into a translation unit or re-declares a name that has been previously introduced by a previous declaration.</p>
+<p>According to the ANSI C++ Spec, a declaration is a statement that "introduces a name into a translation unit or re-declares a name that has been previously introduced by a previous declaration".</p>
 <p>All C/C++ search elements can be searched for declarations.</p>
 
 <h3>Definitions</h3>
 <p>Most declarations are also definitions; in other words, they also define the entity for they declare the name for. However there are some elements that can have separate definitions from their declarations.</p>
 <p>For C/C++ search the following elements can be searched for definitions:
 <ul>
-	<li>Functions/Methods – the definition is where the code implementation resides</li>
+	<li>Functions/Methods - the definition is where the code implementation resides</li>
 	<li>Variable:
 		<ol>
-			<li>Extern – the definition is where the variable is initialized</li>
+			<li>Extern - the definition is where the variable is initialized</li>
 			<li>Non extern - the definition of a variable is where it is declared </li>
 		</ol></li>
 	<li>Field:
@@ -237,17 +237,17 @@ your last search.</p>
 			<li>Static fields - the definition of a static field is where it gets initialized</li>
 			<li>Non static fields - the definition corresponds to the fields declaration</li>
 		</ol></li>
-	<li>Namespace – the definition of a namespace is the same as its declaration</li>
+	<li>Namespace - the definition of a namespace is the same as its declaration</li>
 </ul></p>
 
 <h3>References</h3>
 <p>By selecting references, C/C++ search will return all of the places the selected element is used.</p>
 
 <h3>All Occurrences</h3>
-<p>Selecting ‘All Occurrences’ in the Limit To section will result in a search for declarations, definitions (if applicable) and references for whatever element or elements have been selected.</p>
+<p>Selecting 'All Occurrences' in the Limit To section will result in a search for declarations, definitions (if applicable) and references for whatever element or elements have been selected.</p>
 
 <h3>Any Element</h3>
-<p>Selecting ‘Any Element’ in the Search For section will result in a search for all of the listed elements plus macros and typedefs.</p>
+<p>Selecting 'Any Element' in the Search For section will result in a search for all of the listed elements plus macros and typedefs.</p>
 
 
 <p>For more information, see:<ul>

doc/org.eclipse.cdt.doc.user/reference/cdt_u_m_edit.htm

@@ -99,7 +99,7 @@
  <tr align="left" valign="top">
  	<td><strong>Add Task...</strong></td>
  	<td>Add a user defined task to the current text selection or selected element.</td>
- 	<td> Alt+<strong></strong>Enter</td>
+ 	<td> Alt+Enter</td>
  </tr>
  
 <tr align="left" valign="top">

doc/org.eclipse.cdt.doc.user/reference/cdt_u_project_explorer_view.htm

@@ -70,7 +70,7 @@
 									<dl>
 										<p><dt>Top Level Elements</dt>
 											<dd>Choose whether to show working sets or projects as top level elements. 
-											Chosing working sets allows easy grouping of projects in large workspaces.</dd><p></p>
+											Choosing working sets allows easy grouping of projects in large workspaces.</dd><p></p>
 										<p><dt>Select Working Set</dt>
 											<dd>Opens the <strong>Select Working Set</strong> dialog to allow selecting a working set for the view.</dd><p></p>
 										<p><dt>Deselect Working Set</dt>
@@ -81,7 +81,7 @@
 											<dd>Choose to display packages in flat or hierarchical form.</dd><p></p>
 										<p><dt>Customize View</dt>
 											<dd>This command allows customization of view filters and content modules. 
-											The previous will allow you to supress the display of certain types of files 
+											The previous will allow you to suppress the display of certain types of files 
 											while the later will allow entirely new types of content to be shown in the view.<dd><p></p>
 										<p><dt>Link Editor</dt>
 											<dd>See the toolbar item description above.</dd><p></p>

doc/org.eclipse.cdt.doc.user/reference/cdt_u_prop_build.htm

@@ -38,7 +38,7 @@ and, moreover, change the visibility of other property pages.
 		</tr>
 		<tr>
 			<td><strong>Builder type</strong></td>
-			<td>Specifies the type of builder to use: <strong>Internal builder</strong> (builds C/C++ programs using a compiler that implements the C/C++ Language Specificationt) and <strong>External builder</strong> (external tools let you configure and run programs and Ant buildfiles using the Workbench, which can saved and run at a later time to perform a build).</td>
+			<td>Specifies the type of builder to use: <strong>Internal builder</strong> (builds C/C++ programs using a compiler that implements the C/C++ Language Specification) and <strong>External builder</strong> (external tools let you configure and run programs and Ant buildfiles using the Workbench, which can saved and run at a later time to perform a build).</td>
 		</tr>
 		<tr>
 			<td><strong>Use default build command</strong></td>

doc/org.eclipse.cdt.doc.user/reference/cdt_u_prop_general_pns_lib.htm

@@ -35,7 +35,7 @@ alt="C/C++ Project Properties, Paths and Symbols, Libraries">
         <dd>Check to display system (built-in) libraries.</dd>
   <dt><br>Available for :</dt>
   <dd>CDT projects, folders and files. 
-  Note that current toolchain may not support this featrure.</dd>
+  Note that current toolchain may not support this feature.</dd>
 </dl></p>
 
 <p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21"><br>

doc/org.eclipse.cdt.doc.user/reference/cdt_u_prop_general_pns_libpath.htm

@@ -35,7 +35,7 @@ alt="C/C++ Project Properties, Paths and Symbols, Library paths">
         <dd>Check to display system (built-in) library paths.</dd>
   <dt><br>Available for :</dt>
   <dd>CDT projects, folders and files. 
-  Note that current toolchain may not support this featrure.</dd>
+  Note that current toolchain may not support this feature.</dd>
 </dl></p>
 
 <p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21"><br>

doc/org.eclipse.cdt.doc.user/reference/cdt_u_prop_general_pns_ref.htm

@@ -12,7 +12,7 @@
 Project references are a powerful way of expressing dependencies between
 Build configurations in different projects. Specifically they perform 2 roles:
 <ul>
-<li>Automatic propogation of <a href="cdt_u_prop_general_exp.htm"><em>Exported Settings</em></a> from one project
+<li>Automatic propagation of <a href="cdt_u_prop_general_exp.htm"><em>Exported Settings</em></a> from one project
 to another which depends on it</li>
 <li>Build, if necessary, referenced projects before dependent project</li>
 </ul> 

doc/org.eclipse.cdt.doc.user/reference/cdt_u_view_executables.htm

@@ -36,7 +36,7 @@
      <td><strong>Executable Name </strong></td>
      <td><p>Displays a list of  executables in the workspace as well as other files added by the user. Select an executable to update the Source File Name pane with related files. The executable information shown  can include: </p>
        <ul>
-         <li><strong>Executable Name</strong> - (default) Name of the exectable file.</li>
+         <li><strong>Executable Name</strong> - (default) Name of the executable file.</li>
          <li><strong>Executable Project</strong> - (default) The project  associated with the executable.</li>
          <li><strong>Executable Location</strong> - (default) The current location of the executable.</li>
          <li><strong>Executable Size</strong> - The executable size shown in bytes.</li>

doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_build_set.htm

@@ -16,7 +16,7 @@
   <li>Configure how the CDT handles make errors.</li>
   <li>Change parallel build settings.</li> 
   <li>Map the target passed to make when you select build or rebuild.</li>
-  <li>Redefine duild directory (for custom makefile only)</li>
+  <li>Redefine build directory (for custom makefile only)</li>
 </ul>
 
 <p>To define build settings:<br>

doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_paths.htm

@@ -17,7 +17,7 @@ function newWin(url) {
 preprocessor symbols for the parser. This lets the parser understand the contents of the C/C++ source code so that you can more effectively use the search and code completion features. </p>
 
 <p>If Autodiscovery is enabled, after a build finishes, any
-discovered paths and symbols will be displayed in the <strong>Discoverd Paths</strong>
+discovered paths and symbols will be displayed in the <strong>Discovered Paths</strong>
 section. You can also define the properties on a per project basis in
 the C/C++ Projects or Navigator views.</p>
 <p>To add include paths and symbols:</p>

doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_platf.htm

@@ -31,7 +31,7 @@ While creating CDT project project, you need to select its type.
 </ul>
 
 <p>
-  By default, this dialog dispays only the project types
+  By default, this dialog displays only the project types
   that are buildable on the system on which Eclipse is running.  
   You can view all installed project types by unchecking the 
   <strong>Show Project Types and toolchains only if they are supported on the platform</strong> box.

doc/org.eclipse.cdt.doc.user/tasks/cdt_t_search.htm

@@ -44,11 +44,11 @@ The info required to do a search is:
 	</tr>
 	<tr>
 		<td valign="top"><strong>Search For </strong></td>
-		<td valign="top">this is the element type that you wish to search for. You can also select to search on ‘Any Element’ which will perform the search on a combination of all elements</td>
+		<td valign="top">this is the element type that you wish to search for. You can also select to search on 'Any Element' which will perform the search on a combination of all elements</td>
 	</tr>
 	<tr>
 		<td valign="top"><strong>Limit To</strong></td>
-		<td valign="top">this allows you to limit your search to declarations, definitions or references. You can also select ‘All Occurrences’ which will search for declarations, definitions and references that match the element</td>
+		<td valign="top">this allows you to limit your search to declarations, definitions or references. You can also select 'All Occurrences' which will search for declarations, definitions and references that match the element</td>
 	</tr>
 	<tr>
 		<td valign="top"><strong>Scope</strong></td>

doc/org.eclipse.cdt.doc.user/tasks/cdt_t_set_src_fold.htm

@@ -11,7 +11,7 @@
 <p><em>Note that source folders can only be currently used with Standard
 Make projects. Managed Make projects treat the entire project as a
 source folder.</em></p>
-<p>Source folders are a way to cut down on a project’s indexing scope.
+<p>Source folders are a way to cut down on a project's indexing scope.
 You can mark the folders that are part of your day to day work or part
 of a subsystem that you work on. All files inside source folders will
 be indexed and are, thus, searchable. Note that any files pulled in by