Refer to Datastore everywhere correctly by its capitalized form

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=147479683

java/google/registry/backup/BackupUtils.java

@@ -41,7 +41,7 @@ public class BackupUtils {
   }
 
   /**
-   * Converts the given {@link ImmutableObject} to a raw datastore entity and write it to an
+   * Converts the given {@link ImmutableObject} to a raw Datastore entity and write it to an
    * {@link OutputStream} in delimited protocol buffer format.
    */
   static void serializeEntity(ImmutableObject entity, OutputStream stream) throws IOException {
@@ -51,7 +51,7 @@ public class BackupUtils {
   /**
    * Return an iterator of {@link ImmutableObject} instances deserialized from the given stream.
    *
-   * <p>This parses out delimited protocol buffers for raw datastore entities and then Ofy-loads
+   * <p>This parses out delimited protocol buffers for raw Datastore entities and then Ofy-loads
    * those as {@link ImmutableObject}.
    *
    * <p>The iterator reads from the stream on demand, and as such will fail if the stream is closed.

java/google/registry/backup/CommitLogCheckpointAction.java

@@ -33,7 +33,7 @@ import javax.inject.Inject;
 import org.joda.time.DateTime;
 
 /**
- * Action that saves commit log checkpoints to datastore and kicks off a diff export task.
+ * Action that saves commit log checkpoints to Datastore and kicks off a diff export task.
  *
  * <p>We separate computing and saving the checkpoint from exporting it because the export to GCS
  * is retryable but should not require the computation of a new checkpoint. Saving the checkpoint

java/google/registry/backup/CommitLogCheckpointStrategy.java

@@ -40,7 +40,7 @@ import org.joda.time.DateTime;
  *
  * <p>This algorithm examines the recently written commit log data and uses a dual-read approach
  * to determine a point-in-time consistent set of checkpoint times for the commit log buckets.  By
- * "consistent" we mean, generally speaking, that if the datastore were restored by replaying all
+ * "consistent" we mean, generally speaking, that if the Datastore were restored by replaying all
  * the commit logs up to the checkpoint times of the buckets, the result would be transactionally
  * correct; there must be no "holes" where restored state depends on non-restored state.
  *
@@ -116,7 +116,7 @@ class CommitLogCheckpointStrategy {
    */
   @VisibleForTesting
   ImmutableMap<Integer, DateTime> readBucketTimestamps() {
-    // Use a fresh session cache so that we get the latest data from datastore.
+    // Use a fresh session cache so that we get the latest data from Datastore.
     return ofy.doWithFreshSessionCache(new Work<ImmutableMap<Integer, DateTime>>() {
       @Override
       public ImmutableMap<Integer, DateTime> run() {

java/google/registry/backup/DeleteOldCommitLogsAction.java

@@ -42,7 +42,7 @@ import org.joda.time.Duration;
 /**
  * Task that garbage collects old {@link CommitLogManifest} entities.
  *
- * <p>Once commit logs have been written to GCS, we don't really need them in datastore anymore,
+ * <p>Once commit logs have been written to GCS, we don't really need them in Datastore anymore,
  * except to reconstruct point-in-time snapshots of the database. But that functionality is not
  * useful after a certain amount of time, e.g. thirty days. So this task runs periodically to delete
  * the old data.
@@ -72,7 +72,7 @@ import org.joda.time.Duration;
  * commitLogMaxDeletes} for further documentation on this matter.
  *
  * <p>Finally, we need to pick an appropriate cron interval time for this task. Since a bucket
- * represents a single datastore entity group, it's only guaranteed to have one transaction per
+ * represents a single Datastore entity group, it's only guaranteed to have one transaction per
  * second. So we just need to divide {@code maxDeletes} by sixty to get an appropriate minute
  * interval. Assuming {@code maxDeletes} is five hundred, this rounds up to ten minutes, which we'll
  * double, since this task can always catch up in off-peak hours.

java/google/registry/backup/RestoreCommitLogsAction.java

@@ -55,7 +55,7 @@ import java.util.concurrent.Callable;
 import javax.inject.Inject;
 import org.joda.time.DateTime;
 
-/** Restore Registry 2 commit logs from GCS to datastore. */
+/** Restore Registry 2 commit logs from GCS to Datastore. */
 @Action(
     path = RestoreCommitLogsAction.PATH,
     method = Action.Method.POST,
@@ -124,12 +124,12 @@ public class RestoreCommitLogsAction implements Runnable {
   }
 
   /**
-   * Restore the contents of one transaction to datastore.
+   * Restore the contents of one transaction to Datastore.
    *
    * <p>The objects to delete are listed in the {@link CommitLogManifest}, which will be the first
    * object in the iterable. The objects to save follow, each as a {@link CommitLogMutation}. We
    * restore by deleting the deletes and recreating the saves from their proto form. We also save
-   * the commit logs themselves back to datastore, so that the commit log system itself is
+   * the commit logs themselves back to Datastore, so that the commit log system itself is
    * transparently restored alongside the data.
    *
    * @return the manifest, for use in restoring the {@link CommitLogBucket}.