Fixes typo in Javadoc.

--
MOS_MIGRATED_REVID=128192249

1 files changed, 5 insertions, 5 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/rules/RuleConfiguredTargetFactory.java b/src/main/java/com/google/devtools/build/lib/rules/RuleConfiguredTargetFactory.java
index 6f5eb7cd90..8167632a01 100644
--- a/src/main/java/com/google/devtools/build/lib/rules/RuleConfiguredTargetFactory.java
+++ b/src/main/java/com/google/devtools/build/lib/rules/RuleConfiguredTargetFactory.java
@@ -24,8 +24,8 @@ import com.google.devtools.build.lib.packages.RuleClass;
  * <p>Here follows an overview of how loading and analysis works in Bazel:
  *
  * <p>Actions (i.e. commands that are run during the build) are created by configured targets
- * (see {@link ConfiguredTarget}), wich are a pair of a target (e.g. <code>//src:bazel</code>) and a
- * {@link com.google.devtools.build.lib.analysis.config.BuildConfiguration}, which is a blob of
+ * (see {@link ConfiguredTarget}), which are a pair of a target (e.g. <code>//src:bazel</code>) and
+ * a {@link com.google.devtools.build.lib.analysis.config.BuildConfiguration}, which is a blob of
  * data that contains extra information about how the target should be built (for example, for which
  * platform or with which C++ preprocessor definitions). Accordingly, a target can give rise to
  * multiple configured targets, for example, if it needs to be built both for the host and the
@@ -54,7 +54,7 @@ import com.google.devtools.build.lib.packages.RuleClass;
  *       file produced by during the build. Not every file produced during the build has a
  *       corresponding output file target.</li>
  *   <li>Rules. These describe things a build actually does. Each rule has a class (e.g.
- *       <code>cc_binary</code>. Rule classes can be defined either in Skylark using the
+ *       <code>cc_binary</code>). Rule classes can be defined either in Skylark using the
  *       <code>rule()</code> function or in Java code by implementing
  *       {@link com.google.devtools.build.lib.analysis.RuleDefinition}.</li>
  * </p>
@@ -76,13 +76,13 @@ import com.google.devtools.build.lib.packages.RuleClass;
  * <p>Analysis of non-rule configured targets is special-cased and is not covered here.
  *
  * <p>The analysis of a rule itself is done by implementations {@link RuleConfiguredTargetFactory}
- * (there should be one for each rule class). the data above is available using the
+ * (there should be one for each rule class). The data above is available using the
  * {@link RuleContext} argument passed into its create() method. It should
  * result in three things:
  * <ul>
  *   <li>A set of actions. These should be passed to
  *   {@link RuleContext#registerAction(ActionAnalysisMetadata...)}, although for more
- *       common cases (e.g. {@link com.google.devtools.build.lib.analysis.actions.SpawnAction)},
+ *       common cases (e.g. {@link com.google.devtools.build.lib.analysis.actions.SpawnAction}),
  *       shortcuts are provided.</li>
  *   <li>A set of artifacts (files produced by actions). These should be created using methods of
  *       {@link RuleContext}. Each artifact thus created must have a generating action.</li>