Skip to content

Commit

Permalink
fix vale nags - round 1
Browse files Browse the repository at this point in the history
Signed-off-by: Craig <[email protected]>
  • Loading branch information
craig-osterhout committed Dec 10, 2024
1 parent 3dfbf03 commit ef93e83
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 5 deletions.
4 changes: 3 additions & 1 deletion _vale/config/vocabularies/Docker/accept.txt
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,8 @@ Windows
WireMock
Zscaler
Zsh
[Aa]utobuild
[Aa]utobuilds?
[Aa]tests?
[Bb]uildx
[Bb]uildpack(s)?
[Cc]odenames?
Expand All @@ -119,6 +120,7 @@ Zsh
[Pp]roxied
[Pp]roxying
[Rr]eal-time
[Rr]egex(es)?
[Rr]untimes?
[Ss]andbox(ed)?
[Ss]eccomp
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ services:
command: run_tests.sh
```
The example above builds the repository, and runs the `run_tests.sh` file inside
The previous example builds the repository, and runs the `run_tests.sh` file inside
a container using the built image.

You can define any number of linked services in this file. The only requirement
Expand Down
6 changes: 3 additions & 3 deletions content/manuals/docker-hub/repos/manage/builds/setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ when the tests succeed.
>
> You may be redirected to the settings page to [link](link-source.md) the
> code repository service. Otherwise, if you are editing the build settings
> for an existing automated build, click **Configure automated builds**.
> for an existing automated build, select **Configure automated builds**.
4. Select the **source repository** to build the Docker images from.

Expand Down Expand Up @@ -289,9 +289,9 @@ variable to automated builds associated with the account. For more information,

> [!NOTE]
>
> You may need to log out of your individual account on the source code provider to create the link to the service account.
> You may need to sign out of your individual account on the source code provider to create the link to the service account.
6. Optional: Use the SSH keys you generated to set up any builds with private submodules, using the service account and [the instructions above](troubleshoot.md#build-repositories-with-linked-private-submodules).
6. Optional: Use the SSH keys you generated to set up any builds with private submodules, using the service account and [the previous instructions](troubleshoot.md#build-repositories-with-linked-private-submodules).

## What's Next?

Expand Down

0 comments on commit ef93e83

Please sign in to comment.