Fixing syntax.

_includes/content-reuse/admin-guides/connecting-to-external-services/creating-using-access-tokens-to-authenticate-external-services-qumulo-core.md

@@ -1,4 +1,5 @@
-{% include tip.html content="It is possible to confuse the terms _access token_ and _session token_. Unlike access tokens, session tokens are short-lived and require a password to refresh, for example, to authenticate by using the {% include qq.html command="qq login" %} command. Access tokens are the focus of this section." %}
+{% capture differentTerms %}It is possible to confuse the terms _access token_ and _session token_. Unlike access tokens, session tokens are short-lived and require a password to refresh, for example, to authenticate by using the {% include qq.html command="qq login" %} command. Access tokens are the focus of this section.{% endcapture %}
+{% include tip.html content=differentTerms %}
 
 In Qumulo Core 5.3.0 (and higher), you can use _access tokens_ to let a user authenticate to the Qumulo Core REST API without having to complete repetitive login procedures.
 

_includes/content-reuse/admin-guides/replicating-data/shift-from-s3.md

@@ -235,7 +235,8 @@ Whenever Qumulo Core doesn't complete an operation successfully and returns an e
 We recommend the following best practices for working with Qumulo Shift-From for Amazon S3.
 * **Inheritable Permissions:** Because the system user creates the files that Shift-From for S3 copies, the system owns these files. By default, everyone is granted read permissions and administrators always have full access to the files.
 
-  {% include note.html content="To ensure that the copied files and subdirectories have the correct permissions, you must assign the necessary inheritable permissions to the root directory of the relationship _before_ you create a Shift-From S3 relationship. To edit directory permissions, you can use the Windows Security Dialog or the {% include qq.html command="qq fs_modify_acl` %} command. For more information, see [Qumulo File Permissions Overview](https://care.qumulo.com/hc/en-us/articles/115008211868) on Qumulo Care." %}
+  {% capture ensurePermissions %}To ensure that the copied files and subdirectories have the correct permissions, you must assign the necessary inheritable permissions to the root directory of the relationship _before_ you create a Shift-From S3 relationship. To edit directory permissions, you can use the Windows Security Dialog or the {% include qq.html command="fs_modify_acl" %} command. For more information, see [Qumulo File Permissions Overview](https://care.qumulo.com/hc/en-us/articles/115008211868) on Qumulo Care.{% endcapture %}
+  {% include note.html content=ensurePermissions %}
 
 * **VPC Endpoints:** For best performance when using a Qumulo cluster in AWS, configure a [VPC endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints.html) to S3. For on-premises Qumulo clusters, we recommend [AWS Direct Connect](https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/aws-direct-connect.html) or another high-bandwidth, low-latency connection to S3.
 * **Repeated Synchronization:** If you need to repeatedly synchronize an S3 folder with a Qumulo directory, we recommend reusing the same relationship. This lets you avoid repeated downloading of unchanged objects that already exist locally.

_includes/content-reuse/admin-guides/s3-api/managing-access-to-s3-buckets.md

@@ -124,7 +124,7 @@ To add ACEs to a directory, use the `qq` CLI or use the File Explorer on a Windo
 The following sections show how to use the `qq` CLI to imitate bucket-level permissions by adding inheritable ACEs.
 
 ### Imitating Bucket-Level Read-Write Access
-Run the `qq fs_modify_acl` command. In the following example, we add the access control entry (ACE) to the bucket whose root directory is `/buckets/my-bucket` for the user group `MyWriters`.
+Run the {% include qq.html command="fs_modify_acl" %} command. In the following example, we add the access control entry (ACE) to the bucket whose root directory is `/buckets/my-bucket` for the user group `MyWriters`.
 
 ```bash
 $ qq fs_modify_acl \
@@ -146,7 +146,7 @@ Allowed  Object inherit, Container inherit  Delete child, Execute/Traverse, Read
 
 <a id="bucket-level-read-access"></a>
 ### Imitating Bucket-Level Read-Only Access
-Run the `qq fs_modify_acl` command. In the following example, we add the access control entry (ACE) to the bucket whose root directory is `/buckets/my-bucket` for the user group `MyReaders`:
+Run the {% include qq.html command="fs_modify_acl" %} command. In the following example, we add the access control entry (ACE) to the bucket whose root directory is `/buckets/my-bucket` for the user group `MyReaders`:
 
 ```bash
 $ qq fs_modify_acl
@@ -166,7 +166,7 @@ Allowed  Object inherit, Container inherit  Execute/Traverse, Read
 ```
 
 ### Imitating Bucket-Level List-Only Access
-Run the `qq fs_modify_acl` command. In the following example, we add two access control entries (ACEs) to the bucket whose root directory is `/buckets/my-bucket` for the user group `MyListers`.
+Run the {% include qq.html command="fs_modify_acl" %} command. In the following example, we add two access control entries (ACEs) to the bucket whose root directory is `/buckets/my-bucket` for the user group `MyListers`.
 
 ```bash
 $ qq fs_modify_acl

administrator-guide/network-multitenancy/partitioning-cluster-into-tenants.md

@@ -15,7 +15,8 @@ For each tenant, you can specify individual [management protocol access and conf
 
 
 ## Prerequisites
-{% include important.html content="If your cluster runs a version of Qumulo Core lower than 6.1.0.3, you must run the {% include qq.html command="multitenancy_enable" %} to enable multitenancy for your cluster." %}
+{% capture lowerThan6103 %}If your cluster runs a version of Qumulo Core lower than 6.1.0.3, you must run the {% include qq.html command="multitenancy_enable" %} to enable multitenancy for your cluster.{% endcapture %}
+{% include important.html content=lowerThan6103 %}
 
 To manage network multitenancy and tenants, your user must have membership in a Qumulo role with the following privileges.
 

administrator-guide/upgrading-qumulo-core/performing-upgrades.md

@@ -7,7 +7,7 @@ redirect_from:
   - /administrator-guide/upgrades/instant-software-platform.html
 sidebar: administrator_guide_sidebar
 varContactQumuloCare: If you perform multiple upgrades back to back, you might encounter one or more platform upgrades in one of the incremental releases; you must install these upgrades before you continue. Before performing back to back upgrades, <a href="https://docs.qumulo.com/contacting-qumulo-care-team.html">contact the Qumulo Care team</a> for guidance.
-varViewUpgradeStatus: "To view your cluster's upgrade phase and status, run the {% include qq.html command="upgrade_status" %} command."
+varViewUpgradeStatus: "To view your cluster's upgrade phase and status, run the `qq upgrade_status` command."
 varRollingRebootRefresh: If you don't see a rolling reboot option for a platform upgrade, refresh the page in your browser.
 varDisableProgressBar: "You can disable the CLI progress bar by adding the <code>--no-monitor</code> flag to your command. If you do this, it isn't possible to cancel the upgrade process after it begins."
 varUploadUpgradeFile: "1. Upload the `qumulo_core_x.x.x.qimg` upgrade file to any directory on your cluster by using a client protocol such as NFS or SMB."