build(ci): some fixes and lint

Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>

build/ci/github-actions/index.md

@@ -14,21 +14,19 @@ components for building, annotating, and pushing images.
 
 The following GitHub Actions are available:
 
-- [Build and push Docker images](https://github.com/marketplace/actions/build-and-push-docker-images){:
-  target="blank" rel="noopener" class=""}: build and push Docker images with
-  BuildKit.
-- [Docker Login](https://github.com/marketplace/actions/docker-login){:
-  target="blank" rel="noopener"}: sign in to a Docker registry.
-- [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx){:
-  target="blank" rel="noopener"}: initiates a BuildKit builder
-- [Docker Metadata action](https://github.com/marketplace/actions/docker-metadata-action){:
-  target="blank" rel="noopener"}: extracts metadata from Git reference and
-  GitHub events.
-- [Docker Setup QEMU](https://github.com/marketplace/actions/docker-setup-qemu){:
-  target="blank" rel="noopener"}: installs [QEMU](https://github.com/qemu/qemu)
-  static binaries for multi-arch builds.
-- [Docker Buildx Bake](https://github.com/marketplace/actions/docker-buildx-bake){:
-  target="blank" rel="noopener"}: enables using `docker buildx bake`.
+- [Build and push Docker images](https://github.com/marketplace/actions/build-and-push-docker-images){: target="_blank" rel="noopener" class="_" }:
+  build and push Docker images with BuildKit.
+- [Docker Login](https://github.com/marketplace/actions/docker-login){: target="_blank" rel="noopener" class="_" }:
+  sign in to a Docker registry.
+- [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx){: target="_blank" rel="noopener" class="_" }:
+  initiates a BuildKit builder.
+- [Docker Metadata action](https://github.com/marketplace/actions/docker-metadata-action){: target="_blank" rel="noopener" class="_" }:
+  extracts metadata from Git reference and GitHub events.
+- [Docker Setup QEMU](https://github.com/marketplace/actions/docker-setup-qemu){: target="_blank" rel="noopener" class="_" }:
+  installs [QEMU](https://github.com/qemu/qemu) static binaries for multi-arch
+  builds.
+- [Docker Buildx Bake](https://github.com/marketplace/actions/docker-buildx-bake){: target="_blank" rel="noopener" class="_" }:
+  enables using high-level builds with [Bake](../../customize/bake/index.md).
 
 Using Docker's actions provides an easy-to-use interface, while still allowing
 flexibility for customizing build parameters.
@@ -44,6 +42,5 @@ using the official Docker actions, to build and push an image to Docker Hub.
 
 There are many more things you can do to customize your workflow to better suit
 your needs. To learn more about some of the more advanced use cases, take a look
-at the advanced examples, such as
-[building multi-platform images](examples.md#multi-platform-images), or
-[using cache storage backends](examples.md#cache).
+at the advanced examples, such as [building multi-platform images](examples.md#multi-platform-images),
+or [using cache storage backends](examples.md#cache).

build/ci/index.md

@@ -11,8 +11,7 @@ looking to get your code changes merged with the main branch of the project. At
 this point, development teams run tests and builds to vet that the code changes
 don't cause any unwanted or unexpected behaviors.
 
-![Git branches about to get merged](./images/continuous-integration.svg){:
-.invertible }
+![Git branches about to get merged](./images/continuous-integration.svg){: .invertible }
 
 There are several uses for Docker at this stage of development, even if you
 don't end up packaging your application as a container image.
@@ -37,14 +36,10 @@ image, just like you would for any other containerized application.
 The following links provide instructions for how you can get started using
 Docker for building your applications in CI:
 
-- [GitHub Actions](https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action){:
-  target="blank" rel="noopener" class=""}
-- [GitLab](https://docs.gitlab.com/runner/executors/docker.html){:
-  target="blank" rel="noopener" class=""}
-- [Circle CI](https://circleci.com/docs/using-docker/){: target="blank"
-  rel="noopener" class=""}
-- [Render](https://render.com/docs/docker){: target="blank" rel="noopener"
-  class=""}
+- [GitHub Actions](https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action){: target="_blank" rel="noopener" class="_" }
+- [GitLab](https://docs.gitlab.com/runner/executors/docker.html){: target="_blank" rel="noopener" class="_" }
+- [Circle CI](https://circleci.com/docs/using-docker/){: target="_blank" rel="noopener" class="_" }
+- [Render](https://render.com/docs/docker){: target="_blank" rel="noopener" class="_" }
 
 ### Docker in Docker
 
@@ -52,7 +47,7 @@ You can also use a Dockerized build environment to build container images using
 Docker. That is, your build environment runs inside a container which itself is
 equipped to run Docker builds. This method is referred to as "Docker in Docker".
 
-Docker provides an official [Docker image](https://hub.docker.com/_/docker) that
+Docker provides an official [Docker image](https://hub.docker.com/_/docker){: target="_blank" rel="noopener" class="_" }
 that you can use for this purpose.
 
 ## What's next

build/index.md

@@ -85,10 +85,9 @@ pull, and run images seamlessly on different computer architectures:
 ### GitHub Actions
 
 Automate your image builds to run in GitHub actions using the official docker
-build actions:
+build actions.
 
-* [GitHub Action to build and push Docker images with Buildx](https://github.com/docker/build-push-action).
-* [GitHub Action to extract metadata from Git reference and GitHub events](https://github.com/docker/metadata-action/).
+[GitHub Actions](ci/github-actions/index.md){: .button .outline-btn }
 
 ## Customizing your builds