Author: humbedooh
Date: Wed Sep 19 08:52:03 2012
New Revision: 1387493
URL: http://svn.apache.org/viewvc?rev=1387493&view=rev
Log:
Some more typo/grammar fixes
Modified:
trafficserver/site/trunk/content/docs/trunk/admin/cluster-howto/index.en.mdtext
trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
trafficserver/site/trunk/content/docs/trunk/admin/security-options/index.en.mdtext
Modified:
trafficserver/site/trunk/content/docs/trunk/admin/cluster-howto/index.en.mdtext
URL:
http://svn.apache.org/viewvc/trafficserver/site/trunk/content/docs/trunk/admin/cluster-howto/index.en.mdtext?rev=1387493&r1=1387492&r2=1387493&view=diff
==============================================================================
---
trafficserver/site/trunk/content/docs/trunk/admin/cluster-howto/index.en.mdtext
(original)
+++
trafficserver/site/trunk/content/docs/trunk/admin/cluster-howto/index.en.mdtext
Wed Sep 19 08:52:03 2012
@@ -112,16 +112,16 @@ individually. You may following these in
::::text
traffic_line -L
- process traffic_server and traffic_manager need to restart after the change
- of 'proxy.local.cluster.type' and 'proxy.config.cluster.ethernet_interface'
+ The `traffic_server` and `traffic_manager` processes will need to restart
after the change
+ of 'proxy.local.cluster.type' and 'proxy.config.cluster.ethernet_interface'
have taken place.
-Traffic Server will join into the Cluster in about 10 seconds and you can run
-`traffic_line -r proxy.process.cluster.nodes` to check the hosts in cluster
-or checkout the
[`cluster.config`](../configuration-files/cluster.configcluster.config)
+Traffic Server will join into the cluster in about 10 seconds, and you can run
+`traffic_line -r proxy.process.cluster.nodes` to check the hosts in the
cluster,
+or check out the
[`cluster.config`](../configuration-files/cluster.configcluster.config)
in the configuration directory.
After a successful join of the cluster, all changes of global configurations
on any
-node, will take effect on **all** nodes now.
+node, will take effect on **all** nodes.
# Deleting Nodes from a Cluster # {#DeletingNodesFromCluster}
Modified:
trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
URL:
http://svn.apache.org/viewvc/trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext?rev=1387493&r1=1387492&r2=1387493&view=diff
==============================================================================
---
trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
(original)
+++
trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
Wed Sep 19 08:52:03 2012
@@ -1065,7 +1065,7 @@ the `records.config` file.
*`proxy.config.log.logfile_perm`* {#proxy.config.log.logfile_perm}
: `STRING`
: Default: `rw-r--r--`
-: The log file permissions. The standard UNIX file permissions are used
(owner, group, other). Permissable values are:
+: The log file permissions. The standard UNIX file permissions are used
(owner, group, other). Permissible values are:
`-`no permission
`r`read permission
Modified:
trafficserver/site/trunk/content/docs/trunk/admin/security-options/index.en.mdtext
URL:
http://svn.apache.org/viewvc/trafficserver/site/trunk/content/docs/trunk/admin/security-options/index.en.mdtext?rev=1387493&r1=1387492&r2=1387493&view=diff
==============================================================================
---
trafficserver/site/trunk/content/docs/trunk/admin/security-options/index.en.mdtext
(original)
+++
trafficserver/site/trunk/content/docs/trunk/admin/security-options/index.en.mdtext
Wed Sep 19 08:52:03 2012
@@ -87,7 +87,7 @@ on the authentication options configured
that will be used. If the client is allowed access, then Traffic Server checks
its cache for the requested content.
-**Step 2:** If the request is a cache hit and the content is fresh,
thenTraffic
+**Step 2:** If the request is a cache hit and the content is fresh, then
Traffic
Server encrypts the content and sends it to the client. The client decrypts
the content (using the method determined during the handshake) and displays
it.
