Small fixes to Documentation/rest-api-changes.txt

Add the missing "base_revision" field in the example EditInfo.

Change "baseRevision" from camel case to underscore in the EditInfo
description.

Change "destination" to "destination_branch" in the MoveInput
description.

Change-Id: I7d0d7637828835115026f8f467b6932b1908ea39

Documentation/rest-api-changes.txt

@@ -1809,6 +1809,7 @@ provided fetch info map is also included.
        "subject":"Use an EventBus to manage star icons",
        "message":"Use an EventBus to manage star icons\n\nImage widgets that need to ..."
     },
+    "base_revision":"c35558e0925e6985c91f3a16921537d5e572b7a3"
   }
 ----
 
@@ -4474,15 +4475,15 @@ The `EditInfo` entity contains information about a change edit.
 
 [options="header",cols="1,^1,5"]
 |===========================
-|Field Name    ||Description
-|`commit`      ||The commit of change edit as
+|Field Name     ||Description
+|`commit`       ||The commit of change edit as
 link:#commit-info[CommitInfo] entity.
-|`baseRevision`||The revision of the patch set change edit is based on.
-|`fetch`       ||
+|`base_revision`||The revision of the patch set the change edit is based on.
+|`fetch`        ||
 Information about how to fetch this patch set. The fetch information is
 provided as a map that maps the protocol name ("`git`", "`http`",
 "`ssh`") to link:#fetch-info[FetchInfo] entities.
-|`files`       |optional|
+|`files`        |optional|
 The files of the change edit as a map that maps the file names to
 link:#file-info[FileInfo] entities.
 |===========================
@@ -4671,9 +4672,9 @@ The `MoveInput` entity contains information for moving a change to a new branch.
 
 [options="header",cols="1,^1,5"]
 |===========================
-|Field Name   ||Description
-|`destination`||Destination branch
-|`message`    |optional|
+|Field Name          ||Description
+|`destination_branch`||Destination branch
+|`message`           |optional|
 A message to be posted in this change's comments
 |===========================