fix spelling

5 files changed, 6 insertions, 6 deletions

diff --git a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_build_set.htm b/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_build_set.htm
index e27664fd750..c63e2f4e923 100644
--- a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_build_set.htm
+++ b/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>
diff --git a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_paths.htm b/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_paths.htm
index 715a97dcc61..7e352acd51b 100644
--- a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_paths.htm
+++ b/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>
diff --git a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_platf.htm b/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_platf.htm
index f5996969db3..5670b058933 100644
--- a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_proj_platf.htm
+++ b/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.
diff --git a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_search.htm b/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_search.htm
index 752aecf0947..c379a37f950 100644
--- a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_search.htm
+++ b/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>
diff --git a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_set_src_fold.htm b/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_set_src_fold.htm
index 0e418fa2670..03b75308a15 100644
--- a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_set_src_fold.htm
+++ b/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