Fix additional spelling errors in documentation

Co-authored-by: laeubi <[email protected]>

Author: Copilot

eclipse.platform.common/bundles/org.eclipse.jdt.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>

eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/resInt_linked.htm

@@ -146,7 +146,7 @@ <H3>Compatibility with installed plug-ins</H3>
 Finally, there is a preference setting that can be used to disable linked resources
 for the entire workspace.  While the previous two veto mechanisms work
 on a per-project basis, this preference affects all projects in the workspace.  To
-set this preference programatically, use the preference <code>ResourcesPlugin.PREF_DISABLE_LINKING</code>.
+set this preference programmatically, use the preference <code>ResourcesPlugin.PREF_DISABLE_LINKING</code>.
 Note that even when set, users or plug-ins can override this by turning the preference
 off.
 </p>

eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_contributing.htm

@@ -125,7 +125,7 @@ <h4>Content Type Aliasing</h4>
 
 <p>This provides plug-ins with a placeholder they can refer to regardless the 
   preferred content type is available or not. If it is, the alias content type 
-  is supressed from the content type catalog and any references to it are interpreted 
+  is suppressed from the content type catalog and any references to it are interpreted 
   as references to the target content type. If it is not, the alias will be used 
   as an ordinary content type.</p>
 </BODY>

eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/runtime_model_bundles.htm

@@ -17,7 +17,7 @@ <H3>
 <p>
 The mechanics for supporting plug-ins are implemented using the <a href="https://docs.osgi.org/specification/osgi.core/7.0.0/">OSGi</a> framework.  From this
 standpoint, a plug-in is the same thing as an OSGi <b>bundle</b>.  The bundle and its associated classes specify and implement
-the process for Java class-loading, prequisite management, and the bundle's life-cycle.  For the rest of this discussion, we use
+the process for Java class-loading, prerequisite management, and the bundle's life-cycle.  For the rest of this discussion, we use
 the terms <b>plug-in</b> and <b>bundle</b> interchangeably, unless discussing a particular class in the framework.  
 </p>
 <h4>Plugin</h4>

eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/st_text_types.htm

@@ -52,7 +52,7 @@ <h4>Detailed Design</h4>
 following adaptations:</p>
 <ul>
   <li>There is only one separator, the comma(,). </li>
-  <li>This design can easily be adapted to accomodate a different separator,
+  <li>This design can easily be adapted to accommodate a different separator,
   like a semicolon (;) or a tab character, etc... </li>
 </ul>
 <b>Example:</b>

eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm

@@ -146,7 +146,7 @@ <H4>Resource disposal</H4>
 
 <ul>
   <li>If you create a graphic object or widget using a constructor, you must
-      explicitely dispose of it when you are finished using it.</li>
+      explicitly dispose of it when you are finished using it.</li>
   <li>When a
       <a href="../reference/api/org/eclipse/swt/widgets/Composite.html"><strong>Composite</strong></a>,
       is disposed, the composite and all of its child widgets are recursively disposed. In this

eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/team_model_repo.htm

@@ -481,7 +481,7 @@ <h2><a name="TeamContent"></a>Model Content in Team Viewers</h2>
 	for handling the transition from a model-based merge to a preview in a
 	dialog or Synchronize view.</li>
 </ul>
-<p>The following XML snipets illustrate how the CVS participant class
+<p>The following XML snippets illustrate how the CVS participant class
 is registered and how it's viewer is defined.</p>
 <pre style="background-color: rgb(204, 204, 255);">   &lt;extension point="org.eclipse.team.ui.synchronizeParticipants"&gt;
       &lt;participant

eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm

@@ -202,7 +202,7 @@ <h4>Repeated Subitems</h4>
 </pre>
 If the value of the variable is <code>1,b,three</code>, then three subitems will appear in the cheat sheet, each
 having a unique label ("Step 1," "Step b," "Step three").  The variable can be used in the label or the
-action paramater value.  It can also be accessed from the 
+action parameter 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>

eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm

@@ -46,7 +46,7 @@ <h2>Declaring a Context Id</h2>
 <p>
 <em>
 Note: The default implementation of help will display the help dialog tray only if
-the dialog is either large enough to accomodate it, or is resizable. Otherwise,
+the dialog is either large enough to accommodate it, or is resizable. Otherwise,
 an infopop will be shown.
 </em>
 </p>

eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_infocenter.htm

@@ -197,7 +197,7 @@ <h3>Making Information Center Available on the Web</h3>
 
 <p>
 Eclipse contains a complete information center and does not require any other server
-software to run. However, in an unsecure environment like the Internet, it is
+software to run. However, in an insecure environment like the Internet, it is
 not recommended to allow direct access by the clients, but instead made
 available through an HTTP server or an application server. Most servers come
 with modules or servlets for delegating certain request to other Web resources.