[geode] branch develop updated: User Guide: fixed language and command examples in the cluster config deployment section

[db...@apache.org]

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

dbarnes 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 cd6fa12  User Guide: fixed language and command examples in the cluster config deployment section
cd6fa12 is described below

commit cd6fa1208982f1ec1bf82e870e8ca78f2dd6200e
Author: Dave Barnes <db...@pivotal.io>
AuthorDate: Wed Nov 1 15:47:46 2017 -0700

    User Guide: fixed language and command examples in the cluster config deployment section
---
 .../configuring/running/change_file_spec.html.md.erb    | 17 ++++++++---------
 1 file changed, 8 insertions(+), 9 deletions(-)

diff --git a/geode-docs/configuring/running/change_file_spec.html.md.erb b/geode-docs/configuring/running/change_file_spec.html.md.erb
index 9a0e3d4..1232857 100644
--- a/geode-docs/configuring/running/change_file_spec.html.md.erb
+++ b/geode-docs/configuring/running/change_file_spec.html.md.erb
@@ -22,22 +22,22 @@ limitations under the License.
 You can change all file specifications in the `gemfire.properties` file and at the command line.
 
 **Note:**
-<%=vars.product_name%> applications can use the API to pass `java.lang.System properties` to the distributed system connection. This changes file specifications made at the command line and in the `gemfire.properties`. You can verify an application’s property settings in the configuration information logged at application startup. The configuration is listed when the `gemfire.properties` `log-level` is set to `config` or lower.
+<%=vars.product_name%> applications can use the API to pass `java.lang.System` properties to the distributed system connection. This changes file specifications made at the command line and in the `gemfire.properties` file. You can verify an application’s property settings in the configuration information logged at application startup. The configuration is listed when the `gemfire.properties` `log-level` is set to `config` or lower.
 
-This invocation of the application, `testApplication.TestApp1`, provides non-default specifications for both the `cache.xml` and `gemfire.properties`:
+This invocation of the application, `testApplication.TestApp1`, provides non-default specifications for both the `cache.xml` and `gemfire.properties` files:
 
 ``` pre
-java -Dgemfire.cache-xml-file=
-/gemfireSamples/examples/dist/cacheRunner/queryPortfolios.xml
--DgemfirePropertyFile=defaultConfigs/gemfire.properties
+java -Dgemfire.cache-xml-file=\
+/gemfireSamples/examples/dist/cacheRunner/queryPortfolios.xml \
+-DgemfirePropertyFile=defaultConfigs/gemfire.properties \
 testApplication.TestApp1
 ```
 
 The gfsh start server command can use the same specifications:
 
 ``` pre
-gfsh>start server
--J-Dgemfire.cache-xml-file=/gemfireSamples/examples/dist/cacheRunner/queryPortfolios.xml
+gfsh>start server \
+-J-Dgemfire.cache-xml-file=/gemfireSamples/examples/dist/cacheRunner/queryPortfolios.xml \
 -J-DgemfirePropertyFile=defaultConfigs/gemfire.properties
 ```
 
@@ -52,6 +52,5 @@ Example `gemfire.properties` file with non-default `cache.xml` specification:
 #Tue May 09 17:53:54 PDT 2006
 mcast-address=192.0.2.0
 mcast-port=10333
-locators=
-cache-xml-file=/gemfireSamples/examples/dist/cacheRunner/queryPortfolios.xml
+locators=cache-xml-file=/gemfireSamples/examples/dist/cacheRunner/queryPortfolios.xml
 ```

-- 
To stop receiving notification emails like this one, please contact
['"commits@geode.apache.org" <co...@geode.apache.org>'].