Fix common spelling errors in documentation

Copilot · laeubi · Copilot · commit 6407c0390d7d · 2025-10-02T07:44:28.000Z
Co-authored-by: laeubi &lt;1331477+laeubi@users.noreply.github.com&gt;
diff --git a/eclipse.platform.common/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-search.htm b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-search.htm
@@ -74,7 +74,7 @@ <h1>
         <tr>
           <td valign="top">
             <p>
-              Implementors
+              Implementers
             </p>
 
           </td>
diff --git a/eclipse.platform.common/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-search.htm b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-search.htm
@@ -110,7 +110,7 @@ <h2 class="Head">Limit To</h2>
     <ul>
       <li>Declarations</li>
 
-      <li>Implementors (available only when searching for types)</li>
+      <li>Implementers (available only when searching for types)</li>
 
       <li>References</li>
 
diff --git a/eclipse.platform.common/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-search.htm b/eclipse.platform.common/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-search.htm
@@ -131,7 +131,7 @@ <h1>
       <tr align="left" valign="top">
         <td align="left" valign="top">
           <p>
-            Implementors
+            Implementers
           </p>
         </td>
         <td>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ant_developing.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ant_developing.htm
@@ -49,7 +49,7 @@ <h2>
 <p>
   The <code>org.eclipse.ant.core</code> plugin can be used as an example of how to set up a plugin that contributes tasks within Eclipse. 
  For development and testing of this plugin within Eclipse, an external tool builder
- explictly generates the tasks JAR when triggered on specific resource changes.
+ explicitly generates the tasks JAR when triggered on specific resource changes.
 </p>  
 
 <p>Also see <a href="ant_contributing_task.htm">Contributing tasks and types</a>.</p>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/cnf.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/cnf.htm
@@ -144,7 +144,7 @@ <h2>Navigators - Where the CNF Fits</h2>
 </ol>
 
 <p>The only navigator intended for general purpose client use if the
-CNF, which can be used either by adding NCEs visable in the Project
+CNF, which can be used either by adding NCEs visible in the Project
 Explorer (if developing an IDE plugin), or using a separate instance of
 the CommonNavigator as a view.</p>
 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/cnf_config.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/cnf_config.htm
@@ -107,7 +107,7 @@ <h2>Viewer Configuration</h2>
 	transfer types to be used when starting a drag from the viewer.</li>
 	<li><b>options</b> - specifies options used to control the
 	presentation of the view. For example these allow hiding of menus and
-	buttons shown at the top of the view. Theses options are defined by <b><a
+	buttons shown at the top of the view. These options are defined by <b><a
 		href="../reference/api/org/eclipse/ui/navigator/INavigatorViewerDescriptor.html">INavigatorViewerDescriptor
 	</a> </b></li>
 </ol>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/console_shell.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/console_shell.htm
@@ -209,7 +209,7 @@ <h2>Starting an SSH Session With JAAS Authentication</h2>
   console prompt to explore commands to perform the following functions:</p>
   <ul>
     <li>adding, deleting, listing users</li>
-    <li>reseting and changing passwords</li>
+    <li>resetting and changing passwords</li>
     <li>adding and removing user roles</li>
   </ul>
 
@@ -508,7 +508,7 @@ <h2>Implementing Custom Console Commands</h2>
 
   <h2>Implementing Custom Tab Completion</h2>
 
-  <p>The Equinox console provides tab completion and allows implementors to provide their own
+  <p>The Equinox console provides tab completion and allows implementers to provide their own
   custom completion providers. This feature is available only when connecting through a Telnet
   or SSH session. Completion is available for:</p>
 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/debug_launch.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/debug_launch.htm
@@ -13,7 +13,7 @@
 <BODY>
 <h2>Launching a Program</h2>
 <p>The platform debug plug-ins allow your plug-in to extend the platform so that your
-partiticular type of program can be launched from the workbench, obtaining input from the user if
+particular type of program can be launched from the workbench, obtaining input from the user if
 necessary.  A unique type of program that can be launched in the platform is called a
 <b>launch configuration type</b>. The class 
 <a href="../reference/api/org/eclipse/debug/core/ILaunchConfiguration.html"><b>ILaunchConfiguration</b></a>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/debug_presentation.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/debug_presentation.htm
@@ -43,9 +43,9 @@ <h3>Debug Model Presentation</h3>
 model. The details are computed by the debug model presentation and passed
 to the details viewer. For example, the Java debugger uses the details
 viewer to show code assist in the variables view when expressions are evaluated.</p>
-<p>Implementors of <a href="../reference/api/org/eclipse/debug/ui/IDebugModelPresentation.html"><b>IDebugModelPresentation</b></a> may
+<p>Implementers of <a href="../reference/api/org/eclipse/debug/ui/IDebugModelPresentation.html"><b>IDebugModelPresentation</b></a> may
 also implement <a href="../reference/api/org/eclipse/debug/ui/IDebugEditorPresentation.html"><b>IDebugEditorPresentation</b></a> when
-more control is needed over the editor that is displaying source code for a stack frame.  Implementors may control the
+more control is needed over the editor that is displaying source code for a stack frame.  Implementers may control the
 editor's position or the annotations in the source.</p>
 
 </BODY>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards.htm
@@ -86,7 +86,7 @@ <h3>
 creating the SWT controls that represent the page</li>
   <li>
     
-determing when the user has supplied enough information to complete the page (that is, when the user can move to the next page.)
+determining when the user has supplied enough information to complete the page (that is, when the user can move to the next page.)
   </li>
 </ul>
 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/editors_hover.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/editors_hover.htm
@@ -88,7 +88,7 @@ <h3>Ruler Hover</h3>
 The hover class is configured as described above.&nbsp; <b><a href="../reference/api/org/eclipse/jface/text/source/IAnnotationHover.html">IAnnotationHover</a></b>
 is the interface for ruler hover objects.&nbsp; Although the name implies that
 the hover is designed for annotations in the ruler, it is really up to an
-individual editor to detemine what is appropriate.&nbsp; A ruler hover is responsible for returning the info string associated with a
+individual editor to determine what is appropriate.&nbsp; A ruler hover is responsible for returning the info string associated with a
 particular line number, regardless of the presence of markers on that line.&nbsp;&nbsp;&nbsp;</p>
 <p>The Java example editor's <b>JavaAnnotationHover</b>  implements hover for
 all lines.&nbsp; It uses the line number to
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_fieldassist.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_fieldassist.htm
@@ -185,7 +185,7 @@ <h3>Content Proposals</h3>
 IContentProposalProvider</a></b> allows you to implement a proposal provider with advanced features, such as filtering
 the proposals based on the control's content, providing explanatory labels in the popup instead of the actual
 content that will be inserted, and specifying the expected cursor position after a proposal is inserted.
-See the <b>Field Assist Example</b> and search for implementors of 
+See the <b>Field Assist Example</b> and search for implementers of 
 <b><a href="../reference/api/org/eclipse/jface/fieldassist/IContentProposalProvider.html">
 IContentProposalProvider</a></b> for advanced usage.
 </p>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm
@@ -47,7 +47,7 @@ <h3>Runnables and Progress</h3>
 method for this interface has an <b><a
  href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a>
 </b>parameter that is used to report progress and check for user
-cancelation.</p>
+cancellation.</p>
 <p><a
  href="../reference/api/org/eclipse/jface/operation/IRunnableContext.html"><b>IRunnableContext</b></a>
 is the interface for the different places in the UI where progress can
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/p2_actions_touchpoints.html b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/p2_actions_touchpoints.html
@@ -237,7 +237,7 @@ <h3>Eclipse Touchpoint Actions</h3>
 		</td>
 		<td>bundle</td>
 		<td>Uninstalls a bundle artifact with a bundle-id specified by
-		the paramter <i>bundle</i></td>
+		the parameter <i>bundle</i></td>
 	</tr>
 	<tr>
 		<td style="font-weight: bold;">addSourceBundle
@@ -470,7 +470,7 @@ <h2>Action Format</h2>
 <h2>Built-in Action Variables</h2>
 <p>What follows is a catalog of the variables made available by the
 phases and touchpoints. Many of these are mostly useful to the
-implementor of new actions and touchpoint types.</p>
+implementer of new actions and touchpoint types.</p>
 <h3>Variables Available in All Phases</h3>
 <table style="border: 1px solid #CCC; border-collapse: collapse;">
 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/p2_category_generation.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/p2_category_generation.htm
@@ -40,7 +40,7 @@ <h2><a name="category_def">Category Definition File</a></h2>
 
 <h2><a name="p2_inf">The p2.inf File</a></h2>
 <p>
-The p2.inf file is a properties file that can be used to customize capabilites, properties, and instructions. Information
+The p2.inf file is a properties file that can be used to customize capabilities, properties, and instructions. Information
 about this provisional file is available in the section 
 <a href="p2_customizing_metadata.html">Customizing p2 metadata</a>.
 
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/p2_director.html b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/p2_director.html
@@ -279,7 +279,7 @@ <h2>Arguments Description</h2>
 </dd>
 <dt>-trustedCertificates | -tc &lt;comma separated list&gt;</dt>
 <dd>
-The SHA-256 'fingerprints' of unanchored certficates to trust as signers of artifacts. An empty value will reject all unanchored certificates.
+The SHA-256 'fingerprints' of unanchored certificates to trust as signers of artifacts. An empty value will reject all unanchored certificates.
 </dd>
 <dt>-addJREIU</dt>
 <dd>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm
@@ -696,7 +696,7 @@ <h3 class="c2">
 
             <tr>
               <td>
-                <tt>desination</tt>
+                <tt>destination</tt>
               </td>
               <td>
                 Destination repositories, as outlined <a href=
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/product_configproduct.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/product_configproduct.htm
@@ -64,7 +64,7 @@ <h3>Window Images</h3>
 <pre>	&lt;property
 		name="windowImages"
 		value="icons/eclipse.png,icons/eclipse32.png"/&gt;</pre>
-<p>The <b>windowImages</b> property supercedes the <b>windowImage</b> property if
+<p>The <b>windowImages</b> property supersedes the <b>windowImage</b> property if
 both are specified.</p>
 <h3>Welcome Page</h3>
 <p>Products using the Eclipse 2.1 welcome page mechanism can specify the name and location
@@ -113,7 +113,7 @@ <h3>Splash Screens</h3>
 <p>The product splash screen is specified in the <tt>config.ini</tt> which is
   located underneath the product's <tt>configuration</tt> directory. The <b>osgi.splashPath</b> property
   in this file describes places to search for a file called <b>splash.bmp</b>.
-  The <strong>osgi.splashLocation </strong>property identifes a complete and
+  The <strong>osgi.splashLocation </strong>property identifies a complete and
   exact path to the splash screen file to use. Specifying a splash path allows
   for locale specific splash screens to be used as the given search path can
   indicate several plug-ins or fragments to search as well as <code>$nl$</code> style paths.
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/product_def_nl.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/product_def_nl.htm
@@ -95,7 +95,7 @@ <h4><a name="platform">Platform Core Mechanism</a></h4>
 </ul>
 <blockquote>
   <p><i>(Note:&nbsp; The <b>plugin.properties</b> and <b>fragment.properties </b>are
-  conspicuously absent from this list. They are treated in a sightly different way described below.)</i></p>
+  conspicuously absent from this list. They are treated in a slightly different way described below.)</i></p>
 </blockquote>
 <h4>Java Resource Bundles</h4>
 <p>The standard Java handling of property resource bundles is used for other
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/product_open_file.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/product_open_file.htm
@@ -32,7 +32,7 @@ <h2>Associate and Open Files</h2>
       Specifies a file to be opened.
   </li>
   <li><a href="../reference/misc/runtime-options.html#launcherdefaultaction">--launcher.defaultAction</a>
-      Specifies an action to take when the launcher is started witout any &quot;-&quot; arguments on 
+      Specifies an action to take when the launcher is started without any &quot;-&quot; arguments on 
       the command line.
   </li>
 </ul>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_api.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_api.htm
@@ -22,7 +22,7 @@ <h3>Using the File System API</h3>
 </p>
 <ul>
 <li>Plug-ins can install providers for different types of file systems.</li>
-<li>All methods integrate support for reporting progress and responding to cancelation,
+<li>All methods integrate support for reporting progress and responding to cancellation,
 making it easier to integrate into a graphical user interface.</li>
 <li>There is support for some additional functionality not available in <tt>java.io.File</tt>,
 such as getting and setting file permissions.</li>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/resAdv_hooks.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/resAdv_hooks.htm
@@ -37,7 +37,7 @@ <h3 >
 This hook allows the team plug-in and its providers to control
     how resource moves and deletes are implemented.&nbsp; The hook includes the ability to prevent
 these operations from
-    happening.&nbsp; Implementors can provide alternate implementations for
+    happening.&nbsp; Implementers can provide alternate implementations for
     moving or deleting files, folders, and projects.&nbsp;</P>
 
 <P >
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/resAdv_saving.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/resAdv_saving.htm
@@ -74,15 +74,15 @@ <H3>
    }</pre>
 <P >
 <b><a href="../reference/api/org/eclipse/core/resources/ISaveParticipant.html">
-ISaveParticipant</a></b> defines the protocol for a workspace save participant. Implementors of this
+ISaveParticipant</a></b> defines the protocol for a workspace save participant. Implementers of this
 interface can provide behavior for different stages of the save process.&nbsp;
 Let's look at the stages and how our class <b>WorkspaceSaveParticipant</b>
 implements each of these steps.</P>
 <ul>
   <li>
 <b>
 prepareToSave</b> notifies the participant that the workspace is about to be saved and that it should suspend normal operation until further notice.&nbsp;
-Our save particpant does nothing here.</li>
+Our save participant does nothing here.</li>
 </ul>
 <pre>
       public void prepareToSave(ISaveContext context) throws CoreException {
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/resInt_filters.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/resInt_filters.htm
@@ -22,7 +22,7 @@ <H2>Resource Filters</H2>
 <P >Resource filters can be created using the <b>IContainer.createFilter</b> method.</P>
 <P>
 The <b>FileInfoMatcherDescription</b> object has to be initialized with the ID of a <b>filterMatchers</b> extension point.  The org.eclipse.core.resources plugin
-specifiy one default filter matcher, of ID <b>org.eclipse.core.resources.regexFilterMatcher</b>, which accepts regular expressions Strings as argument.  Other plugins distributed with the workbench (such as the <b>org.eclipse.ui.ide</b> plugin) define other reusable filter matchers. 
+specify one default filter matcher, of ID <b>org.eclipse.core.resources.regexFilterMatcher</b>, which accepts regular expressions Strings as argument.  Other plugins distributed with the workbench (such as the <b>org.eclipse.ui.ide</b> plugin) define other reusable filter matchers. 
 </p>
 <P>
 Filter matchers are extensible through the <b>org.eclipse.core.resources.filterMatchers</b> extension point.
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/team_provider_repository.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/team_provider_repository.htm
@@ -271,7 +271,7 @@ <h3>Resource Modification Hooks<a Name="hooks"></a></h3>
  href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>
 appropriate for the provider.&nbsp; This hook allows providers to
 control how moves and deletes occur and includes the ability to prevent
-them from happening.&nbsp; Implementors can provide alternate
+them from happening.&nbsp; Implementers can provide alternate
 implementations for moving or deleting files, folders, and
 projects.&nbsp; The CVS client uses this hook to monitor folder
 deletions and ensure that any files contained in deleted folders are
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
@@ -51,7 +51,7 @@ <h4>Associating a Default Handler With a Command</h4>
 <p>
 <b>defaultHandler</b> points to the IHandler class that implements the default
 behaviour for this command.  The default handler will always be available unless
-overriden by a handler association in a more specific scope.  This is a shortcut
+overridden by a handler association in a more specific scope.  This is a shortcut
 for the equivalent <b>org.eclipse.ui.handlers</b> entry:</p>
 <pre>
       ...
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
@@ -34,7 +34,7 @@ <h2>
 should be used when the user first opens the perspective.</P>
 <P >
 Perspectives are implemented using&nbsp; <b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a>.&nbsp;
-</b>Implementors of
+</b>Implementers of
 <b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a></b>
 are expected to configure an <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b> with information that describes the
 perspective and its perspective page layout.</P>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html
@@ -102,7 +102,7 @@ <h2>
 The specification of API elements is generated from Javadoc comments in
 the element's Java source code. For some types of elements, the specification
 is in the form of a contract. For example, in the case of methods, the
-contract is between two parties, the caller of the method and the implementor
+contract is between two parties, the caller of the method and the implementer
 of the method. The fundamental ground rule is:
 <ul>
 <li>
@@ -274,7 +274,7 @@ <h2>
 an API interface if and only if they are allowed to implement it.
 <ul>
 <li>
-<b>Restricted implementors.</b> Do not implement an API interface that
+<b>Restricted implementers.</b> Do not implement an API interface that
 is documented as available only to certain parties unless you're one of
 them. In many situations, interfaces are used to hide internal implementation
 details from view.</li>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html
@@ -497,7 +497,7 @@ <h3>The Model-Fragment Header</h3>
   The <code>apply</code> attribute is optional and defaults to <code>always</code>. It can have the following values:
 </p>
 <ul>
-  <li><b>always</b>: each time the application started potentially replacing existing model elements and loosing information stored</li>
+  <li><b>always</b>: each time the application started potentially replacing existing model elements and losing information stored</li>
   <li><b>initial</b>: only when coming from a none persistent state</li>
   <li><b>notexists</b>: only if the given element does not exist already in the model</li>
 </ul>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/reference/misc/project_description_file.html b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/reference/misc/project_description_file.html
@@ -96,7 +96,7 @@ <h1>
 <li><b>arguments</b> - optional arguments that may be passed to the project
 builder.&nbsp; Corresponds to <code>ICommand.getArguments()</code>.</li>
 <li><b>dictionary</b> - a list of &lt;key, value&gt; pairs in the argument list.&nbsp;
-Analagous to <code>java.util.Map.</code></li>
+Analogous to <code>java.util.Map.</code></li>
 </ul>
 <p><code>&nbsp;&nbsp; &lt;!ELEMENT natures (nature)*&gt;</code></p>
 <p><code>&nbsp;&nbsp; &lt;!ELEMENT nature EMPTY&gt;</code></p>
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html
@@ -458,7 +458,7 @@ <h2>System Properties</h2>
      run. If the start-level (&gt;0 integer) is omitted then the framework will use the
      default start level for the bundle. If the &quot;start&quot; tag is added
      then the bundle will be marked as started after being installed.
-     Simple bundle locations are interepreted as relative to the framework's
+     Simple bundle locations are interpreted as relative to the framework's
      parent directory.  If the location is not a fully qualified path or URL then a search is done
      to find the highest version available.  Note that the reference: protocol can only be used to refer
      to content specified by a file: URL (e.g. reference:file:/path/to/mybundle_1.0.0.jar).
@@ -808,7 +808,7 @@ <h2>System Properties</h2>
     starting Eclipse. This property overrides any value set in <a href="#osgisplashpath">osgi.splashPath</a>.</dd>
   <dt id="osgisplashpath">osgi.splashPath</dt>
   <dd>a comma separated list of URLs to search for a file called splash.bmp.
-  This property is overriden by any value set in <a href="#osgisplashlocation">osgi.splashLocation</a>.</dd>
+  This property is overridden by any value set in <a href="#osgisplashlocation">osgi.splashLocation</a>.</dd>
   <dt id="osgistartlevel">osgi.startLevel</dt>
   <dd>the start level value the framework will be set to at startup.  The default value is 6.</dd>
   <dt id="osgistrictbundleentrypath">osgi.strictBundleEntryPath</dt>
