[arvados] updated: 2.7.0-6546-g218b4d51dd

[git repository hosting]

Summary of changes:
 doc/install/salt-multi-host.html.textile.liquid | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

       via  218b4d51dd9b31604a37d78bb602151bdc2af4d6 (commit)
      from  887751a6c862fdd9184f5f9c58e6bfaa61269e23 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit 218b4d51dd9b31604a37d78bb602151bdc2af4d6
Author: Brett Smith <brett.smith at curii.com>
Date:   Sun May 12 17:15:35 2024 -0400

    21678: Copyedit installer diagnostics documentation
    
    Small wording and punctuation changes that I hope make things a little
    clearer.
    
    Arvados-DCO-1.1-Signed-off-by: Brett Smith <brett.smith at curii.com>

diff --git a/doc/install/salt-multi-host.html.textile.liquid b/doc/install/salt-multi-host.html.textile.liquid
index 2aa05ca213..ddf9e5d797 100644
--- a/doc/install/salt-multi-host.html.textile.liquid
+++ b/doc/install/salt-multi-host.html.textile.liquid
@@ -392,21 +392,19 @@ This will install and configure Arvados on all the nodes.  It will take a while
 
 h2(#test-install). Confirm the cluster is working
 
-When everything has finished, you can run the diagnostics. There's a couple ways of doing this, as listed below.
+When everything has finished, you can run the diagnostics. There's a couple ways of doing this listed below.
 
 h3. Running diagnostics from the same system as the installer
 
-The requirements to run diagnostics are having @arvados-client@ and @docker@ installed, if this is not possible you can run them on an Arvados node as explained below.
+The requirements to run diagnostics are having @arvados-client@ and @docker@ installed. If this is not possible you can run them on your Arvados shell node as explained in the next section.
 
-Depending on where you are running the installer, you need to provide @-internal-client@ or @-external-client at . For example, if you are running the installer from one of the Arvados hosts inside the private network, you want @-internal-client at .
-
-You are an "external client" if you are running the diagnostics from your workstation outside of the cluster's private network.
+Depending on where you are running the installer, you need to provide @-internal-client@ or @-external-client at . If you are running the installer from a host connected to the Arvados private network, use @-internal-client at . Otherwise, use @-external-client at .
 
 <pre><code class="userinput">./installer.sh diagnostics (-internal-client|-external-client)</code></pre>
 
 h3. Running diagnostics from a cluster node
 
-You can run the diagnostics from the cluster's shell node. This has the advantage that you don't need to manage any software dependency on the local system, but might not be a possibility if your Arvados cluster doesn't include one.
+You can run the diagnostics from the cluster's shell node. This has the advantage that you don't need to manage any software on your local system, but might not be a possibility if your Arvados cluster doesn't include a shell node.
 
 <pre><code class="userinput">./installer.sh diagnostics-internal</code></pre>
 

-----------------------------------------------------------------------


hooks/post-receive
--