misc: fix spelling

Author: jbampton

bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ContentViewer.java

@@ -78,7 +78,7 @@ public void labelProviderChanged(LabelProviderChangedEvent event) {
 			Control control = getControl();
 			if (control == null || control.isDisposed()) {
 				if (logWhenDisposed) {
-					String message = "Ignored labelProviderChanged notification because control is diposed." + //$NON-NLS-1$
+					String message = "Ignored labelProviderChanged notification because control is disposed." + //$NON-NLS-1$
 							" This indicates a potential memory leak."; //$NON-NLS-1$
 					if (!InternalPolicy.DEBUG_LOG_LABEL_PROVIDER_NOTIFICATIONS_WHEN_DISPOSED) {
 						// stop logging after the first

bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/deferred/LazySortedCollection.java

@@ -521,7 +521,7 @@ private int getObjectIndex(Object value) {
 	/**
 	 * Redirects any pointers from the original to the replacement. If the replacement
 	 * causes a change in the number of elements in the parent tree, the changes are
-	 * propogated toward the root.
+	 * propagated toward the root.
 	 *
 	 * @since 3.1
 	 */

bundles/org.eclipse.ui.workbench/eclipseui/org/eclipse/ui/internal/handlers/ActionDelegateHandlerProxy.java

@@ -166,7 +166,7 @@ public final class ActionDelegateHandlerProxy implements ISelectionListener, ISe
 	 * @param element               The configuration element from which the real
 	 *                              class can be loaded at run-time; must not be
 	 *                              <code>null</code>.
-	 * @param delegateAttributeName The name of the attibute or element containing
+	 * @param delegateAttributeName The name of the attribute or element containing
 	 *                              the action delegate; must not be
 	 *                              <code>null</code>.
 	 * @param actionId              The identifier of the underlying action; may be

bundles/org.eclipse.ui.workbench/eclipseui/org/eclipse/ui/internal/handlers/HandlerProxy.java

@@ -127,7 +127,7 @@ public final class HandlerProxy extends AbstractHandlerWithState implements IEle
 	 * @param configurationElement The configuration element from which the real
 	 *                             class can be loaded at run-time; must not be
 	 *                             <code>null</code>.
-	 * @param handlerAttributeName The name of the attibute or element containing
+	 * @param handlerAttributeName The name of the attribute or element containing
 	 *                             the handler executable extension; must not be
 	 *                             <code>null</code>.
 	 */
@@ -247,7 +247,7 @@ private IPropertyChangeListener getEnablementListener() {
 	}
 
 	/**
-	 * Passes the dipose on to the proxied handler, if it has been loaded.
+	 * Passes the dispose on to the proxied handler, if it has been loaded.
 	 */
 	@Override
 	public void dispose() {
@@ -390,7 +390,7 @@ public String toString() {
 	}
 
 	/**
-	 * Retrives the ConfigurationElement attribute according to the
+	 * Retrieves the ConfigurationElement attribute according to the
 	 * <code>handlerAttributeName</code>.
 	 *
 	 * @return the handlerAttributeName value, may be <code>null</code>.

docs/Eclipse_Corner.md

@@ -697,7 +697,7 @@ How to Internationalize your Eclipse Plug-In
 This article is a roadmap for writing Eclipse plug-ins destined for the international market. We'll begin with a brief review of the motivations and technical challenges of internationalization, followed by step-by-step instructions of how to internationalize your Eclipse plug-in.
 
 *   [How to Internationalize your Eclipse Plug-In](http://www.eclipse.org/articles/Article-Internationalization/how2I18n.html)
-*   [Ukranian Translation](http://softdroid.net/how2I18n-ua)
+*   [Ukrainian Translation](http://softdroid.net/how2I18n-ua)
 
 
 
@@ -1053,7 +1053,7 @@ Development environments have become very complex. As a result, providing users
 BIRT Extension Mechanism, Part 1: Custom Report Items
 -----------------------------------------------------
 
-This article introduces the extension mechanism of BIRT report model, engine and designer, and shows how to create custom custom report items step-by-step.
+This article introduces the extension mechanism of BIRT report model, engine and designer, and shows how to create custom report items step-by-step.
 
 *   [BIRT Extension Mechanism, Part 1: Custom Report Items](http://www.eclipse.org/articles/article.php?file=Article-BIRT-ExtensionTutorial1/index.html)
 

docs/JFaceDataBinding.md

@@ -522,7 +522,7 @@ Usually, when creating a model-side observable, you call a method like BeansObse
 
 When the selected person changes, you could dispose the observable (and the binding) for the previously selected person and create new ones for the newly selected person, but there is a better way. By creating a _detail observable_, you can keep the same observable and binding and what you would have done manually is done for you by the framework automatically.
 
-To create a detail observable, first create an observable for the current selection (this is sometimes called the _master observable_), for example through ViewersObservables.observeSingleSelection(). Then, call BeansObservables.observeDetailValue(selectionObservable, "name", String.class) to create the detail observable for the currently selected person's name attibute.
+To create a detail observable, first create an observable for the current selection (this is sometimes called the _master observable_), for example through ViewersObservables.observeSingleSelection(). Then, call BeansObservables.observeDetailValue(selectionObservable, "name", String.class) to create the detail observable for the currently selected person's name attribute.
 
 For an example snippet, see the [Master Detail snippet](#Snippets).
 
@@ -676,7 +676,7 @@ Since the tests are JUnit3 tests you can integrate them into your tests in stand
 
 
 
-When subclassing, because of single inheritance, you will will have to create multiple implementations to test the mutable and immutable use cases (e.g. there would need to be a ButtonMutableObservableValueTest as well to test the mutable cases). The rest of the implementation should be straightforward. The only thing we ask is that you don't depend upon API other than the constructors. Tests are public because JUnit requires them to be, not because we want to commit to them as API. Over time we would like to have the opportunity to rename, add, remove, or optimize the test methods to ensure that we're getting the best coverage as possible. Because of the issues outlined above the preferred method is creating a JUnit suite.
+When subclassing, because of single inheritance, you will have to create multiple implementations to test the mutable and immutable use cases (e.g. there would need to be a ButtonMutableObservableValueTest as well to test the mutable cases). The rest of the implementation should be straightforward. The only thing we ask is that you don't depend upon API other than the constructors. Tests are public because JUnit requires them to be, not because we want to commit to them as API. Over time we would like to have the opportunity to rename, add, remove, or optimize the test methods to ensure that we're getting the best coverage as possible. Because of the issues outlined above the preferred method is creating a JUnit suite.
 
 #### JUnit suite()
 

docs/Menu_Contributions.md

@@ -24,7 +24,7 @@ Contents
         *   [3.4.4 Another Expression Alternative: Specify Context at Extension Level](#Another-Expression-Alternative-Specify-Context-at-Extension-Level)
 *   [4 Updating the menu and toolbar appearance](#Updating-the-menu-and-toolbar-appearance)
     *   [4.1 UIElements represent each UI visible instance of a command](#UIElements-represent-each-UI-visible-instance-of-a-command)
-    *   [4.2 State associated with the command is propogated to UI visible elements](#State-associated-with-the-command-is-propogated-to-UI-visible-elements)
+    *   [4.2 State associated with the command is propagated to UI visible elements](#State-associated-with-the-command-is-propagated-to-UI-visible-elements)
 
 
 Placement and visibility
@@ -389,7 +389,7 @@ When the toggle handler runs, it can request that any UI elements have their app
             .getService(ICommandService.class);
     service.refreshElements(IJavaEditorActionDefinitionIds.TOGGLE_MARK_OCCURRENCES, null);
 
-State associated with the command is propogated to UI visible elements
+State associated with the command is propagated to UI visible elements
 ----------------------------------------------------------------------
 
 First define the toggle mark occurrences command. 

tests/org.eclipse.jface.tests.databinding/src/org/eclipse/core/tests/databinding/DatabindingContextTest.java

@@ -70,7 +70,7 @@ public void testDisposeBindings() throws Exception {
 
 		assertFalse(binding.isDisposed());
 		dbc.dispose();
-		assertTrue("binding should be diposed when dbc is disposed", binding
+		assertTrue("binding should be disposed when dbc is disposed", binding
 				.isDisposed());
 	}
 

tests/org.eclipse.jface.tests/src/org/eclipse/jface/tests/viewers/StructuredViewerTest.java

@@ -180,7 +180,7 @@ public void testDeleteSibling() {
 	}
 
 	/**
-	 * Tests to ensure that the viewer is properly diposed.  Includes:
+	 * Tests to ensure that the viewer is properly disposed.  Includes:
 	 *     removal of filters
 	 */
 	@Test

tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/multipageeditor/MultiPageEditorPartTest.java

@@ -40,7 +40,7 @@ public void testDisposalWithoutSuccessfulInitialization() throws Exception {
 				"org.eclipse.ui.tests.multipageeditor.TestMultiPageEditorThrowingPartInitException"); //$NON-NLS-1$
 
 		assertTrue(editor instanceof ErrorEditorPart);
-		assertTrue("The editor should have been diposed by CompatibilityPart",
+		assertTrue("The editor should have been disposed by CompatibilityPart",
 				TestMultiPageEditorThrowingPartInitException.disposeCalled);
 		assertNull("No exception should have been thrown while disposing",
 				TestMultiPageEditorThrowingPartInitException.exceptionWhileDisposing);