Fixed javadoc errors.

Author: deepika-u

bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/AbstractHandler.java

@@ -59,7 +59,7 @@ public void dispose() {
 	 * type of listener can be attached to a subclass). This is used primarily
 	 * for support of <code>AbstractHandler</code> in
 	 * <code>org.eclipse.ui.workbench</code>, and clients should be wary of
-	 * overriding this behaviour. If this method is overridden, then the first
+	 * overriding this behavior. If this method is overridden, then the first
 	 * line of the method should be "<code>super.fireHandlerChanged(handlerEvent);</code>".
 	 * </p>
 	 *
@@ -147,7 +147,7 @@ public boolean isHandled() {
 	 * type of listener can be attached to a subclass). This is used primarily
 	 * for support of <code>AbstractHandler</code> in
 	 * <code>org.eclipse.ui.workbench</code>, and clients should be wary of
-	 * overriding this behaviour. If this method is overridden, then the return
+	 * overriding this behavior. If this method is overridden, then the return
 	 * value should include "<code>super.hasListeners() ||</code>".
 	 * </p>
 	 *

bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/AbstractParameterValueConverter.java

@@ -30,7 +30,7 @@
  * <p>
  * This class will typically be extended so the subclass can be referenced from
  * the <code>converter</code> attribute of the
- * <code>commandParameterType</code> elemement of the
+ * <code>commandParameterType</code> element of the
  * <code>org.eclipse.ui.commands</code> extension-point. Objects implementing
  * this interface may also be passed directly to
  * {@link ParameterType#define(String, AbstractParameterValueConverter)} by

bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/Command.java

@@ -26,8 +26,8 @@
 /**
  * <p>
  * A command is an abstract representation for some semantic behaviour. It is
- * not the actual implementation of this behaviour, nor is it the visual
- * appearance of this behaviour in the user interface. Instead, it is a bridge
+ * not the actual implementation of this behavior, nor is it the visual
+ * appearance of this behavior in the user interface. Instead, it is a bridge
  * between the two.
  * </p>
  * <p>

bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/CommandEvent.java

@@ -172,26 +172,26 @@ public CommandEvent(final Command command, final boolean categoryChanged,
 	 * @param command
 	 *            the instance of the interface that changed.
 	 * @param categoryChanged
-	 *            <code>true</code>, iff the category property changed.
+	 *            <code>true</code>, if the category property changed.
 	 * @param definedChanged
-	 *            <code>true</code>, iff the defined property changed.
+	 *            <code>true</code>, if the defined property changed.
 	 * @param descriptionChanged
-	 *            <code>true</code>, iff the description property changed.
+	 *            <code>true</code>, if the description property changed.
 	 * @param handledChanged
-	 *            <code>true</code>, iff the handled property changed.
+	 *            <code>true</code>, if the handled property changed.
 	 * @param nameChanged
-	 *            <code>true</code>, iff the name property changed.
+	 *            <code>true</code>, if the name property changed.
 	 * @param parametersChanged
 	 *            <code>true</code> if the parameters have changed;
 	 *            <code>false</code> otherwise.
 	 * @param returnTypeChanged
-	 *            <code>true</code> iff the return type property changed;
+	 *            <code>true</code> if the return type property changed;
 	 *            <code>false</code> otherwise.
 	 * @param helpContextIdChanged
-	 *            <code>true</code> iff the help context identifier changed;
+	 *            <code>true</code> if the help context identifier changed;
 	 *            <code>false</code> otherwise.
 	 * @param enabledChanged
-	 *            <code>true</code> iff the comand enablement changed;
+	 *            <code>true</code> if the command enablement changed;
 	 *            <code>false</code> otherwise.
 	 * @since 3.3
 	 */
@@ -287,7 +287,7 @@ public final boolean isReturnTypeChanged() {
 	/**
 	 * Return whether the enable property changed.
 	 *
-	 * @return <code>true</code> iff the comand enablement changed
+	 * @return <code>true</code> if the command enablement changed
 	 * @since 3.3
 	 */
 	public final boolean isEnabledChanged() {

bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/ParameterizedCommand.java

@@ -33,7 +33,7 @@
  * <p>
  * A command that has had one or more of its parameters specified. This class
  * serves as a utility class for developers that need to manipulate commands
- * with parameters. It handles the behaviour of generating a parameter map and a
+ * with parameters. It handles the behavior of generating a parameter map and a
  * human-readable name.
  * </p>
  *
@@ -434,7 +434,7 @@ public boolean equals(final Object object) {
 	/**
 	 * Executes this command with its parameters. This method will succeed
 	 * regardless of whether the command is enabled or defined. It is
-	 * preferrable to use {@link #executeWithChecks(Object, Object)}.
+	 * preferable to use {@link #executeWithChecks(Object, Object)}.
 	 *
 	 * @param trigger
 	 *            The object that triggered the execution; may be

bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/common/NamedHandleObject.java

@@ -29,7 +29,7 @@ public abstract class NamedHandleObject extends HandleObject {
 	protected String description = null;
 
 	/**
-	 * The name of this handle. This valud should not be <code>null</code>
+	 * The name of this handle. This value should not be <code>null</code>
 	 * unless the handle is undefined.
 	 */
 	protected String name = null;

bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/common/NamedHandleObjectComparator.java

@@ -32,7 +32,7 @@ public class NamedHandleObjectComparator implements Comparator {
 	 * useful is they are display to an end user.
 	 *
 	 * @param left
-	 *            The first obect to compare; may be <code>null</code>.
+	 *            The first object to compare; may be <code>null</code>.
 	 * @param right
 	 *            The second object to compare; may be <code>null</code>.
 	 * @return <code>-1</code> if <code>left</code> is <code>null</code>

bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/operations/IAdvancedUndoableOperation.java

@@ -89,7 +89,7 @@ public interface IAdvancedUndoableOperation {
 	 * @return the IStatus indicating the validity of the undo. The status
 	 *         severity should be set to <code>OK</code> if the undo can
 	 *         successfully be performed, and <code>ERROR</code> if it
-	 *         cannnot. Any other status is assumed to represent an ambiguous
+	 *         cannot. Any other status is assumed to represent an ambiguous
 	 *         state.
 	 * @throws ExecutionException
 	 *             if an exception occurs while computing the validity.
@@ -119,7 +119,7 @@ IStatus computeUndoableStatus(IProgressMonitor monitor)
 	 * @return the IStatus indicating the validity of the redo. The status
 	 *         severity should be set to <code>OK</code> if the redo can
 	 *         successfully be performed, and <code>ERROR</code> if it
-	 *         cannnot. Any other status is assumed to represent an ambiguous
+	 *         cannot. Any other status is assumed to represent an ambiguous
 	 *         state.
 	 * @throws ExecutionException
 	 *             if an exception occurs while computing the validity.

bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/package.html

@@ -13,7 +13,7 @@ <h2>Package Specification</h2>
 This package provides API and implementation classes to define abstract
 pieces of functionality.  These pieces of functionality are intended to
 provide a common way for plug-ins and the user interface to communicate
-potential behaviour.
+potential behavior.
 </p>
 <p>
 This package is designed so that its elements can be public and dynamic.  That
@@ -22,11 +22,11 @@ <h2>Package Specification</h2>
 </p>
 <h3>Command</h3>
 <p>
-A command is an abstract representation for some semantic behaviour.  For
+A command is an abstract representation for some semantic behavior.  For
 example, there might be a "copy" command.  How this command actually
 behaves might be dependent on what state your application is in.  It is not
-the actual implementation of that behaviour, and it is not the visual
-representation of that behaviour.
+the actual implementation of that behavior, and it is not the visual
+representation of that behavior.
 </p>
 <p>
 Commands are managed by an instance of <code>CommandManager</code>.  In fact, a
@@ -45,7 +45,7 @@ <h3>Command</h3>
 built around dynamic components (e.g., plug-ins).
 <p>
 Commands can be grouped into categories.  These categories are arbitrary
-groupings, and have no defined behaviour.  These categories might be used in a
+groupings, and have no defined behavior.  These categories might be used in a
 user interface for breaking up a large list of commands into semantically
 similar commands -- making the list easier to navigate.
 </p>
@@ -115,20 +115,20 @@ <h4>Examples</h4>
 
 <h3>Handler</h3>
 <p>
-A handler is the behaviour of a command at a particular point in time.  This is
+A handler is the behavior of a command at a particular point in time.  This is
 the piece that will actually interact with your application model.  For every
 command, there can be zero or more possible handlers.  However, at any one
 time, there is either one handler (i.e., handled) or no handler (i.e.,
 unhandled).
 </p>
 <p>
 Handlers must implement <code>IHandler</code>.  However, there is a convenient
-abstract class, <code>AbstractHandler</code> which provides default behaviour
+abstract class, <code>AbstractHandler</code> which provides default behavior
 for some of the methods in the interface.  It is recommended that developers
 subclass <code>AbstractHandler</code>.
 </p>
 <p>
-Beside functional behaviour, a handler carries with it a map of attribute
+Beside functional behavior, a handler carries with it a map of attribute
 values.  This is a completely optionaly way of carrying extra data.  In the
 case of the <code>AbstractHandler</code>, this map is empty.  Some attributes
 have well defined meanings.  These attributes are defined in