Skip to content

Commit c13e563

Browse files
authored
Merge pull request #21514 from docker/published-update
publish updates from main
2 parents 09c7538 + 6e2a78f commit c13e563

File tree

4 files changed

+5
-7
lines changed

4 files changed

+5
-7
lines changed

content/guides/admin-set-up/comms-and-info-gathering.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,4 +30,4 @@ To view the parameters that can be preset, see [Configure Settings Management](/
3030

3131
## Optional step four: Meet with the Docker Implementation team
3232

33-
The Docker Implementation team can help you step through setting up your organization, configuring SSO, enforcing sign in, and configuring Docker. You can reach out to set up a meeting by emailing [email protected].
33+
The Docker Implementation team can help you step through setting up your organization, configuring SSO, enforcing sign-in, and configuring Docker. You can reach out to set up a meeting by emailing [email protected].

content/guides/admin-set-up/finalize-plans-and-setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ weight: 20
66

77
## Step one: Send finalized settings files to the MDM team
88

9-
After reaching an agreement with the relevant teams on your baseline and security configurations as outlined in module one, follow the instructions in the [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md) documentation to create the `admin-settings.json` file that captures these configurations.
9+
After reaching an agreement with the relevant teams about your baseline and security configurations as outlined in module one, configure Settings Management using either the [Docker Admin Console](/manuals/security/for-admins/hardened-desktop/settings-management/configure-admin-console.md) or an [`admin-settings.json` file](/manuals/security/for-admins/hardened-desktop/settings-management/configure-json-file.md).
1010

11-
Once the file is ready, collaborate with your MDM team to deploy the `admin-settings.json` file, along with your chosen method for [enforcing sign-in](/manuals/security/for-admins/enforce-sign-in/_index.md).
11+
Once the file is ready, collaborate with your MDM team to deploy your chosen settings, along with your chosen method for [enforcing sign-in](/manuals/security/for-admins/enforce-sign-in/_index.md).
1212

1313
> [!IMPORTANT]
1414
>

content/guides/admin-set-up/testing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,10 +23,10 @@ If you plan to use [Registry Access Management (RAM)](/manuals/security/for-admi
2323

2424
Deploy the Docker settings and enforce sign-in for a small group of test users via MDM. Have this group test their development workflows with containers on Docker Desktop and Docker Hub to ensure all settings and the sign-in enforcement function as expected.
2525

26-
## Test Build Cloud capabilities
26+
## Test Docker Build Cloud capabilities
2727

2828
Have one of your Docker Desktop testers [connect to the cloud builder you created and use it to build](/manuals/build-cloud/usage.md).
2929

30-
## Verify Scout monitoring of repositories
30+
## Verify Docker Scout monitoring of repositories
3131

3232
Check the [Docker Scout dashboard](https://scout.docker.com/) to confirm that data is being properly received for the repositories where Docker Scout has been enabled.

content/manuals/docker-hub/repos/create.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ title: Create a repository
55
linkTitle: Create
66
toc_max: 3
77
weight: 20
8-
aliases:
9-
- /docker-hub/repos/create/
108
---
119

1210
1. Sign in to [Docker Hub](https://hub.docker.com).

0 commit comments

Comments
 (0)