You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by km...@apache.org on 2018/04/02 16:30:54 UTC

[geode] branch develop updated: COMMIT THEN REVIEW: Fixed doc typos.

This is an automated email from the ASF dual-hosted git repository.

kmiller pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode.git


The following commit(s) were added to refs/heads/develop by this push:
     new fce124f  COMMIT THEN REVIEW: Fixed doc typos.
fce124f is described below

commit fce124f1007331ed1085c11f50420008fa975589
Author: Karen Miller <km...@pivotal.io>
AuthorDate: Mon Apr 2 09:21:20 2018 -0700

    COMMIT THEN REVIEW: Fixed doc typos.
---
 .../continuous_querying/continuous_querying_whats_next.html.md.erb      | 2 +-
 geode-docs/managing/disk_storage/compacting_disk_stores.html.md.erb     | 2 +-
 .../disk_storage/keeping_offline_disk_store_in_sync.html.md.erb         | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/geode-docs/developing/continuous_querying/continuous_querying_whats_next.html.md.erb b/geode-docs/developing/continuous_querying/continuous_querying_whats_next.html.md.erb
index 4d91722..7344035 100644
--- a/geode-docs/developing/continuous_querying/continuous_querying_whats_next.html.md.erb
+++ b/geode-docs/developing/continuous_querying/continuous_querying_whats_next.html.md.erb
@@ -23,7 +23,7 @@ This topic discusses CQ management options, CQ states, and retrieving initial re
 
 ## Using CQs from a RegionService Instance
 
-If you are running durable client queues (CQs) from the `RegionService` instance, stop and start the offline event storage for the client as a whole. The server manages one queue for the entire client process, so you need to request the stop and start of durable CQ event messaging for the cache as a whole, through the `ClientCache` instance. If you closed the `RegionService` instances, event processing would stop, but the server would continue to send events, and those events would be lost.
+If you are running durable client queues from the `RegionService` instance, stop and start the offline event storage for the client as a whole. The server manages one queue for the entire client process, so you need to request the stop and start of durable CQ event messaging for the cache as a whole, through the `ClientCache` instance. If you closed the `RegionService` instances, event processing would stop, but the server would continue to send events, and those events would be lost.
 
 Stop with:
 
diff --git a/geode-docs/managing/disk_storage/compacting_disk_stores.html.md.erb b/geode-docs/managing/disk_storage/compacting_disk_stores.html.md.erb
index 17910b5..ab43276 100644
--- a/geode-docs/managing/disk_storage/compacting_disk_stores.html.md.erb
+++ b/geode-docs/managing/disk_storage/compacting_disk_stores.html.md.erb
@@ -85,7 +85,7 @@ To follow a strategy like this, you need to set aside enough disk space to accom
 
 ## <a id="compacting_disk_stores__section_A9EE86F662EE4D46A327C336E901A0F2" class="no-quick-link"></a>Directory Size Limits
 
-Reaching directory size limits during has different results depending on whether you are running an automatic or manual compaction:
+Reaching directory size limits during compaction has different results depending on whether you are running an automatic or manual compaction:
 
 -   For automatic compaction, the system logs a warning, but does not stop.
 -   For manual compaction, the operation stops and returns a `DiskAccessException` to the calling process, reporting that the system has run out of disk space.
diff --git a/geode-docs/managing/disk_storage/keeping_offline_disk_store_in_sync.html.md.erb b/geode-docs/managing/disk_storage/keeping_offline_disk_store_in_sync.html.md.erb
index cd1bce4..506d833 100644
--- a/geode-docs/managing/disk_storage/keeping_offline_disk_store_in_sync.html.md.erb
+++ b/geode-docs/managing/disk_storage/keeping_offline_disk_store_in_sync.html.md.erb
@@ -71,7 +71,7 @@ Perform the following operations with caution. You are permanently removing data
 
 You can remove the region from the disk store in one of two ways:
 
--   Delete the entire set of disk store files. Your member will initialize with an empty set of files the next time you and start it. Exercise caution when removing the files from the file system, as more than one region can be specified to use the same disk store directories.
+-   Delete the entire set of disk store files. Your member will initialize with an empty set of files the next time you start it. Exercise caution when removing the files from the file system, as more than one region can be specified to use the same disk store directories.
 -   Selectively remove the discontinued region from the disk store with a command such as:
 
     ``` pre

-- 
To stop receiving notification emails like this one, please contact
kmiller@apache.org.