Merge pull request #22078 from docker/published-update

publish updates from main

Author: sarahsanders-docker

assets/css/lists.css

@@ -0,0 +1,12 @@
+.prose ol {
+    list-style-type: decimal;
+}
+
+.prose ol ol {
+    list-style-type: lower-alpha;
+}
+
+.prose ol ol ol {
+    list-style-type: lower-roman;
+}
+

assets/css/styles.css

@@ -13,3 +13,4 @@
 @import "/assets/css/syntax-light";
 @import "/assets/css/syntax-dark";
 @import "/assets/css/icons";
+@import "/assets/css/lists";

content/manuals/compose/install/standalone.md

@@ -48,7 +48,7 @@ on Microsoft Windows Server](/manuals/engine/install/binaries.md#install-server-
     In order to proceed with the installation, select **Yes** when asked if you want this app to make changes to your device.
 
 2.  Optional. Ensure TLS1.2 is enabled. 
-    GitHub requires TLS1.2 fore secure connections. If you’re using an older version of Windows Server, for example 2016, or suspect that TLS1.2 is not enabled, run the following command in PowerShell:
+    GitHub requires TLS1.2 for secure connections. If you’re using an older version of Windows Server, for example 2016, or suspect that TLS1.2 is not enabled, run the following command in PowerShell:
 
     ```powershell
     [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

content/manuals/security/for-admins/access-tokens.md

@@ -15,13 +15,12 @@ params:
 
 > [!WARNING]
 >
-> Organization access tokens (OATs) are not intended to be used with Docker Desktop, and are incompatible.
+> Organization access tokens (OATs) are not intended to be used with Docker 
+> Desktop, and are incompatible.
 >
 > OATs are also currently incompatible with the following services:
 >
-> - Docker Build Cloud
 > - Docker Scout
-> - Docker REST APIs
 >
 > If you use Docker Desktop or one of these services, you must use personal access tokens instead.
 
@@ -38,8 +37,8 @@ OATs provide the following advantages:
   if you find any suspicious activity.
 - You can limit what each OAT has access to, which limits the impact if an OAT
   is compromised.
-- All organization owners can manage OATs. If one owner leaves the organization,
-  the remaining owners can still manage the OATs.
+- All company or organization owners can manage OATs. If one owner leaves the 
+  organization, the remaining owners can still manage the OATs.
 - OATs have their own Docker Hub usage limits that don't count towards your
   personal account's limits.
 
@@ -55,18 +54,19 @@ If you have existing [service accounts](/docker-hub/service-accounts/), Docker r
   it.
 - OATs are not associated with a single user. If a user with access to the
   service account leaves your organization, you may lose access to the service
-  account. OATs can be managed by any organization owner.
+  account. OATs can be managed by any company or organization owner.
 
 ## Create an organization access token
 
 > [!IMPORTANT]
 >
-> Treat access tokens like a password and keep them secret. Store your tokens securely in a credential manager for example.
+> Treat access tokens like a password and keep them secret. Store your tokens 
+> securely in a credential manager for example.
 
-Organization owners can create up to 10 organization access tokens (OATs) for
-organizations with a Team subscription and up to 100 OATs for organizations with
-a Business subscription. Expired tokens count towards the total amount of
-tokens.
+Company or organization owners can create up to 10 organization access tokens 
+(OATs) for organizations with a Team subscription and up to 100 OATs for 
+organizations with a Business subscription. Expired tokens count towards the 
+total amount of tokens.
 
 To create an OAT:
 

content/manuals/security/for-admins/single-sign-on/troubleshoot.md

@@ -0,0 +1,6 @@
+---
+build:
+  render: never
+title: Troubleshoot
+weight: 40
+---