Refer to Datastore everywhere correctly by its capitalized form

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

java/google/registry/env/alpha/default/WEB-INF/cron.xml

@@ -16,9 +16,9 @@
 
       We want it to be close to midnight because that reduces the chance that the
       point-in-time code won't have to go to the extra trouble of fetching old
-      versions of objects from the datastore. However, we don't want it to run too
+      versions of objects from Datastore. However, we don't want it to run too
       close to midnight, because there's always a chance that a change which was
-      timestamped before midnight hasn't fully been committed to the datastore. So
+      timestamped before midnight hasn't fully been committed to Datastore. So
       we add a 4+ minute grace period to ensure the transactions cool down, since
       our queries are not transactional.
     -->
@@ -87,7 +87,7 @@
   <cron>
     <url><![CDATA[/_dr/cron/commitLogFanout?queue=delete-commits&endpoint=/_dr/task/deleteOldCommitLogs&jitterSeconds=600]]></url>
     <description>
-      This job deletes commit logs from datastore that are old, e.g. thirty days.
+      This job deletes commit logs from Datastore that are old, e.g. thirty days.
     </description>
     <schedule>every 20 minutes synchronized</schedule>
     <target>backend</target>
@@ -158,7 +158,7 @@
   <cron>
     <url><![CDATA[/_dr/cron/fanout?queue=export-snapshot&endpoint=/_dr/task/exportSnapshot&runInEmpty]]></url>
     <description>
-      This job fires off a datastore backup-as-a-service job that generates snapshot files in GCS.
+      This job fires off a Datastore backup-as-a-service job that generates snapshot files in GCS.
       It also enqueues a new task to wait on the completion of that job and then load the resulting
       snapshot into bigquery.
     </description>

java/google/registry/env/common/backend/WEB-INF/web.xml

@@ -113,19 +113,19 @@
     <url-pattern>/_dr/task/verifyEntityIntegrity</url-pattern>
   </servlet-mapping>
 
-  <!-- Exports a datastore backup snapshot to GCS. -->
+  <!-- Exports a Datastore backup snapshot to GCS. -->
   <servlet-mapping>
     <servlet-name>backend-servlet</servlet-name>
     <url-pattern>/_dr/task/exportSnapshot</url-pattern>
   </servlet-mapping>
 
-  <!-- Checks the completion of a datastore backup snapshot. -->
+  <!-- Checks the completion of a Datastore backup snapshot. -->
   <servlet-mapping>
     <servlet-name>backend-servlet</servlet-name>
     <url-pattern>/_dr/task/checkSnapshot</url-pattern>
   </servlet-mapping>
 
-  <!-- Loads a datastore backup snapshot into BigQuery. -->
+  <!-- Loads a Datastore backup snapshot into BigQuery. -->
   <servlet-mapping>
     <servlet-name>backend-servlet</servlet-name>
     <url-pattern>/_dr/task/loadSnapshot</url-pattern>
@@ -157,7 +157,7 @@
     <url-pattern>/_dr/cron/commitLogFanout</url-pattern>
   </servlet-mapping>
 
-  <!-- Deletes old commit logs from datastore. -->
+  <!-- Deletes old commit logs from Datastore. -->
   <servlet-mapping>
     <servlet-name>backend-servlet</servlet-name>
     <url-pattern>/_dr/task/deleteOldCommitLogs</url-pattern>

java/google/registry/env/common/default/WEB-INF/queue.xml

@@ -37,7 +37,7 @@
     <bucket-size>100</bucket-size>
     <retry-parameters>
       <!-- Retry aggressively since a single delayed export increases our time window of
-           unrecoverable data loss in the event of a datastore failure. -->
+           unrecoverable data loss in the event of a Datastore failure. -->
       <min-backoff-seconds>1</min-backoff-seconds>
       <max-backoff-seconds>60</max-backoff-seconds>
       <!-- No age limit; a failed export should be retried as long as possible to avoid

java/google/registry/env/common/tools/WEB-INF/web.xml

@@ -48,7 +48,7 @@
     <url-pattern>/_dr/loadtest</url-pattern>
   </servlet-mapping>
 
-  <!-- Command line tool uses this endpoint to modify the datastore. -->
+  <!-- The nomulus command line tool uses this endpoint to write to Datastore. -->
   <servlet>
     <display-name>Remote API Servlet</display-name>
     <servlet-name>RemoteApiServlet</servlet-name>

java/google/registry/env/crash/default/WEB-INF/cron.xml

@@ -16,9 +16,9 @@
 
       We want it to be close to midnight because that reduces the chance that the
       point-in-time code won't have to go to the extra trouble of fetching old
-      versions of objects from the datastore. However, we don't want it to run too
+      versions of objects from Datastore. However, we don't want it to run too
       close to midnight, because there's always a chance that a change which was
-      timestamped before midnight hasn't fully been committed to the datastore. So
+      timestamped before midnight hasn't fully been committed to Datastore. So
       we add a 4+ minute grace period to ensure the transactions cool down, since
       our queries are not transactional.
     -->
@@ -127,7 +127,7 @@
   <cron>
     <url><![CDATA[/_dr/cron/fanout?queue=export-snapshot&endpoint=/_dr/task/exportSnapshot&runInEmpty]]></url>
     <description>
-      This job fires off a datastore backup-as-a-service job that generates snapshot files in GCS.
+      This job fires off a Datastore backup-as-a-service job that generates snapshot files in GCS.
       It also enqueues a new task to wait on the completion of that job and then load the resulting
       snapshot into bigquery.
     </description>

java/google/registry/env/production/default/WEB-INF/cron.xml

@@ -28,9 +28,9 @@
 
       We want it to be close to midnight because that reduces the chance that the
       point-in-time code won't have to go to the extra trouble of fetching old
-      versions of objects from the datastore. However, we don't want it to run too
+      versions of objects from Datastore. However, we don't want it to run too
       close to midnight, because there's always a chance that a change which was
-      timestamped before midnight hasn't fully been committed to the datastore. So
+      timestamped before midnight hasn't fully been committed to Datastore. So
       we add a 4+ minute grace period to ensure the transactions cool down, since
       our queries are not transactional.
     -->
@@ -108,7 +108,7 @@
   <cron>
     <url><![CDATA[/_dr/cron/commitLogFanout?queue=delete-commits&endpoint=/_dr/task/deleteOldCommitLogs&jitterSeconds=600]]></url>
     <description>
-      This job deletes commit logs from datastore that are old, e.g. thirty days.
+      This job deletes commit logs from Datastore that are old, e.g. thirty days.
     </description>
     <schedule>every 20 minutes synchronized</schedule>
     <target>backend</target>
@@ -169,7 +169,7 @@
   <cron>
     <url><![CDATA[/_dr/cron/fanout?queue=export-snapshot&endpoint=/_dr/task/exportSnapshot&runInEmpty]]></url>
     <description>
-      This job fires off a datastore backup-as-a-service job that generates snapshot files in GCS.
+      This job fires off a Datastore backup-as-a-service job that generates snapshot files in GCS.
       It also enqueues a new task to wait on the completion of that job and then load the resulting
       snapshot into bigquery.
     </description>

java/google/registry/env/sandbox/default/WEB-INF/cron.xml

@@ -76,7 +76,7 @@
   <cron>
     <url><![CDATA[/_dr/cron/fanout?queue=export-snapshot&endpoint=/_dr/task/exportSnapshot&runInEmpty]]></url>
     <description>
-      This job fires off a datastore backup-as-a-service job that generates snapshot files in GCS.
+      This job fires off a Datastore backup-as-a-service job that generates snapshot files in GCS.
       It also enqueues a new task to wait on the completion of that job and then load the resulting
       snapshot into bigquery.
     </description>
@@ -146,7 +146,7 @@
   <cron>
     <url><![CDATA[/_dr/cron/commitLogFanout?queue=delete-commits&endpoint=/_dr/task/deleteOldCommitLogs&jitterSeconds=600]]></url>
     <description>
-      This job deletes commit logs from datastore that are old, e.g. thirty days.
+      This job deletes commit logs from Datastore that are old, e.g. thirty days.
     </description>
     <schedule>every 20 minutes synchronized</schedule>
     <target>backend</target>