From 91854c523bdbc72a5ee858d5d87d3a36f4bdb245 Mon Sep 17 00:00:00 2001
From: Matthias Becker <ma.becker@sap.com>
Date: Fri, 4 Oct 2024 15:18:33 +0200
Subject: [PATCH] Write HTML-Headers in Title Case in platform.doc.isv (II)

---
 .../org.eclipse.platform.doc.isv/guide/ua.htm  |  4 ++--
 .../guide/ua_cheatsheet.htm                    |  6 +++---
 .../guide/ua_cheatsheet_composite.htm          | 10 +++++-----
 .../guide/ua_cheatsheet_composite_content.htm  |  2 +-
 .../guide/ua_cheatsheet_guidelines.htm         | 17 +++++++----------
 .../guide/ua_cheatsheet_simple.htm             | 18 ++++++++----------
 .../guide/ua_dynamic.htm                       |  6 +++---
 .../guide/ua_dynamic_extensions.htm            | 16 ++++------------
 .../guide/ua_dynamic_filters.htm               | 10 +++++-----
 .../guide/ua_dynamic_includes.htm              |  2 +-
 .../guide/ua_help_abstract_scope.htm           |  2 +-
 .../guide/ua_help_content.htm                  |  2 +-
 .../guide/ua_help_content_active.htm           |  2 +-
 .../guide/ua_help_content_active_action.htm    |  2 +-
 .../guide/ua_help_content_active_debug.htm     | 10 +++++-----
 .../guide/ua_help_content_active_invoke.htm    |  2 +-
 .../guide/ua_help_content_command.htm          |  2 +-
 .../ua_help_content_command_authoring.htm      |  2 +-
 .../guide/ua_help_content_criteria.htm         | 12 ++++++------
 .../guide/ua_help_content_files.htm            |  6 +++---
 .../guide/ua_help_content_manifest.htm         |  2 +-
 .../guide/ua_help_content_nested.htm           |  6 +++---
 .../guide/ua_help_content_toc.htm              |  2 +-
 .../guide/ua_help_content_xhtml.htm            |  2 +-
 .../guide/ua_help_context.htm                  |  2 +-
 .../guide/ua_help_context_dynamic.htm          |  2 +-
 .../guide/ua_help_context_id.htm               |  2 +-
 .../guide/ua_help_context_xml.htm              |  8 ++++----
 .../guide/ua_help_infocenter_preferences.htm   |  8 ++++----
 .../guide/ua_help_search.htm                   |  2 +-
 .../guide/ua_help_search_types.htm             |  2 +-
 .../guide/ua_help_setup.htm                    |  6 +++---
 .../guide/ua_help_setup_about.htm              |  2 +-
 .../guide/ua_help_setup_infocenter.htm         | 10 +++++-----
 .../guide/ua_help_setup_nav.htm                |  2 +-
 .../guide/ua_help_setup_preferences.htm        | 10 +++++-----
 .../guide/ua_help_setup_preindex.htm           |  8 ++++----
 .../guide/ua_help_setup_rcp.htm                |  2 +-
 .../guide/ua_help_setup_standalone.htm         |  8 ++++----
 .../guide/ua_help_war.htm                      |  4 ++--
 .../guide/ua_intro_cust_static.htm             |  2 +-
 .../guide/ua_intro_define_content.htm          |  2 +-
 .../guide/ua_intro_defining.htm                |  2 +-
 .../guide/ua_intro_defining_config.htm         |  2 +-
 .../guide/ua_intro_ext_custom_url.htm          |  2 +-
 .../guide/ua_intro_ext_standbypart.htm         |  2 +-
 .../guide/ua_intro_ext_theme.htm               |  4 ++--
 .../guide/ua_intro_extending.htm               |  2 +-
 .../guide/ua_intro_extending_content.htm       |  2 +-
 .../guide/ua_intro_hello_world.htm             |  2 +-
 .../guide/ua_intro_minimal.htm                 |  8 ++++----
 .../guide/ua_intro_universal.htm               |  6 +++---
 .../guide/ua_intro_universal_contributing.htm  |  2 +-
 .../guide/ua_intro_universal_defaults.htm      |  2 +-
 .../guide/ua_intro_universal_extending.htm     |  4 ++--
 .../guide/ua_intro_universal_links.htm         |  2 +-
 .../guide/ua_intro_universal_preference.htm    |  2 +-
 .../guide/ua_intro_xhtml.htm                   |  2 +-
 .../guide/ua_statushandling.htm                |  2 +-
 .../guide/ua_statushandling_defining.htm       |  2 +-
 .../guide/ua_statushandling_sample.htm         |  2 +-
 .../guide/workbench.htm                        |  2 +-
 .../guide/workbench_advext_activities.htm      | 16 ++++++++--------
 .../guide/workbench_advext_contexts.htm        |  6 +++---
 .../guide/workbench_cmd_bindings.htm           |  2 +-
 .../guide/workbench_cmd_commands.htm           |  2 +-
 .../guide/workbench_cmd_handlers.htm           |  8 ++++----
 .../guide/workbench_cmd_menus.htm              |  8 ++++----
 .../guide/workbench_jobs.htm                   |  8 ++++----
 .../guide/workbench_perspectives.htm           | 13 +++++--------
 .../guide/workbench_resources.htm              |  2 +-
 .../guide/workbench_scalability.htm            |  2 +-
 .../guide/workbench_statushandling.htm         | 14 +++++++-------
 .../workbench_statushandling_defining.htm      |  4 ++--
 .../guide/wrkAdv_accessibility.htm             |  8 ++++----
 .../guide/wrkAdv_commands_handlers.htm         |  2 +-
 .../guide/wrkAdv_efs_resources.htm             |  2 +-
 .../guide/wrkAdv_encoding.htm                  |  2 +-
 .../guide/wrkAdv_keyBindings.htm               |  2 +-
 .../guide/wrkAdv_keyBindings_accelConfig.htm   |  4 ++--
 .../guide/wrkAdv_keyBindings_accelSet.htm      |  2 +-
 .../guide/wrkAdv_keyBindings_actionDef.htm     |  2 +-
 .../guide/wrkAdv_keyBindings_contexts.htm      |  2 +-
 .../guide/wrkAdv_marker_support.htm            |  2 +-
 .../guide/wrkAdv_markerhelp.htm                |  2 +-
 .../guide/wrkAdv_markerresolution.htm          |  2 +-
 .../guide/wrkAdv_markers.htm                   |  2 +-
 .../guide/wrkAdv_singleclick.htm               |  8 ++++----
 .../guide/wrkAdv_undo.htm                      | 14 +++++++-------
 .../guide/wrkAdv_workingsets.htm               |  4 ++--
 90 files changed, 205 insertions(+), 221 deletions(-)

diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua.htm
index 5890646f388..efd7bf825ea 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua.htm
@@ -10,9 +10,9 @@
 </head>
 <body>
 
-<h1>User assistance support</h1>
+<h1>User Assistance Support</h1>
 
-<h3>What is user assistance?</h3>
+<h3>What Is User Assistance?</h3>
 
 <p>
 User assistance is a set of components that together introduce the user
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm
index 6f988399132..461acea246f 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm
@@ -10,9 +10,9 @@
 </head>
 <body>
 
-<h2>Cheat sheets</h2>
+<h2>Cheat Sheets</h2>
 
-<h3><b>Guiding the user through tasks</b></h3>
+<h3><b>guiding the User Through Tasks</b></h3>
 
 <p>
 Even when the platform UI filters out unneeded functionality, there is still a steep learning
@@ -30,7 +30,7 @@ <h3><b>Guiding the user through tasks</b></h3>
 Each task is represented by a simple cheat sheet. </li>
 </ul>
 
-<h3>Related links</h3>
+<h3>Related Links</h3>
 <p>
 <a href="../../org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm">Working with cheat sheets</a><br>
 <a href="../../org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm">Working with composite cheat sheets</a><br>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm
index d8e0ddfde64..617e98eba35 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm
@@ -23,7 +23,7 @@
   </head>
   <body>
     <h2>
-      Composite cheat sheets
+      Composite Cheat Sheets
     </h2>
     <p>
       <a href=
@@ -36,7 +36,7 @@ <h2>
       org.eclipse.ui.cheatsheets.cheatSheetContent</a></b> extension point.
     </p>
     <h3>
-      Content file format
+      Content File Format
     </h3>
     <p>
       The composite cheat sheet content itself is defined in a separate file
@@ -77,7 +77,7 @@ <h3>
     </p>
 
     <h3>
-      Cheat sheet task parameters
+      Cheat Sheet Task Parameters
     </h3>
     <p>
       If a task has kind = "cheatsheet" a cheat sheet will be opened when that
@@ -130,7 +130,7 @@ <h3>
       </tr>
     </table>
     <h3>
-      Example of a composite cheat sheet
+      Example of a Composite Cheat Sheet
     </h3>
 
     <p>
@@ -217,7 +217,7 @@ <h3>
     </p>
 
     <h3>
-      Related links
+      Related Links
     </h3>
     <p>
       <a href=
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm
index 79d9be1faf5..93851c96d15 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm
@@ -11,7 +11,7 @@
 </head>
 <body>
 
-<h3>Composite cheat sheet content file XML format</h3>
+<h3>Composite Cheat Sheet Content File XML Format</h3>
 
 <h6 class="CaptionFigColumn">Identifier: </h6>org.eclipse.ui.cheatsheets.composite_schema
 <h6 class="CaptionFigColumn">Since: </h6>3.2
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_guidelines.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_guidelines.htm
index 2763f754d3e..68d9177a429 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_guidelines.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_guidelines.htm
@@ -10,15 +10,14 @@
 </head>
 <body>
 
-<h2>Cheat sheet authoring guidelines</h2>
+<h2>Cheat Sheet Authoring Guidelines</h2>
 
 <p>
 Cheat sheets and composite cheat sheets enable a user to achieve a goal by 
 completing a sequence of steps. These guidelines discuss when to use cheat 
 sheets and how to best write a cheat sheet. </p>
 
-<h3>
-When to create cheat sheets</h3>
+<h3>When to Create Cheat Sheets</h3>
 
 <p>
 Cheat sheets are well suited to tasks which consist of&nbsp; steps which lead 
@@ -29,8 +28,7 @@ <h3>
 usually contain up to 10 steps and can be completed in a half an hour or less. 
 For larger tasks consider using a composite cheat sheet. </p>
 
-<h3>
-When to create composite cheat sheets</h3>
+<h3>When to Create Composite Cheat Sheets</h3>
 
 <p>
 Composite cheat sheets are used to for 
@@ -38,15 +36,14 @@ <h3>
 cheat sheet or which has multiple goals. A composite cheat sheet can be used to 
 describe a sequence of tasks each of which builds on its predecessor. </p>
 
-<h3>
-When not to use cheat sheets</h3>
+<h3>When Not to Use Cheat Sheets</h3>
 
 <p>
 Cheat sheets work best when problem can be solved by a sequence of simple steps. Cheat sheets are not a substitute for the help system which allows for 
 creation of HTML pages with rich graphics and random access of information using 
 search and hyperlinks. Cheat sheets are not intended for tasks which require a 
 large amount of text to be input by the user. </p>
-<h3>Guidelines for creating a cheat sheet</h3>
+<h3>Guidelines for Creating a Cheat Sheet</h3>
 <ul>
   <li>Choose a short and meaningful title.</li>
   <li>Utilize links to the help system in cheat sheet tasks whenever possible to 
@@ -83,7 +80,7 @@ <h3>Guidelines for creating a cheat sheet</h3>
   <li>Test cheat sheets with the error log view open so you can see if any 
   warnings are written to the log.</li>
 </ul>
-<h3>Guidelines for creating a composite cheat sheet</h3>
+<h3>Guidelines for Creating a Composite Cheat Sheet</h3>
 <ul>
   <li>A composite cheat sheet should contain tasks that are related by a common 
   theme.</li>
@@ -101,7 +98,7 @@ <h3>Guidelines for creating a composite cheat sheet</h3>
   which tasks can be started.</li>
 </ul>
 
-<h3>Related links</h3>
+<h3>Related Links</h3>
 <p>
 <a href="../../org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm">Working with cheat sheets</a><br>
 <a href="../../org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm">Working with composite cheat sheets</a><br>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm
index ffc402dbb01..6714e0db82f 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Simple cheat sheets</h2>
+<h2>Simple Cheat Sheets</h2>
 
 <P >
 Cheat sheets guide the user through a series of complex tasks to achieve
@@ -29,7 +29,7 @@ <h2>Simple cheat sheets</h2>
 translated into other languages.
 </P>
 <h4>
-Contributing a cheat sheet</h4>
+Contributing a Cheat Sheet</h4>
 <p>Contributing a cheat sheet is pretty straightforward.  Let's look at a cheat sheet contributed by the
 JDT for building a simple Java application.
 </p>
@@ -54,7 +54,7 @@ <h4>
 appear in the <b>Other</b> category.
 <p align="center">
 <img border="0" src="images/cheatsheets.png" alt="Cheat sheet dialog"></p>
-<h4>Cheat sheet items</h4>
+<h4>Cheat Sheet Items</h4>
 <p>
 The real work for cheat sheets is done in the content file.  The content file is an XML file whose name and location
 are specified in the <b>contentFile</b> attribute.  The path for the file is relative to the plug-in's directory.  (Note
@@ -144,7 +144,7 @@ <h4>Subitems</h4>
 be visited in any particular order.  Subitems may also define actions that automatically perform the subtask for
 the user.  Subitem actions are described in the same way as item actions. 
 </p>
-<h4>Conditional expressions and cheat sheet variables</h4>
+<h4>Conditional Expressions and Cheat Sheet Variables</h4>
 <p>
 Conditional expressions can be used to define cheat sheet elements whose content or behavior depends upon a
 particular condition being true.  Conditions are described in the <b>condition</b> element of a subitem
@@ -184,7 +184,7 @@ <h4>Conditional expressions and cheat sheet variables</h4>
 </pre>
 The action to be performed is chosen based on the value of the <tt>v1</tt> variable.  If the variable
 value is neither <tt>a</tt> or <tt>b</tt>, it is considered an error.
-<h4>Repeated subitems</h4>
+<h4>Repeated Subitems</h4>
 <p>Repeated subitems describe a subitem that can can expand into 0, 1, or more similar substeps.  The
 substeps are individualized using the special variable <tt>${this}</tt>.  This variable will be replaced by
 the values specified in the <b>values</b> attribute.  The values attribute is a string of values that are separated
@@ -202,8 +202,7 @@ <h4>Repeated subitems</h4>
 action paramater value.  It can also be accessed from the 
 <a href="../reference/api/org/eclipse/ui/cheatsheets/ICheatSheetManager.html"><b>ICheatSheetManager</b></a>
 while the action is executing.
-<h4>
-Cheat sheet listeners</h4>
+<h4>Cheat Sheet Listeners</h4>
 <p>
 In some cases, you may want to change other parts of your UI if a cheat sheet is active.
 For example, you may have an editor that shows special annotations if a cheat sheet is guiding the
@@ -215,8 +214,7 @@ <h4>
 <a href="../reference/api/org/eclipse/ui/cheatsheets/ICheatSheetEvent.html"><b>ICheatSheetEvent</b></a> when there
 is a change in the cheat sheet's life cycle, such as when it opens, closes, or completes.  
 </p>
-<h4>
-Contributing attributes to an existing cheat sheet</h4>
+<h4>Contributing Attributes to an Existing Cheat Sheet</h4>
 <p>
 The <b><a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetItemExtension.html">org.eclipse.ui.cheatsheets.cheatSheetItemExtension</a></b>
 extension can be used to contribute arbitrary attributes to a pre-existing cheat sheet.  
@@ -228,7 +226,7 @@ <h4>
 See the extension point documentation for more detail.
 </p>
 
-<h4>Related links</h4>
+<h4>Related Links</h4>
 <p>
 <a href="../../org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm">Working with cheat sheets</a><br>
 <a href="ua_cheatsheet_composite.htm">Creating composite cheat sheets</a><br>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm
index 5c1c1a416a0..d18239f187b 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm
@@ -16,9 +16,9 @@
 </head>
 <body>
 
-<h2>Dynamic content</h2>
+<h2>Dynamic Content</h2>
 
-<h3>What is dynamic content?</h3>
+<h3>What Is Dynamic Content?</h3>
 
 <p>
 Several user assistance components allow you to provide dynamic content. This
@@ -98,7 +98,7 @@ <h3>XML Annotations</h3>
 </pre>
 <hr>
 
-<h3>Content producers</h3>
+<h3>Content Producers</h3>
 
 <p>
 A content producer is a mechanism for plugging-in Java code to produce the document
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_extensions.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_extensions.htm
index 483f33624a7..4b5b642a715 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_extensions.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_extensions.htm
@@ -22,18 +22,14 @@
     </style>
   </head>
   <body>
-    <h2>
-      Content extensions
-    </h2>
+    <h2>Content Extensions</h2>
     <p>
       A content extension is either a contribution of content into a known
       anchor (similar to an extension into an extension point), or the
       replacement of an existing element in a document.
     </p>
 
-    <h3>
-      Contributing into anchors
-    </h3>
+    <h3>Contributing Into Anchors</h3>
     <p>
       Anchor elements (e.g. <code>&lt;anchor id="my_anchor"/&gt;</code>) can be
       specified in any user assistance XML document, and represent places at
@@ -108,9 +104,7 @@ <h3>
       it was explicitly added into the original document.
     </p>
 
-    <h3>
-      Replacing content
-    </h3>
+    <h3>Replacing Content</h3>
     <p>
       Any XML element in a user assistance document that has an <code>id</code>
       attribute that is unique to that document can be replaced with any other
@@ -151,9 +145,7 @@ <h3>
       <code>org.eclipse.ui.intro.configExtension</code></a> extension point)
     </p>
 
-    <h3>
-      Path format
-    </h3>
+    <h3>Path Format</h3>
     <p>
       The format of the <code>path</code> attribute is
       <code>/pluginId/path/file.xml#elementId</code>, except welcome where it
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm
index 4e8b194cec7..0f1d6e27de3 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm
@@ -37,7 +37,7 @@ <h2>Filters</h2>
 core expressions</a>, which is the same syntax used to filter menu contributions, etc from the UI.
 </p>
 
-<h3>System tests</h3>
+<h3>System Tests</h3>
 
 <p>
 Expressions check criteria by performing tests. One type of test is a system test, which tests
@@ -128,7 +128,7 @@ <h3>System tests</h3>
 expressions syntax</a> specification for more details.</em>
 </p>
 
-<h3>Property tests</h3>
+<h3>Property Tests</h3>
 
 <p>
 In addition to system tests, you can test any property of an available object as long as
@@ -277,7 +277,7 @@ <h3>Property tests</h3>
 expressions syntax</a> specification for more details on how to write expressions.</em>
 </p>
 
-<h3>Defining your own test</h3>
+<h3>Defining Your Own Test</h3>
 
 The core expressions framework allows you define your own test that can test
 on any arbitrary property of any object that is accessible through the variables defined for
@@ -308,7 +308,7 @@ <h3>
       &lt;/enablement&gt;
     &lt;/topic&gt;</pre>
 
-<h3>Filter attributes/elements <span class="warning">(deprecated)</span></h3>
+<h3>Filter Attributes/Elements <span class="warning">(deprecated)</span></h3>
 
 <p>
 Prior to the 3.3, filters were specified using <code>filter</code> attributes or elements.
@@ -502,7 +502,7 @@ <h3>Information Center</h3>
 see <a href="ua_help_setup_preferences.htm">help system customization</a>. 
 </p>
 
-<h3>Where can I use filters?</h3>
+<h3>Where Can I Use Filters?</h3>
 
 <p>
 Filtering can be used in any XML-based user assistance document, such as help XHTML topics,
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm
index 90af295808f..1682b3dca7e 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm
@@ -67,7 +67,7 @@ <h2>
     </p>
 
     <h3>
-      Where can I use includes?
+      Where Can I Use Includes?
     </h3>
     <p>
       See below for a list of the document types in which includes can be used.
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_abstract_scope.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_abstract_scope.htm
index cdac5ee4f82..024bdc80ec9 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_abstract_scope.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_abstract_scope.htm
@@ -18,7 +18,7 @@
   </head>
   <body>
     <h2>
-      Using AbstractHelpScope to filter an information center
+      Using AbstractHelpScope to Filter an Information Center
     </h2>
     <p>
       An information center can be used to serve information for more than one
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm
index 5a7f7134e97..07e5b7436d6 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Help content</h2>
+<h2>Help Content</h2>
 
 <p><b>Building a help plug-in</b></p>
 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm
index 0fafd1bf58d..99f6ac83bdd 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Active help</h2>
+<h2>Active Help</h2>
 
 <p>Active help is the ability to invoke Eclipse code from on-line
 documentation.&nbsp;It is implemented by including some JavaScript in your
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm
index 9c711e3cdbb..cd02f8c9cf3 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h3>Writing the help action</h3>
+<h3>Writing the Help Action</h3>
 
 <p>The interface <a href="../reference/api/org/eclipse/help/ILiveHelpAction.html"><b>ILiveHelpAction</b></a>
 is used to build an active help action.</p>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm
index bd18f63b78d..53abc086c8d 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Tips for debugging active help</h2>
+<h2>Tips for Debugging Active Help</h2>
 
 
 <p>The code and markup that triggered our active help link looks pretty
@@ -18,7 +18,7 @@ <h2>Tips for debugging active help</h2>
 to work?</p>
 
 
-<h4>Test your action ahead of time</h4>
+<h4>Test Your Action Ahead of Time</h4>
 
 
 <p>If your action implementation is fairly involved, you should invoke the
@@ -26,7 +26,7 @@ <h4>Test your action ahead of time</h4>
 that the action is error-free before invoking it from the JavaScript.&nbsp; </p>
 
 
-<h4>Ensure the JavaScript is running</h4>
+<h4>Ensure the JavaScript Is Running</h4>
 
 
 <p>You can modify &quot;<b>liveHelp.js</b>&quot; (make a copy of this from the plugins/org.eclipse.help
@@ -47,7 +47,7 @@ <h4>Ensure the JavaScript is running</h4>
 then you have a problem in the HTML markup.</p>
 
 
-<h4>Debug the active help action</h4>
+<h4>Debug the Active Help Action</h4>
 
 
 <p>Once you know that the JavaScript is running, you can debug your action from
@@ -67,7 +67,7 @@ <h4>Debug the active help action</h4>
 the action as you would any other Java code.</p>
 
 
-<h4>Make sure your UI code is wrapped in Display.syncExec</h4>
+<h4>Make Sure Your UI Code Is Wrapped in Display.syncExec</h4>
 
 
 <p>A common runtime problem is improperly accessing UI code from the thread that
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm
index 3180f87d3e1..f13d362c472 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Invoking the action from HTML</h2>
+<h2>Invoking the Action From HTML</h2>
 
 <P>
 To include active help links in your documentation, you must first declare the
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm
index 0740fa292a8..86a64a91047 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Embedding commands in help</h2>
+<h2>Embedding Commands in Help</h2>
 
 <p>It is possible to create links to workbench commands in help content.  When
 the user clicks the link, the command will be executed.  This feature is similar
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm
index 8c253e879e9..8729de8f76d 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Authoring a command link</h2>
+<h2>Authoring a Command Link</h2>
 
 <P>
 To include command links in your documentation, you must first declare the
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_criteria.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_criteria.htm
index 33760e32b1d..33db60218f3 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_criteria.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_criteria.htm
@@ -9,20 +9,20 @@
 </head>
 <body>
 
-<h2>Adding criteria to help content</h2>
+<h2>Adding Criteria to Help Content</h2>
 
 <p>This page will explain how to activate criteria. To enable criteria you need define which criteria are associated 
 with each topic and also set preferences which tell the help system to show criteria. The association between criteria and topics can be
 either in a toc file or using a criteria provider class. </p>
 
-<h3>What are criteria?</h3>
+<h3>What Are Criteria?</h3>
 
 <p>Some topics of the plug-in might only be of interest to certain users, for example a topic may be specific to the linux platform.
 The document writer can define a criterion "platform" with values such as "linux", "windows" etc applied to different topics. The user can
 then filter the documentation to show only documents applicable to a specific platform.
 </p>
 
-<h3>How to define criteria in a table of contents file</h3>
+<h3>How to Define Criteria in a Table of Contents File</h3>
 
 <p>When defining a table of contents file criteria information can be appended according to these steps:</p>
 <ul>
@@ -53,7 +53,7 @@ <h3>How to define criteria in a table of contents file</h3>
 &lt;criteria name="Platform" value="AIX,Linux"/&gt;. The name attribute takes a single value.</li>
 </ul>
 
-<h3>How to define criteria using a criteria provider</h3>
+<h3>How to Define Criteria Using a Criteria Provider</h3>
 <p>As an alternative to defining criteria in a table of contents file the extension point
 <a href="../reference/extension-points/org_eclipse_help_criteriaProvider.html">org.eclipse.criteriaProvider</a>
 can be used to define a class which will associate criteria with topics.
@@ -62,7 +62,7 @@ <h3>How to define criteria using a criteria provider</h3>
 </p>
 
 
-<h3>Criteria localization</h3>
+<h3>Criteria Localization</h3>
 <p>The names and values of criteria can be localized.
 Follow these steps to add localization information for criteria:</p>
 <ul>
@@ -94,7 +94,7 @@ <h3>Criteria localization</h3>
 </li>
 
 </ul>
-<h3>How to set the preferences to enable criteria</h3>
+<h3>How to Set the Preferences to Enable Criteria</h3>
 <p>Define the necessary preferences in your plugin customization file.</p>
 <ul>
 <li>enableCriteria. This preference must be true to enable filtering by criteria.
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm
index 803412fa844..4242b890a5e 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Help server and file locations</h2>
+<h2>Help Server and File Locations</h2>
 
 <P >
 The platform utilizes its own documentation server to provide the actual web pages
@@ -69,7 +69,7 @@ <h2>Help server and file locations</h2>
 <pre >   &lt;topic label=&quot;Ref1&quot; href=&quot;http://www.example.com/myReference.html&quot;/&gt;</pre>
 
 
-<h4 >National language and translated documentation</h4>
+<h4 >National Language and Translated Documentation</h4>
 
 
 <p >The platform help system uses the same national language directory lookup
@@ -86,7 +86,7 @@ <h4 >National language and translated documentation</h4>
   resource, like images which differ between system, should be placed under ws
   or os directories for specific platform.</p>
   
-<h4 ><a name="help_plugin_files_xref">Cross plug-in referencing</a></h4>
+<h4 ><a name="help_plugin_files_xref">Cross Plug-in Referencing</a></h4>
 
 <P >The <b>href</b> argument can also refer to content from another
 plug-in.&nbsp; This is done by using a special cross plug-in referencing
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm
index b25b927df1c..b5db5c00e76 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Completing the plug-in manifest</h2>
+<h2>Completing the Plug-in Manifest</h2>
 
 <P >
 We started this example by creating our plug-in and document files. Next we created
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm
index 20347216bd6..0c2528014a8 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Building nested documentation structures</h2>
+<h2>Building Nested Documentation Structures</h2>
 
 <p>As plug-ins contribute functionality to the platform, it's common to add
 documentation that describes the new function.&nbsp; How can this documentation
@@ -19,7 +19,7 @@ <h2>Building nested documentation structures</h2>
 provides mechanisms for building documentation in both a top-down and bottom-up
 fashion.</p>
 
-<h4>Top-down nesting</h4>
+<h4>Top-down Nesting</h4>
 
 <p>Top-down nesting refers to the technique of defining a master table of
 contents which refers to all other included tocs.&nbsp; Top-down nesting is a
@@ -44,7 +44,7 @@ <h4>Top-down nesting</h4>
 individual tocs are free to evolve.&nbsp; They in turn might link to other sub-tocs.
 </p>
 
-<h4>Bottom-up composition</h4>
+<h4>Bottom-up Composition</h4>
 
 <p>Bottom-up composition is more flexible in that it lets new plug-ins decide
 where the documentation should exist in the toc structure.&nbsp; Bottom-up
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm
index 453e0e974a8..da3f938ddda 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Table of contents (toc) files</h2>
+<h2>Table of Contents (toc) Files</h2>
 
 <P >
 Now that we have our sample content files we can create a table of contents (<b>toc</b>)
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm
index 75c72b08d36..10710c2976d 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Contributing XHTML help documents</h2>
+<h2>Contributing XHTML Help Documents</h2>
 
 <p><b>Why use XHTML?</b></p>
 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm
index a50da1582ee..11fc37d2e8f 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Context-sensitive help</h2>
+<h2>Context-sensitive Help</h2>
 
 <p>A focused set of help topics that is related to the current context can be 
 shown to users on demand using <b>context-sensitive help</b>. This form of user 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm
index 0029e41a640..5d9bf85f701 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Dynamic context help</h2>
+<h2>Dynamic Context Help</h2>
 
 <p>
 In addition to statically associating widgets and context Ids, it is possible to 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm
index bde9fecd79a..87f27cb9f1a 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Declaring a context id</h2>
+<h2>Declaring a Context Id</h2>
 
 <p>
 The <b>setHelp</b> method in
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm
index 96ec442991d..db7eb64fd23 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Describing and packaging context-sensitive help content</h2>
+<h2>Describing and Packaging Context-sensitive Help Content</h2>
 
 <p>
 Context-sensitive help is described by associating the context id declared in
@@ -71,7 +71,7 @@ <h2>Describing and packaging context-sensitive help content</h2>
 name of the plug-in in which the org.eclipse.help.contexts extension is declared.</p>
 
 <h4>
-Context-sensitive help from multiple plug-ins</h4>
+Context-sensitive Help From Multiple Plug-ins</h4>
 
 
 <p>Another level of flexibility is the ability to contribute context-sensitive 
@@ -90,7 +90,7 @@ <h4>
 context (the UI plug-in) is shown first.&nbsp; Additional descriptions and links
 are appended in no guaranteed order.</p>
 
-<h4>Dynamic content</h4>
+<h4>Dynamic Content</h4>
 
 <p>
 Dynamic content is available for the context help in the form of
@@ -100,7 +100,7 @@ <h4>Dynamic content</h4>
 </p>
 
 <h4>
-Adding Context Help to your Java Code</h4>
+Adding Context Help to Your Java Code</h4>
 
 <p>
 See <a href="ua_help_context_id.htm">declaring a context Id</a> for more 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_infocenter_preferences.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_infocenter_preferences.htm
index d11c6a01061..10aaa10fb6e 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_infocenter_preferences.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_infocenter_preferences.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Information center customization</h2>
+<h2>Information Center Customization</h2>
 
 <p>All of the customizations which can apply to the Eclipse help system can also be applied to an Eclipse information center including
 product specific branding, style sheets, banner and ordering of books. The easiest way to do this is to 
@@ -23,7 +23,7 @@ <h2>Information center customization</h2>
 defines them.
 </p>
 
-<h3>Creating a product plug-in</h3>
+<h3>Creating a Product Plug-in</h3>
 <p>A product plugin can be created using the menu item File/New/Project and selecting Plug-in Project. 
 Uncheck the check box titled "Create Java Project", give the project a name, hit "next" and "finish" to 
 exit the wizard. In the extensions tab of the plug-in manifest editor add the extension 
@@ -48,7 +48,7 @@ <h3>Creating a product plug-in</h3>
 </pre>
 
 
-<h3>Installing the product plug-in</h3>
+<h3>Installing the Product Plug-in</h3>
 <p>
     Export the product plug-in as a deployable plug-in. Copy the jar file for the exported plug-in 
     to the "dropins" folder in the eclipse installation which will be used to start the information center.
@@ -56,7 +56,7 @@ <h3>Installing the product plug-in</h3>
     product plugin is called help.product and its product id is "custom" add the argument 
     "-product help.product.custom". Open the information center, the title will now show the customized product name.
 </p>
-<h3>Additional customization</h3>
+<h3>Additional Customization</h3>
 <p>
 Modify plugin_customization.ini in the product plugin to add more customizations, see <a href = "ua_help_setup_preferences.htm">
 Help system customization</a>, re-export and replace the plug-in in the dropins folder. To modify the banner
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm
index 484aac13925..6bbc1bba7db 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Help search</h2>
+<h2>Help Search</h2>
 
 <p>Since Eclipse 3.1, search in the workbench has been partitioned into two 
 major categories: development artifact search and information search. The former 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm
index 0c3c92fb51e..9e059e94557 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Plugging in search engines</h2>
+<h2>Plugging in Search Engines</h2>
 
 <p>
 The new federated information search in Help system uses the notion of <b>search 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup.htm
index be6ef6292de..aea9b3d5452 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup.htm
@@ -17,7 +17,7 @@ <h2>Configuration/setup</h2>
 the help system to work in different environments and products.
 </p>
 
-<h3>Help modes</h3>
+<h3>Help Modes</h3>
 
 <p>
 The help system can run in three modes: workbench (normal),
@@ -31,7 +31,7 @@ <h3>Help modes</h3>
 over the Web. Consult the links above for details.
 </p>
 
-<h3>Rich Client Platform (RCP) support</h3>
+<h3>Rich Client Platform (RCP) Support</h3>
 
 <p>
 The Help system is an <em>optional</em> Rich Client Platform (RCP) component. That
@@ -39,7 +39,7 @@ <h3>Rich Client Platform (RCP) support</h3>
 added</a> to it to provide help in your RCP application.
 </p>
 
-<h3>Product customization</h3>
+<h3>Product Customization</h3>
 
 <p>
 Help provides <a href="ua_help_setup_preferences.htm">preferences</a> that products
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_about.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_about.htm
index aac13018475..52614151c74 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_about.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_about.htm
@@ -8,7 +8,7 @@
 </head>
 <body>
 
-<h1>Using about.html to debug information centers</h1>
+<h1>Using about.html to Debug Information Centers</h1>
 
 <p>
 When developing an information center sometimes not all of the books show as expected or 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_infocenter.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_infocenter.htm
index 4875a234b91..1dad94e3f3f 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_infocenter.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_infocenter.htm
@@ -122,7 +122,7 @@ <h3>Installation/packaging</h3>
 	</li>
 </ol>
 
-<h3>How to start or stop information center from command line</h3>
+<h3>How to Start or Stop Information Center From Command Line</h3>
 
 <p>
 The <code>org.eclipse.help.standalone.Infocenter</code> class has a <code>
@@ -144,7 +144,7 @@ <h3>How to start or stop information center from command line</h3>
 
 <pre>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_[version].jar org.eclipse.help.standalone.Infocenter -command shutdown -eclipsehome d:\myApp\eclipse</pre>
 
-<h3>Using the information center</h3>
+<h3>Using the Information Center</h3>
 
 <p>
 Start the information center using the instructions above. Point a web browser to the
@@ -154,7 +154,7 @@ <h3>Using the information center</h3>
 <code>http://localhost:8081/help/index.jsp</code>.
 </p>
 
-<h3>How to start and stop an information center from Java</h3>
+<h3>How to Start and Stop an Information Center From Java</h3>
 
 <p>
 When including an information center as part of another application, it may be more
@@ -194,7 +194,7 @@ <h3>How to start and stop an information center from Java</h3>
 	</li>
 </ol>
 
-<h3>Making information center available on the web</h3>
+<h3>Making Information Center Available on the Web</h3>
 
 <p>
 Eclipse contains a complete information center and does not require any other server
@@ -228,7 +228,7 @@ <h3>Making information center available on the web</h3>
 to have browsers display documents using correct character set.
 </p>
 
-<h3>Running multiple instances of an information center</h3>
+<h3>Running Multiple Instances of an Information Center</h3>
 
 <p>
 Multiple instances of an information center can be run on a machine from one
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_nav.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_nav.htm
index f2e484d3f3e..b82f7393fe4 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_nav.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_nav.htm
@@ -6,7 +6,7 @@
 </head>
 <body>
 
-<h1>Generated navigation topics</h1>
+<h1>Generated Navigation Topics</h1>
 
 <p>
 If a topic in the table of contents does not specify an <code>href</code> attribute, or a toc
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preferences.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preferences.htm
index 6c1d4a4ef4f..d9f0cf3364c 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preferences.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preferences.htm
@@ -19,7 +19,7 @@
 </head>
 <body>
 
-<h2>Help system customization</h2>
+<h2>Help System Customization</h2>
 
 <p>The Eclipse help system can be configured and branded to suit your
 product by
@@ -31,7 +31,7 @@ <h2>Help system customization</h2>
 defines them.
 </p>
 
-<h3>org.eclipse.help plug-in:</h3>
+<h3>org.eclipse.help Plug-in:</h3>
 
 <table border="1">
   <tbody>
@@ -92,7 +92,7 @@ <h3>org.eclipse.help plug-in:</h3>
   </tbody>
 </table>
 
-<h3>org.eclipse.help.base plug-in:</h3>
+<h3>org.eclipse.help.base Plug-in:</h3>
 
 <table border="1">
   <tbody>
@@ -487,7 +487,7 @@ <h3>org.eclipse.help.base plug-in:</h3>
   </tbody>
 </table>
 
-<h3 class="deprecated">org.eclipse.help.appserver plug-in:</h3>
+<h3 class="deprecated">org.eclipse.help.appserver Plug-in:</h3>
 <span class="warning">Deprecated: This plug-in is no longer used by help. See table for alternative usage.</span>
 
 <table border="1">
@@ -521,7 +521,7 @@ <h3 class="deprecated">org.eclipse.help.appserver plug-in:</h3>
   </tbody>
 </table>
 
-<h3 class="deprecated">org.eclipse.tomcat plug-in:</h3>
+<h3 class="deprecated">org.eclipse.tomcat Plug-in:</h3>
 <span class="warning">Deprecated: This plug-in is no longer used by help. No alternative commands available.</span>
 
 <table border="1">
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preindex.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preindex.htm
index bb2e0f5f4fb..e9db2cf64ee 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preindex.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preindex.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Pre-indexing documentation</h2>
+<h2>Pre-indexing Documentation</h2>
 
 <p>When user searches help contents of a product, the search is performed
 within a documentation index. &nbsp;By default, this index &nbsp;is created
@@ -23,7 +23,7 @@ <h2>Pre-indexing documentation</h2>
 on
 the user machine and lets the user obtain first search results faster.</p>
 
-<h3>Building a documentation index for a plug-in.</h3>
+<h3>Building a Documentation Index for a Plug-in.</h3>
 
 <p>To build an index follow the steps:</p>
 <ul>
@@ -56,7 +56,7 @@ <h3>Building a documentation index for a plug-in.</h3>
 </li>
 </ul>
 
-<h3>Building an index for a product</h3>
+<h3>Building an Index for a Product</h3>
 
 <p>Per-product index is a one aggregate index of all documentation in the product.
   It should be used in scenarios in which the set of documentation plug-ins is
@@ -86,7 +86,7 @@ <h3>Building an index for a product</h3>
 when they run the product in the <b>en</b> locale.<br>
 </p>
 
-<h3>Packaging and Installation of the product's pre-built index</h3>
+<h3>Packaging and Installation of the Product's Pre-built Index</h3>
 
 Pre-built indices, the <b>doc_index.zip</b> files, need to be packaged as
 a plug-in. &nbsp; You can choose to use a plug-in associated with the primary
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_rcp.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_rcp.htm
index 2784d40720f..e706bc9e6d5 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_rcp.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_rcp.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Rich Client Platform (RCP) help</h2>
+<h2>Rich Client Platform (RCP) Help</h2>
 
 <p>
 The Help system is an <em>optional</em> Rich Client Platform (RCP) component. That
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_standalone.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_standalone.htm
index 659b8c4e11e..7edc0f42cff 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_standalone.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_standalone.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Standalone help</h2>
+<h2>Standalone Help</h2>
 
 <p>If you are creating an application that is not based on 
 the Eclipse framework, you can still use the Eclipse help system. Your 
@@ -65,7 +65,7 @@ <h3>Installation/packaging</h3>
   (which includes the help system). </li>
 </ol>
 
-<h3>How to call the help classes from Java</h3>
+<h3>How to Call the Help Classes From Java</h3>
 
 <ol>
   <li>Make sure <code>d:\myApp\eclipse\plugins\org.eclipse.help.base_[version].jar</code>
@@ -104,7 +104,7 @@ <h3>How to call the help classes from Java</h3>
 	<PRE><EM><SPAN style="font-style: normal">helpSystem.shutdown();</SPAN></EM> </PRE></LI>
 </ol>
 
-<h3>How to call the help from the command line</h3>
+<h3>How to Call the Help From the Command Line</h3>
 
 <p>
 The <code>org.eclipse.help.standalone.Help</code> class has a main method you can
@@ -122,7 +122,7 @@ <h3>How to call the help from the command line</h3>
 <P>The calls above to display help will cause help system to start, display help, and keep running to allow a user to continue browsing  help after the command is executed. To control the life cycle of the help system, use start and shutdown commands, in addition to the displayHelp command. For example, you may call</P>
 <PRE>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_[version].jar org.eclipse.help.standalone.Help -command start</PRE>
 
-<h3>[Optional] Installing a minimal stand-alone help system</h3>
+<h3>[Optional] Installing a Minimal Stand-alone Help System</h3>
 
 <p>
 The stand-alone help does not require the entire eclipse Platform package. It is 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_war.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_war.htm
index e827b073d82..64f0a024d77 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_war.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_war.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Deploying the information center as a Web Archive</h2>
+<h2>Deploying the Information Center as a Web Archive</h2>
 
 <p>
 Using Eclipse 3.4 or later it is possible to configure the help plugins to be deployed as a web archive (war file) which will act as a fully functioning information center. 
@@ -46,7 +46,7 @@ <h2>Deploying the information center as a Web Archive</h2>
 
 <h3>Troubleshooting</h3>
 
-<h4>HTTP 404 with Message "BridgeServlet: /help/"</h4>
+<h4>HTTP 404 With Message "BridgeServlet: /help/"</h4>
 
 <p>
 In the <tt>web.xml</tt> activate the init parameter <tt>enableFrameworkControls</tt>. This enables endpoints to control the embedded OSGi container. Call <a href="http://localhost:8080/help/sp_test">http://localhost:8080/help/sp_test</a>.
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm
index 064ae308364..38d98adce7f 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Displaying static HTML content in a CustomizableIntroPart</h2>
+<h2>Displaying Static HTML Content in a CustomizableIntroPart</h2>
 
 <p>Just like any intro part implementation, to use a CustomizableIntroPart you need to follow the basic steps to bind it to a product. However, there is an extra step needed to use this intro part and it is binding a "configuration" with it. Just like you bind an intro to a product, you must bind an <em>introConfig </em> to a customizableIntroPart. Here is a sample configuration: </p>
 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm
index 3aff58eda0b..0d606170153 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Defining intro content</h2>
+<h2>Defining Intro Content</h2>
 
 <p>
 Now we can look at the content itself.  Content is described in terms of pages.  All pages have an <b>id</b> attribute.
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm
index b91a6755b4b..f6e53e33ec4 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Defining an intro part</h2>
+<h2>Defining an Intro Part</h2>
 
 <p>
 The <a href="../reference/api/org/eclipse/ui/intro/IIntroPart.html"><b>IIntroPart</b></a> interface
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm
index 33d08334c63..ea7ed819a73 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Defining an intro config</h2>
+<h2>Defining an Intro Config</h2>
 
 <p>
 <b><a href="../reference/extension-points/org_eclipse_ui_intro_config.html">org.eclipse.ui.intro.config</a></b>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm
index 758cdf96db3..226b9ba1172 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Defining a custom IntroURL action</h2>
+<h2>Defining a Custom IntroURL Action</h2>
 
 <p>
 Using the <b><a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html">org.eclipse.ui.intro.configExtension</a></b>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm
index 340f8e12e67..431debe1043 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Contributing a standby content part</h2>
+<h2>Contributing a Standby Content Part</h2>
 
 <p>
 Plug-ins can also implement a part for displaying alternative content when the intro page is in standby mode.  For
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_theme.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_theme.htm
index 758bb3c331b..95189fc16d3 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_theme.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_theme.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Defining intro themes</h2>
+<h2>Defining Intro Themes</h2>
 
 <p>
 A theme defines the overall <em>appearance</em> of the intro. It is simply a way
@@ -75,7 +75,7 @@ <h3>Definition</h3>
 <code>org.eclipse.ui.intro/INTRO_THEME</code> in plugin_customization.ini. 
 </p>
 
-<h3>Enabling themes</h3>
+<h3>Enabling Themes</h3>
 
 <p>
 Theme support by itself does not make intro implementations theme-enabled.
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm
index b30b654a720..fdcdcd4ea8b 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Extending an intro config</h2>
+<h2>Extending an Intro Config</h2>
 
 <p>
 An intro configuration can be extended in several ways:
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm
index be31119b815..204da07a85f 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Extending the content of an intro config</h2>
+<h2>Extending the Content of an Intro Config</h2>
 
 <p>
 Plug-ins can contribute intro content to a page defined elsewhere.  However, the defining page must define an
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm
index 04381c20bf0..1d840984971 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Contributing a HelloWorld intro Part</h2>
+<h2>Contributing a HelloWorld Intro Part</h2>
 
 <p>
  We will now contribute a very basic intro part just to illustrate the steps needed to contribute a part implementation to the Workbench and get it to show up as the welcome page. To do this:</p>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_minimal.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_minimal.htm
index 44b708109d4..f062b3466a6 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_minimal.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_minimal.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Defining a minimal intro configuration</h2>
+<h2>Defining a Minimal Intro Configuration</h2>
 
 <p>
 The first stage in creating a new intro configuration is to add the necessary 
@@ -19,7 +19,7 @@ <h2>Defining a minimal intro configuration</h2>
 and have it show up in a product.</p>
 
 <h3>
-Create a plugin project and add extension points</h3>
+Create a Plugin Project and Add Extension Points</h3>
 
 <p>
 Create an new plugin project &quot;org.eclipse.intro.minimal&quot; which has a dependency 
@@ -53,7 +53,7 @@ <h3>
 &lt;/plugin&gt;</pre>
 
 <h3>
-Create the intro config file</h3>
+Create the Intro Config File</h3>
 
 <p>
 Create a file introcontent.xml in the plugin project org.eclipse.intro.minimal 
@@ -78,7 +78,7 @@ <h3>
         &lt;text&gt;This page under construction&lt;/text&gt;
     &lt;/page&gt;   
 &lt;/introContent&gt;</pre>
-<h3>Define a product binding</h3>
+<h3>Define a Product Binding</h3>
 <p>In this step we need to determine the product which is being used and create 
 an intro product binding and modify its plugin.xml file. If you are using the 
 Eclipse SDK this will be in the plugin project org.eclipse.sdk&nbsp; which can 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal.htm
index 4ef06225c50..f6ebd0fdb9e 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal.htm
@@ -10,9 +10,9 @@
 </head>
 <body>
 
-<h2>Universal intro</h2>
+<h2>Universal Intro</h2>
 
-<h3>What is the universal intro?</h3>
+<h3>What Is the Universal Intro?</h3>
 
 <p>
 The universal intro is complete, ready out-of-the-box implementation of intro with a
@@ -74,7 +74,7 @@ <h3>Motivation</h3>
   </li>
 </ul>
 
-<h3>Enter universal intro</h3>
+<h3>Enter Universal Intro</h3>
 
 <p>
 The universal intro is based on experience with intro implementations and the
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_contributing.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_contributing.htm
index 0fc7326bddc..442e415a161 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_contributing.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_contributing.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Contributing to universal intro</h2>
+<h2>Contributing to Universal Intro</h2>
 
 <p>
 In order to hook into to the universal intro, developers should have a 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_defaults.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_defaults.htm
index 7885149ce09..36161b10139 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_defaults.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_defaults.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Configuring product defaults</h2>
+<h2>Configuring Product Defaults</h2>
 
 <p>
 In addition to providing intro customization to the end users for the first 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_extending.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_extending.htm
index e76fc7043a0..2d426d20199 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_extending.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_extending.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Extending the universal intro</h2>
+<h2>Extending the Universal Intro</h2>
 
 <p>
 When launching the universal Welcome configured as shown above, you will notice 
@@ -123,7 +123,7 @@ <h2>Extending the universal intro</h2>
 them as children of the 'hidden' element.
 </p>
 
-<h3>Contributing into extensions</h3>
+<h3>Contributing Into Extensions</h3>
 
 <p>
 An extension contributed into one of the root pages can itself contain 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_links.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_links.htm
index bdccf4456d6..5f1d8cfad39 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_links.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_links.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Managing links</h2>
+<h2>Managing Links</h2>
 
 <p>
 Most of the extensions coming into the main Welcome pages offer links to open 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_preference.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_preference.htm
index e08873e0d87..d07539271f8 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_preference.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_preference.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Adding the preference page</h2>
+<h2>Adding the Preference Page</h2>
 
 <p>
 The combination of product properties and default preference values can fully 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm
index 192d8595f02..d8e9c48ceb9 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm
@@ -9,7 +9,7 @@
 </head>
 <body>
 
-<h2>Using XHTML as intro content</h2>
+<h2>Using XHTML as Intro Content</h2>
 
 <p>Depending on the usage scenario of the intro framework,  XHTML files can be contributed as intro content. 
 The idea is to use the fact that XHTML is well formed XML and parse each document, manipulating the DOM to allow for contributions and extensions to be merged. Three xml elements from the 3.0 intro markup where used to extend the XHTML 1.0 element list. These are <code>include</code>, <code>anchor</code>, and <code> contentProvider</code>:</p>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling.htm
index bbb2cb7da93..3f73bbaee85 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Status handling</h2>
+<h2>Status Handling</h2>
 
 <p>
 Status handling is a facility that 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_defining.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_defining.htm
index 93d2d3fe0ea..9d4cb1016c1 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_defining.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_defining.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Defining a product status handler</h2>
+<h2>Defining a Product Status Handler</h2>
 
 <p> 
 The <a href="../reference/api/org/eclipse/ui/statushandlers/AbstractStatusHandler.html"><b>AbstractStatusHandler</b></a> 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_sample.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_sample.htm
index 9533b09c9e5..04fb9b9c132 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_sample.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_sample.htm
@@ -10,7 +10,7 @@
 </head>
 <body>
 
-<h2>Contributing a sample handler</h2>
+<h2>Contributing a Sample Handler</h2>
 
 <p>
 We will now contribute a very basic status handler just to illustrate the steps 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench.htm
index 2d2fdd764a5..b5f5a06b51e 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench.htm
@@ -24,7 +24,7 @@ <H1>
 perspective.&nbsp; We will show how a plug-in can contribute to the workbench
 UI.</P>
 <h2>
-Quick tour of the workbench</h2>
+Quick Tour of the Workbench</h2>
 <P >
 The workbench is the cockpit for navigating all of the functionality provided by plug-ins.
 By using the workbench, we can navigate resources and we can view and edit
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm
index 4c0107af23f..4327f22243c 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm
@@ -38,7 +38,7 @@ <h3>Activities</h3>An <b>activity</b> is a logical grouping of functionality tha
   </ul>
 
 
-  <h4>Conventional activities</h4>Conventional activities are exposed to the
+  <h4>Conventional Activities</h4>Conventional activities are exposed to the
   user under the name <em>capabilities</em>, although not in a way that is
   apparent to a new user. When an activity is enabled in the platform, the UI
   contributions associated with that activity are shown. When a activity is
@@ -62,7 +62,7 @@ <h4>Conventional activities</h4>Conventional activities are exposed to the
   activities can also still be used programmatically using the Eclipse API.
   </p>
 
-  <h4>Expression-based activities</h4>
+  <h4>Expression-based Activities</h4>
   
   Expression-based activities differ from conventional activities in that:
 
@@ -78,7 +78,7 @@ <h4>Expression-based activities</h4>
     to, for example, the <b>New...</b> wizard.</li>
   </ul>
 
-  <h3>Conventional Activities vs. perspectives</h3>We have seen
+  <h3>Conventional Activities vs. Perspectives</h3>We have seen
   (in <A href="workbench_perspectives.htm">Perspectives</a>) how perspectives are used to
   organize different view layouts and action sets into tasks. Why do we need
   activities? While perspectives and activities define similar kinds of tasks,
@@ -104,7 +104,7 @@ <h3>Conventional Activities vs. perspectives</h3>We have seen
   concepts.
   </p>
 
-  <h3>Defining activities</h3>Activities are defined using the <b><A href="../reference/extension-points/org_eclipse_ui_activities.html">org.eclipse.ui.activities</a></b>
+  <h3>Defining Activities</h3>Activities are defined using the <b><A href="../reference/extension-points/org_eclipse_ui_activities.html">org.eclipse.ui.activities</a></b>
 
   extension point.<br>
   Let's look at first at a simplified version of how the Eclipse SDK
@@ -164,7 +164,7 @@ <h3>Defining activities</h3>Activities are defined using the <b><A href="../refe
   expression-based activities can be also added to categories, but
   they are ignored when the user changes states of these categories.
 
-  <h4>Binding activities to UI contributions</h4>Activities can be associated
+  <h4>Binding Activities to UI Contributions</h4>Activities can be associated
   with UI contributions by referring to them by id, or by pattern matching. The
   pattern matching used in activity pattern bindings follows the rules
   described in the <b>java.util.regex</b> package for regular expressions. The
@@ -230,7 +230,7 @@ <h4>Binding activities to UI contributions</h4>Activities can be associated
   use their own format for identifying contributions and for pattern-matching
   against those names.
 
-  <h4>Binding activities to help contributions</h4>Activities are associated
+  <h4>Binding Activities to Help Contributions</h4>Activities are associated
   with help contributions using the same pattern matching scheme used for UI
   contributions. The second part of the identifier (the local identifier)
   indicates the name of the table of contents (TOC) file. For example, the
@@ -260,7 +260,7 @@ <h4>Binding activities to help contributions</h4>Activities are associated
 activity will hide the "Examples" section from the "JDT Plug-in
 Developer Guide" book.
 
-  <h4>Using the activities API</h4>
+  <h4>Using the Activities API</h4>
   
   The workbench activity support includes an API for working
   with all defined activities (to some extent also expression-based
@@ -309,7 +309,7 @@ <h4>Using the activities API</h4>
   activities, or similar requests that do not apply to expression-based activities.
   </p>
 
-  <h4>Using expression-based activities</h4>
+  <h4>Using Expression-based Activities</h4>
   
   To filter a UI element using an expression-based activity, create an activity like the
   following:<br>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm
index 405e99ba37f..a033db05756 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm
@@ -22,7 +22,7 @@ <h3>
 in time.  For example, the commands available to a user while editing text might be different than those
 available to a user while editing Java text or browsing packages in the package explorer.
 </P>
-<h4>Defining a context</h4>
+<h4>Defining a Context</h4>
 <p>
 Contexts are declared in the
 <b><a href="../reference/extension-points/org_eclipse_ui_contexts.html">org.eclipse.ui.contexts</a></b>
@@ -39,7 +39,7 @@ <h4>Defining a context</h4>
 </pre>
 Contexts are assigned a name and description that are used when showing information about the context to the user.
 The id of the context is used when binding UI contributions such as commands to a particular context.
-<h4>Context hierarchies</h4>
+<h4>Context Hierarchies</h4>
 <p>
 Contexts are hierarchical in nature.  When a context is active, the commands available in the context and in its parent contexts
 are also available.  This is useful for defining levels of contexts that move from very general situations down to more
@@ -67,7 +67,7 @@ <h4>Context hierarchies</h4>
 	id="org.eclipse.ui.contexts.dialogAndWindow"&gt;
 &lt;/context&gt;
 </pre>
-<h4>Associating a contribution with a context</h4>
+<h4>Associating a Contribution With a Context</h4>
 <p>
 So far, all we've done is define a hierarchy of contexts.  The context becomes useful when it is referenced in the
 description of another UI contribution.  The most common use of contexts is in key bindings.  When a context is
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_bindings.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_bindings.htm
index 12d78cea50d..3ef26f4f27e 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_bindings.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_bindings.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h3>Key bindings</h3>
+<h3>Key Bindings</h3>
 
 
 <p>The association between a command and the key combinations that should
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_commands.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_commands.htm
index 6ce0d863338..91a3507dc4b 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_commands.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_commands.htm
@@ -31,7 +31,7 @@ <h3>Commands</h3>
 behaviour implemented in different plug-ins may share the same key binding.</p>
 
 
-<h4>Defining a command</h4>
+<h4>Defining a Command</h4>
 
 
 <p>Commands are defined using the <b><a href="../reference/extension-points/org_eclipse_ui_commands.html">org.eclipse.ui.commands</a></b>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_handlers.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_handlers.htm
index 35d87b405c5..1ba24baf5ae 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_handlers.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_handlers.htm
@@ -26,7 +26,7 @@ <h3>Handlers</h3>
 command has an active handler, we say the command is handled.
 </p>
 
-<h4>Associating a default handler with a command</h4>
+<h4>Associating a Default Handler With a Command</h4>
 
 <p>
 While there is a shortcut for a default handler, most handlers are associated
@@ -63,7 +63,7 @@ <h4>Associating a default handler with a command</h4>
 </pre>
 
 
-<h4>Associating a handler with a command while a part type is active</h4>
+<h4>Associating a Handler With a Command While a Part Type Is Active</h4>
 
 <p>
 The &lt;activeWhen/&gt; expressions in the plugin.xml and programmatic core
@@ -161,7 +161,7 @@ <h4>Associating a handler with a command while a part type is active</h4>
 against the default variable.
 </p>
 
-<h4>Associating a handler programmically with a command while a specific part is active</h4>
+<h4>Associating a Handler Programmically With a Command While a Specific Part Is Active</h4>
 
 <p>
 Sometimes it is desirable to instantiate your handlers when your part is
@@ -220,7 +220,7 @@ <h4>Associating a handler programmically with a command while a specific part is
 </ol>
 
 
-<h4>Implementing the handler</h4>
+<h4>Implementing the Handler</h4>
 <p>
 A handler must implement 
 <a href="../reference/api/org/eclipse/core/commands/IHandler.html">org.eclipse.core.commands.IHandler</a>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_menus.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_menus.htm
index fcb357abbdf..355f3e714bf 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_menus.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_menus.htm
@@ -27,7 +27,7 @@ <h3>org.eclipse.ui.menus</h3>
 trim locations.
 </p>
 
-<h4>Contribution location</h4>
+<h4>Contribution Location</h4>
 <p>
 The <b>org.eclipse.ui.menus</b>
 extension point requires the id of a menu, toolbar, or trim area and an insertion
@@ -134,7 +134,7 @@ <h4>Contribution location</h4>
          &lt;/enabledWhen&gt;
 </pre>
 
-<h4>Contribution visibility</h4>
+<h4>Contribution Visibility</h4>
 
 <p>
 A command's enabled state is controlled by a combination of the command
@@ -303,7 +303,7 @@ <h4>Contribution visibility</h4>
 enabled state track the current selection.
 </p>
 
-<h4>Contributing to popup menus</h4>
+<h4>Contributing to Popup Menus</h4>
 
 <p>
 Commands can be contributed to a specific context menu by the context menu's id, or to any
@@ -353,7 +353,7 @@ <h4>Contributing to popup menus</h4>
 </p>
 
 
-<h4>Adding toolbars to trim areas</h4>
+<h4>Adding Toolbars to Trim Areas</h4>
 <p>
 A 'trim' widget is a control that gets sited into a location (called a 'Trim Area') on the outer boundary of the Workbench Window. The
 most common example is the generic 'status line' which almost all GUI's place along the bottom of the window.
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm
index 4a3d40d9897..e318212a6a7 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm
@@ -14,7 +14,7 @@
 </head>
 <body style="background-color: rgb(255, 255, 255);">
 <h2>
-Workbench concurrency support</h2>
+Workbench Concurrency Support</h2>
 <p>
 We've seen that the JFace UI framework provides basic support for
 showing task progress in a dialog (see <a href="jface_operations.htm">Long
@@ -123,7 +123,7 @@ <h2>
     </p>
   </li>
 </ul>
-<h3>Progress service</h3>
+<h3>Progress Service</h3>
 <p>
 The workbench progress service (<a
  href="../reference/api/org/eclipse/ui/progress/IProgressService.html">IProgressService</a>)
@@ -189,7 +189,7 @@ <h3>Progress service</h3>
    service.<b>registerIconForFamily</b>(newImage, ResourcesPlugin.FAMILY_MANUAL_BUILD);
    service.registerIconForFamily(newImage, ResourcesPlugin.FAMILY_AUTO_BUILD);
 </pre>
-<h3><a name="site_service"></a>Showing that a part is busy</h3>
+<h3><a name="site_service"></a>Showing That a Part is Busy</h3>
 <p>
 <a
  href="../reference/api/org/eclipse/ui/progress/IWorkbenchSiteProgressService.html"><b>IWorkbenchSiteProgressService</b></a>
@@ -239,7 +239,7 @@ <h3><a name="job_properties"></a>Progress Properties for Jobs</h3>
    job.setUser(true);
    job.schedule();
 </pre>
-<h3>Workbench jobs</h3>
+<h3>Workbench Jobs</h3>
 <p>
 Where possible, long running operations should be performed outside of
 the UI thread. However, this cannot always be
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm
index 8d515da9b2f..e79beb362c5 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm
@@ -41,7 +41,7 @@ <h2>
 
 
 <h3>
-Workbench part layout</h3>
+Workbench Part Layout</h3>
 <P >
 One of the main jobs of an <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b>
 is to describe the placement of the editor and the views in the workbench window. Note that these layouts are different than the
@@ -82,8 +82,7 @@ <h3>
 
 
 <h3>
-<a name="showin">
-Linking views and editors</a> with &quot;show-in&quot;</h3>
+<a name="showin">Linking views and editors</a> with &quot;show-in&quot;</h3>
 
 
 
@@ -119,8 +118,7 @@ <h3>
 
 
 
-<h4>
-Show-in source</h4>
+<h4>Show-in Source</h4>
 <p>If you want to allow users to use <b>Navigate &gt; Show In</b> from your
 editor or view to jump to another view, you must implement <a href="../reference/api/org/eclipse/ui/part/IShowInSource.html"><b>IShowInSource</b></a>.&nbsp;
 Your part can supply its <a href="../reference/api/org/eclipse/ui/part/IShowInSource.html"><b>IShowInSource</b></a>
@@ -147,8 +145,7 @@ <h4>
 
 
 
-<h4>
-Show-in target</h4>
+<h4>Show-in Target</h4>
 
 
 
@@ -162,7 +159,7 @@ <h4>
 first in deciding what to show, since this is the more specific
 information.&nbsp; It should show the input element only if no selection is
 indicated.</p>
-<h4>Presenting appropriate targets</h4>
+<h4>Presenting Appropriate Targets</h4>
 
 
 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm
index a2f1217686c..f856357175f 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm
@@ -14,7 +14,7 @@
 <BODY>
 
 <h2>
-Workbench resource support</h2>
+Workbench Resource Support</h2>
 <P>
 The Eclipse platform is structured so that you can develop a workbench application even if your application
 has nothing to do with the platform resource model.  However, the workbench does provide support for
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm
index 09438b922df..55b92dc6258 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm
@@ -14,7 +14,7 @@
 <BODY>
 
 <h2>
-Filtering large user interfaces</h2>
+Filtering Large User Interfaces</h2>
 <P>
 The rich extensibility mechanisms in the workbench provide many ways for plug-ins to contribute to the platform
 UI.  However, extensibility can introduce its own set of problems.  While allowing for a rich set of features
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling.htm
index bd29896efff..1f1fb276b56 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling.htm
@@ -10,13 +10,13 @@
 </head>
 <body>
 
-<h2>Status handling</h2>
+<h2>Status Handling</h2>
 
 Status handling is a facility that allows to introduce a custom way of showing problems 
 in the Eclipse based applications to users. The facility can be configured at both 
 the application and the product level.
 
-<h3><a name="statusHandlers">Status handlers</a></h3>
+<h3><a name="statusHandlers">Status Handlers</a></h3>
 
 <p>
 The handlers are responsible for presenting problems by logging or showing appropriate 
@@ -48,7 +48,7 @@ <h3><a name="statusHandlers">Status handlers</a></h3>
 and parameter set are set during initialization of the handler with the use of elements 
 and attributes of the <b>statusHandler</b> element. 
 
-<h4>Logging with the use of the default logging mechanism</h4>
+<h4>Logging With the Use of the Default Logging Mechanism</h4>
 
 <p>
 In order to log extra information with the use of the default logging mechanism, 
@@ -75,7 +75,7 @@ <h4>Logging with the use of the default logging mechanism</h4>
 </pre>
 
 
-<h4>The default status handler</h4>
+<h4>The Default Status Handler</h4>
 
 <p>
 The platform supplies its own status handler implementation <em>org.eclipse.ui.statushandlers.WorkbenchErrorHandler</em>.
@@ -83,7 +83,7 @@ <h4>The default status handler</h4>
 and a dialog based on the JFace <em>org.eclipse.jface.dialogs.ErrorDialog</em>.
 </p>
 
-<h4>Registering the ErrorSupportProvider with your status handler</h4>
+<h4>Registering the ErrorSupportProvider With Your Status Handler</h4>
 
 <p>
 There is a simple way to contribute a support area in the JFace <em>ErrorDialog</em>. 
@@ -113,7 +113,7 @@ <h4>Registering the ErrorSupportProvider with your status handler</h4>
 support area.
 </p>
 
-<h3>Status manager</h3>
+<h3>Status Manager</h3>
 
 <p>
 The status manager is the entry point for all statuses that are to be displayed in the user interface. 
@@ -153,7 +153,7 @@ <h3>Status manager</h3>
 If any creation error occurs in the product handler, the workbench handler will process this error. 
 </p>
 
-<h3><a name="acceptableStyles">Acceptable styles</a></h3>
+<h3><a name="acceptableStyles">Acceptable Styles</a></h3>
 
 <p>
 Below is a list of StatusManager styles which can be combined with logical OR:</p>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling_defining.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling_defining.htm
index 6587abec604..3e03462e6fa 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling_defining.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling_defining.htm
@@ -12,7 +12,7 @@
 </head>
 <body>
 
-<h2>Defining a status handler</h2>
+<h2>Defining a Status Handler</h2>
 
 <p>There are two ways for contributing handlers to the Workbench:</p>
 <ol>
@@ -23,7 +23,7 @@ <h2>Defining a status handler</h2>
 </ol>
 
 
-<h3>Contributing a status handler using the custom advisor</h3>
+<h3>Contributing a Status Handler Using the Custom Advisor</h3>
 
 <p>First, a custom workbench advisor for your application has
 to be created. In this new custom advisor override <em>getWorkbenchErrorHandler()</em>. 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm
index 892da8d4c96..48250f64698 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h2>Accessible user interfaces</h2>
+<h2>Accessible User Interfaces</h2>
 <p>The term accessible is used to refer to software that has been designed so
 that people who have disabilities have a successful interaction with it.&nbsp;
 Accessible software takes many different kinds of disabilities into account:</p>
@@ -29,7 +29,7 @@ <h2>Accessible user interfaces</h2>
   <li>cognitive - people who have learning disabilities and may need more
     consistency or simplicity in their interfaces</li>
 </ul>
-<h3>Assistive technology</h3>
+<h3>Assistive Technology</h3>
 <p><b>Assistive technology</b> is equipment or software that is used to increase
 the accessibility of existing operating systems and applications.&nbsp; While it
 is beyond the scope of this programmer's guide to cover the broad scope of
@@ -38,14 +38,14 @@ <h3>Assistive technology</h3>
 documentation, such as providing alternate text descriptions for images in your HTML, or
 keyboard equivalents for all of your software actions, can greatly improve the
 effectiveness of assistive technologies that make use of these techniques.</p>
-<h3>Accessibility resources</h3>
+<h3>Accessibility Resources</h3>
 <p>There are some basic coding tips you can use when building plug-in user
 interfaces that will increase the accessibility of your software.&nbsp; See <a href="../reference/misc/ui_accessibility_tips.html">Tips
 for Making User Interfaces More Accessible</a> for more information.</p>
 <p><a href="http://www-03.ibm.com/able/index.html">IBM's Accessibility Center
 Website</a> has many useful resources for accessibility, including <a href="http://www-03.ibm.com/able/guidelines">guidelines
 and checklists</a> for developing software and web interfaces.</p>
-<h3>SWT and accessibility</h3>
+<h3>SWT and Accessibility</h3>
 <p>Because SWT uses the operating system's native widgets, user interfaces built
 with SWT will inherit any assistive technologies that have been installed on the
 host operating system.&nbsp; SWT implements an interface, <a href="../reference/api/org/eclipse/swt/accessibility/AccessibleListener.html"><b>AccessibleListener</b></a>,
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_commands_handlers.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_commands_handlers.htm
index a1ead182dfb..1b96a363190 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_commands_handlers.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_commands_handlers.htm
@@ -32,7 +32,7 @@ <h3>Commands</h3>
 actions implemented in different plug-ins may share the same key binding.</p>
 
 
-<h4>Defining a command</h4>
+<h4>Defining a Command</h4>
 
 
 <p>Commands are defined using the <b><a href="../reference/extension-points/org_eclipse_ui_commands.html">org.eclipse.ui.commands</a></b>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_efs_resources.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_efs_resources.htm
index 019567d9d22..ae108ad25dc 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_efs_resources.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_efs_resources.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h3>User interface support for alternative file systems</h3>
+<h3>User Interface Support for Alternative File Systems</h3>
 
 <p>In environments where there is more than one file system there are several 
   places in the user interface where the user can select a file system.</p>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm
index 323be569b3b..8f73c36d6fa 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm
@@ -15,7 +15,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h3>Text file encoding</h3>
+<h3>Text File Encoding</h3>
 <p>If your plug-in reads text files, it should honor the <b>text file encoding</b>
 preference in the workbench.&nbsp; </p>
 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm
index 12d42e3bb55..b03957c387d 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h2>Workbench key bindings</h2>
+<h2>Workbench Key Bindings</h2>
 <p>The workbench defines many keyboard accelerators for invoking common actions
 with the keyboard.&nbsp; In early versions of the platform, plug-ins could
 define the accelerator key to be used for their action when the action was
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm
index af179f7f093..d83085c0439 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm
@@ -69,7 +69,7 @@ <h3>Schemes</h3>
 active, the sequence &quot;Ctrl+X Ctrl+S&quot; will invoke the command. </p>
 
 
-<h4>Defining new schemes</h4>
+<h4>Defining New Schemes</h4>
 
 
 <p>When your plug-in defines a binding, it will most likely assign it to an existing
@@ -99,7 +99,7 @@ <h4>Defining new schemes</h4>
 schemes.</p>
 
 
-<h4>Activating a scheme </h4>
+<h4>Activating a Scheme </h4>
 
 
 <p>The user controls the active scheme via the preferences page.&nbsp;
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm
index d0456d34c92..07815efdbca 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h3>Key bindings</h3>
+<h3>Key Bindings</h3>
 
 
 <p>The association between a command and the key combinations that should
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm
index 54bb3181f0c..8eed53912a1 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm
@@ -21,7 +21,7 @@ <h3>Commands</h3>
 them in menus.
 </p>
 
-<h4>Associating a legacy action with a command</h4>
+<h4>Associating a Legacy Action With a Command</h4>
 
 
 <p>When still using the old legacy action extension points, actions can be associated with a 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm
index db5fc62e220..c272ea2a792 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h3>Contexts and key bindings</h3>
+<h3>Contexts and Key Bindings</h3>
 
 <p>A <b> context</b> can be specified for a key binding so that the binding is only available when the user is
 working within a specific context.  Contexts are declared in the
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_marker_support.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_marker_support.htm
index 99069594708..558a710e977 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_marker_support.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_marker_support.htm
@@ -15,7 +15,7 @@
 </head>
 
 <body>
-<h2>Support for displaying markers</h2>
+<h2>Support for Displaying Markers</h2>
 <p>The <a
 	href="../reference/extension-points/org_eclipse_ui_ide_markerSupport.html">org.eclipse.ui.ide.markerSupport</a>
 extension point provides facilities for controlling how markers are
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm
index 7181b424e7d..861c542b36a 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h4>Contributing marker help</h4>
+<h4>Contributing Marker Help</h4>
 <p>Now we are ready to look at how to add help to the readme tool's
 markers.&nbsp; Adding marker help is done using the <b><a href="../reference/extension-points/org_eclipse_ui_ide_markerHelp.html">org.eclipse.ui.ide.markerHelp</a></b>
 extension point.&nbsp; This extension point allows plug-ins to associate a help
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm
index 769712c4119..897a35708cd 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h4>Contributing marker resolution</h4>
+<h4>Contributing Marker Resolution</h4>
 <p>Plug-ins can also define marker resolutions, so that their problem markers can
 participate in the workbench <b>Quick Fix</b> feature. Users can select
 a problem marker and choose a <b>Quick Fix</b> from a popup containing the list of supplied
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm
index 07b88e0af66..0b16d87c337 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h3>Marker help and resolution</h3>
+<h3>Marker Help and Resolution</h3>
 <p>In <a href="resAdv_markers.htm">Resource markers</a>, we saw how plug-ins can
 define specialized marker types in order to annotate resources with
 information.&nbsp; The <a href="../samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html">readme
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm
index 160b1ef112a..6161ce2ca21 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h2>Honoring single click support</h2>
+<h2>Honoring Single Click Support</h2>
 <p>The General <b>Preferences</b> allow users to specify whether views should 
   open their objects on single or double click. </p>
 
@@ -37,7 +37,7 @@ <h2>Honoring single click support</h2>
 click.</p>
 
 
-<h3>Single click in JFace viewers</h3>
+<h3>Single Click in JFace Viewers</h3>
 
 
 <p>If you are using a <a href="jface_viewers.htm#listviewer">JFace list-oriented
@@ -52,7 +52,7 @@ <h3>Single click in JFace viewers</h3>
 such as expanding the items in a tree on double-click.</p>
 
 
-<h3>Single click in SWT controls</h3>
+<h3>Single Click in SWT Controls</h3>
 
 
 <p>JFace provides a utility class, <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>, 
@@ -83,7 +83,7 @@ <h3>Single click in SWT controls</h3>
 This means that the &quot;right thing&quot; will happen if you use JFace viewers
 or the <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>
 class to implement open behavior.</p>
-<h3>Activating editors on open</h3>
+<h3>Activating Editors on Open</h3>
 <p>When handling an open event, you should use <b>OpenStrategy.activateOnOpen() </b>to
 determine whether an opened editor should be activated by default.&nbsp;
 Activating an editor switches the focus from the view to the editor, which can
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm
index 6dd66edbafc..8cd30cec15f 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h2>Undoable operations</h2>
+<h2>Undoable Operations</h2>
 <p>We've looked at many different ways to contribute commands to the workbench, but we
 haven't focused on the implementation of a command's <tt>execute(ExecutionEvent)</tt> method.
 The mechanics
@@ -28,7 +28,7 @@ <h2>Undoable operations</h2>
 <a href="../reference/api/org/eclipse/core/commands/operations/IUndoableOperation.html"><b>IUndoableOperation</b></a>,
 the operation can be made available for undo and redo.  Converting an command or action to use operations is straightforward, 
 apart from implementing the undo and redo behavior itself.</p>
-<h3>Writing an undoable operation</h3>
+<h3>Writing an Undoable Operation</h3>
 <p>
 We'll start by looking at a very simple example.  Recall the simple
 example in <b>org.eclipse.ui.examples.contributions.editor.DeltaInfoHandler</b>.
@@ -100,7 +100,7 @@ <h3>Writing an undoable operation</h3>
 to use operations is similar to converting an <tt>execute</tt> method.  The method is responsible for creating
 and executing an operation that does the work previously done inline.
 </p>
-<h3>Operation history</h3>
+<h3>Operation History</h3>
 <p>
 So far we've used an <b>operations history</b> without really explaining it.
 Let's look again at the code that creates our example operation.</p>
@@ -142,7 +142,7 @@ <h3>Operation history</h3>
 to set limits on the history or notify listeners about changes to a particular operation.  Before
 we look at the protocol in detail, we need to understand the <b>undo context</b>.
 
-<h4>Undo contexts</h4>
+<h4>Undo Contexts</h4>
 <p>
 When an operation is created, it is assigned an <b>undo context</b> that describes the user context in which the original
 operation was performed.  The undo context typically depends on the view or editor that originated the undoable operation.  For
@@ -256,7 +256,7 @@ <h4>Undo contexts</h4>
 }
 </pre> 
 
-<h3>Undo and redo action handlers (Deprecated)</h3>
+<h3>Undo and Redo Action Handlers (Deprecated)</h3>
 <p>The platform provides standard undo and redo <b>retargetable action handlers</b> 
 that can be configured by views and editors to provide undo and redo support for their particular context.  When the 
 action handler is created, a context is assigned to it so that the operations history is filtered in a way appropriate for
@@ -270,7 +270,7 @@ <h3>Undo and redo action handlers (Deprecated)</h3>
 be disposed when the operation currently available for undo or redo is not valid.  The setting for this parameter
 is related to the undo context provided and the validation strategy used by operations with that context.
 
-<h3>Application undo models</h3>
+<h3>Application Undo Models</h3>
 <p>
 Earlier we looked at how undo contexts can be used to implement different kinds of application undo models.
 The ability to assign one or more contexts to operations allows applications to implement undo strategies that
@@ -287,7 +287,7 @@ <h3>Application undo models</h3>
 of its position in the history.  The operation history can be configured so that the model appropriate for an
 application can be implemented.  This is done with an interface that is used to pre-approve any undo or redo request
 before the operation is undone or redone.</p>
-<h4>Operation approvers</h4>
+<h4>Operation Approvers</h4>
 <a href="../reference/api/org/eclipse/core/commands/operations/IOperationApprover.html"><b>IOperationApprover</b></a>
 defines the protocol for approving undo and redo of a particular operation.  An operation approver is installed on an operation history.  Specific
 operation approvers may in turn check all operations for their validity, check operations of only certain contexts,
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm
index d24cb6bfcde..e491cfbf184 100644
--- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm
+++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm
@@ -14,7 +14,7 @@
 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY>
-<h2>Working sets</h2>
+<h2>Working Sets</h2>
 <p>Users often find it necessary to filter views such as the navigator view in
 order to reduce clutter.&nbsp; Plug-ins can assist in filtering using different
 techniques.</p>
@@ -52,7 +52,7 @@ <h2>Working sets</h2>
 </b>also provides property change notification as working sets are added,
 removed, or as they change.&nbsp; If your view or editor needs to respond to
 changes in the selected working set, it can add a listener for <b>CHANGE_WORKING_SET_CONTENT_CHANGE.</b></p>
-<h3>Adding new working set types</h3>
+<h3>Adding New Working Set Types</h3>
 
 
 <p>For many plug-ins, using <b><a href="../reference/api/org/eclipse/ui/IWorkingSetManager.html">IWorkingSetManager</a>