Extensions: Small updates to the docserver readme.

- Remove references to update-docs.sh. It was the same as
update-docs-full.sh.

- A new script update-docs-cloud.sh was added to the VM instance for
just updating the GCS buckets. Modify the documentation to refer to it.

BUG=None

Change-Id: I4ed85772b332801ece36f9303a44d067b97ad8be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2301200
Auto-Submit: Karan Bhatia <karandeepb@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#789082}

chrome/common/extensions/docs/server2/README

@@ -135,19 +135,16 @@ instance. From within the SSH session, first switch to user "git-processor":
 
   sudo su - git-processor
 
-You can run './update-docs.sh' from the home directory there. This will
+You can run './update-docs-full.sh' from the home directory there. This will
 automatically fetch any new objects from the upstream repository and then
 perform a full update if there are pending changes.
 
 It's almost never necessary to use this tool. For one interesting example,
 consider the case where no new commits are landing in the chrome repository
 but a change was just pushed to one of the GCS providers (like say, the
-chromedocs-multidevice bucker). In this case, you may want to force an update
-of only the content_providers data.
-
-  ./update_docs.sh --data-source=content_providers --force
-
-This will safely do the push for you, ensuring that the automated job
+chromedocs-multidevice bucket). In this case, you may want to force an update
+of only the content_providers data. To do this run the update-docs-cloud.sh
+script. This will safely do the push for you, ensuring that the automated job
 does not collide with your own.
 
 ----------------------
@@ -183,8 +180,9 @@ update files in these docs, follow these steps:
 4) After the next cron job on the compute engine completes, the modifications
    should be live.
 5) In order to expedite 4), a manual datastore update can be performed by
-   running "./update_docs.sh --data-source=content_providers --force" on the VM
-   instance.
+   running "./update-docs-cloud.sh on the VM instance. This only updates the
+   "content_providers" data source without fetching updates for the chromium
+   repository.
 
 Note: these steps shouldn't require a server version bump. If they do, please
 file a bug.