From 2c6ce77c5a06ab4acb99cfb90304fa61428c6465 Mon Sep 17 00:00:00 2001
From: Jonathan Turner Eagles <jeagles@apache.org>
Date: Thu, 13 Mar 2014 16:49:27 +0000
Subject: [PATCH] MAPREDUCE-5713. InputFormat and JobConf JavaDoc Fixes (Chen
 He via jeagles)

git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/trunk@1577239 13f79535-47bb-0310-9956-ffa450edef68
---
 hadoop-mapreduce-project/CHANGES.txt                       | 2 ++
 .../main/java/org/apache/hadoop/mapred/InputFormat.java    | 2 +-
 .../src/main/java/org/apache/hadoop/mapred/JobConf.java    | 7 ++++---
 3 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/hadoop-mapreduce-project/CHANGES.txt b/hadoop-mapreduce-project/CHANGES.txt
index 07023e67286..0ffbba7adb4 100644
--- a/hadoop-mapreduce-project/CHANGES.txt
+++ b/hadoop-mapreduce-project/CHANGES.txt
@@ -158,6 +158,8 @@ Release 2.5.0 - UNRELEASED
 
     MAPREDUCE-5765. Update hadoop-pipes examples README (Mit Desai via jeagles)
 
+    MAPREDUCE-5713. InputFormat and JobConf JavaDoc Fixes (Chen He via jeagles)
+
   OPTIMIZATIONS
 
   BUG FIXES 
diff --git a/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/InputFormat.java b/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/InputFormat.java
index 8179c9a5120..afebdcf60b5 100644
--- a/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/InputFormat.java
+++ b/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/InputFormat.java
@@ -54,7 +54,7 @@ import org.apache.hadoop.fs.FileSystem;
  * mapreduce.input.fileinputformat.split.minsize</a>.</p>
  * 
  * <p>Clearly, logical splits based on input-size is insufficient for many 
- * applications since record boundaries are to respected. In such cases, the
+ * applications since record boundaries are to be respected. In such cases, the
  * application has to also implement a {@link RecordReader} on whom lies the
  * responsibilty to respect record-boundaries and present a record-oriented
  * view of the logical <code>InputSplit</code> to the individual task.
diff --git a/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/JobConf.java b/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/JobConf.java
index fd9e95d4916..96bca89ed5f 100644
--- a/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/JobConf.java
+++ b/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/JobConf.java
@@ -66,9 +66,10 @@ import org.apache.log4j.Level;
  *   </li>
  *   <li>
  *   While some job parameters are straight-forward to set 
- *   (e.g. {@link #setNumReduceTasks(int)}), some parameters interact subtly 
- *   rest of the framework and/or job-configuration and is relatively more 
- *   complex for the user to control finely (e.g. {@link #setNumMapTasks(int)}).
+ *   (e.g. {@link #setNumReduceTasks(int)}), some parameters interact subtly
+ *   with the rest of the framework and/or job-configuration and is relatively
+ *   more complex for the user to control finely
+ *   (e.g. {@link #setNumMapTasks(int)}).
  *   </li>
  * </ol></p>
  *