rearrange sentenceslcg/action_collection

Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>

1 files changed, 4 insertions, 4 deletions

diff --git a/docs/dev/data_collector.md b/docs/dev/data_collector.md
index 0ac229a5fc..030dd7dfaf 100644
--- a/docs/dev/data_collector.md
+++ b/docs/dev/data_collector.md
@@ -59,10 +59,10 @@ XXX: There is also the `Chef::Config[:data_collector][:output_locations] = { uri
 differently, particularly on non-chef-solo use cases.  In that case the data collector `server_url` will still be automatically derived from the `chef_server_url` and
 the data collector will attempt to contact that endpoint, but with the token being supplied it will use that and will not use Chef Server authentication, and the
 server should 403 back, and if `raise_on_failure` is left to the default of false then it will simply drop that failure and continue without raising, which will
-appear to work, and output will be send to the configured `output_locations`.  But given how hopelessly complicated this is, the recommendation is to use the
-`server_url` and to avoid using any `url` options in the `output_locations` since that feature is fairly poorly designed at this point in time.  Note that the presence of
-a token flips all external URIs to using the token so that it is not possible to use this feature to talk to both a Chef Automate endpoint and a custom URI reporting
-endpoint (which would seem to be the most useful of an incredibly marginally useful feature and it does not work).
+appear to work, and output will be send to the configured `output_locations`.  Note that the presence of a token flips all external URIs to using the token so that
+it is not possible to use this feature to talk to both a Chef Automate endpoint and a custom URI reporting endpoint (which would seem to be the most useful of an
+incredibly marginally useful feature and it does not work).  But given how hopelessly complicated this is, the recommendation is to use the `server_url` and to avoid
+using any `url` options in the `output_locations` since that feature is fairly poorly designed at this point in time.
 
 ## Resiliency to Failures