Tweak discussion regarding reaping to advise against adjusting these

values.

website/source/docs/agent/basics.html.markdown

@@ -135,7 +135,9 @@ marks that node as having _left_. Unlike the _failed_ case, all of the
 services provided by a node are immediately deregistered. If the agent was
 a server, replication to it will stop.
 
-To prevent an accumulation of dead nodes (nodes in either _failed_ or _left_ states),
-Consul will automatically remove dead nodes out of the catalog. This process is
-called _reaping_. This is currently done on a configurable interval of 72 hours.
-Reaping is similar to leaving, causing all associated services to be deregistered.
+To prevent an accumulation of dead nodes (nodes in either _failed_ or _left_
+states), Consul will automatically remove dead nodes out of the catalog. This
+process is called _reaping_. This is currently done on a configurable
+interval of 72 hours (changing the reap interval is *not* recommended due to
+its consequences during outage situations).  Reaping is similar to leaving,
+causing all associated services to be deregistered.

website/source/docs/faq.html.markdown

@@ -59,10 +59,14 @@ the current state of the catalog can lag behind until the state is reconciled.
 
 ## Q: Are _failed_ or _left_ nodes ever removed?
 
-To prevent an accumulation of dead nodes (nodes in either _failed_ or _left_ states),
-Consul will automatically remove dead nodes out of the catalog. This process is
-called _reaping_. This is currently done on a configurable interval of 72 hours.
-Reaping is similar to leaving, causing all associated services to be deregistered.
+To prevent an accumulation of dead nodes (nodes in either _failed_ or _left_
+states), Consul will automatically remove dead nodes out of the catalog. This
+process is called _reaping_. This is currently done on a configurable
+interval of 72 hours.  Reaping is similar to leaving, causing all associated
+services to be deregistered.  Changing the reap interval for aesthetic
+reasons to trim the number of _failed_ or _left_ nodes is not advised (nodes
+in the _failed_ or _left_ state do not cause any additional burden on
+Consul).
 
 ## Q: Does Consul support delta updates for watchers or blocking queries?