Merge pull request #21328 from dvdksn/fix-basics-concepts-typo

chore: fix typos and formatting issues in 'what is an image'

content/get-started/docker-concepts/the-basics/what-is-an-image.md

@@ -11,11 +11,9 @@ aliases:
 
 ## Explanation
 
-Seeing a [container](./what-is-a-container) is an isolated process, where does it get its files and configuration? How do you share those environments? 
+Seeing a [container](./what-is-a-container.md) is an isolated process, where does it get its files and configuration? How do you share those environments?
 
-That's where container images come in! 
+That's where container images come in. A container image is a standardized package that includes all of the files, binaries, libraries, and configurations to run a container.
-
-A container image is a standardized package that includes all of the files, binaries, libraries, and configurations to run a container.
 
 For a [PostgreSQL](https://hub.docker.com/_/postgres) image, that image will package the database binaries, config files, and other dependencies. For a Python web app, it'll include the Python runtime, your app code, and all of its dependencies.
 
@@ -23,7 +21,7 @@ There are two important principles of images:
 
 1. Images are immutable. Once an image is created, it can't be modified. You can only make a new image or add changes on top of it.
 
-2. Container images are composed of layers. Each layer represented a set of file system changes that add, remove, or modify files.
+2. Container images are composed of layers. Each layer represents a set of file system changes that add, remove, or modify files.
 
 These two principles let you to extend or add to existing images. For example, if you are building a Python app, you can start from the [Python image](https://hub.docker.com/_/python) and add additional layers to install your app's dependencies and add your code. This lets you focus on your app, rather than Python itself.
 
@@ -62,7 +60,6 @@ In this hands-on, you will learn how to search and pull a container image using
 
 4. Select **Pull** to download the image.
 
-
 ### Learn about the image
 
 Once you have an image downloaded, you can learn quite a few details about the image either through the GUI or the CLI.
@@ -77,8 +74,6 @@ Once you have an image downloaded, you can learn quite a few details about the i
 
    ![A screenshot of the image details view for the docker/welcome-to-docker image](images/image-layers.webp?border=true&w=1050&h=400)
 
-
-
 {{< /tab >}}
 
 {{< tab name="Using the CLI" >}}
@@ -87,7 +82,7 @@ Follow the instructions to search and pull a Docker image using CLI to view its
 
 ### Search for and download an image
 
-1. Open a terminal and search for images using the [`docker search`](/reference/cli/docker/search/) command:
+1. Open a terminal and search for images using the [`docker search`](/reference/cli/docker/search.md) command:
 
    ```console
    docker search docker/welcome-to-docker
@@ -102,7 +97,7 @@ Follow the instructions to search and pull a Docker image using CLI to view its
 
    This output shows you information about relevant images available on Docker Hub.
 
-2. Pull the image using the [`docker pull`](/reference/cli/docker/image/pull/) command.
+2. Pull the image using the [`docker pull`](/reference/cli/docker/image/pull.md) command.
 
    ```console
    docker pull docker/welcome-to-docker
@@ -128,10 +123,9 @@ Follow the instructions to search and pull a Docker image using CLI to view its
 
    Each of line represents a different downloaded layer of the image. Remember that each layer is a set of filesystem changes and provides functionality of the image.
 
-
 ### Learn about the image
 
-1. List your downloaded images using the [`docker image ls`](/reference/cli/docker/image/ls/) command:
+1. List your downloaded images using the [`docker image ls`](/reference/cli/docker/image/ls.md) command:
 
    ```console
    docker image ls
@@ -150,7 +144,7 @@ Follow the instructions to search and pull a Docker image using CLI to view its
    >
    > The image size represented here reflects the uncompressed size of the image, not the download size of the layers.
 
-2. List the image's layers using the [`docker image history`](/reference/cli/docker/image/history/) command:
+2. List the image's layers using the [`docker image history`](/reference/cli/docker/image/history.md) command:
 
    ```console
    docker image history docker/welcome-to-docker
@@ -184,7 +178,6 @@ Follow the instructions to search and pull a Docker image using CLI to view its
    >
    > If you add the `--no-trunc` flag to the command, you will see the full command. Note that, since the output is in a table-like format, longer commands will cause the output to be very difficult to navigate.
 
-
 {{< /tab >}}
 {{< /tabs >}}
 
@@ -194,12 +187,12 @@ In this walkthrough, you searched and pulled a Docker image. In addition to pull
 
 The following resources will help you learn more about exploring, finding, and building images:
 
-- [Docker Trusted Content](/trusted-content/)
+- [Docker Trusted Content](/manuals/trusted-content/_index.md)
-  - [Docker Official Images docs](/trusted-content/official-images/)
+  - [Docker Official Images docs](/manuals/trusted-content/official-images/_index.md)
-  - [Docker Verified Publisher docs](/trusted-content/dvp-program/)
+  - [Docker Verified Publisher docs](/manuals/trusted-content/dvp-program.md)
-  - [Docker-Sponsored Open Source Program docs](/trusted-content/dsos-program/)
+  - [Docker-Sponsored Open Source Program docs](/manuals/trusted-content/dsos-program.md)
-- [Explore the Image view in Docker Desktop](/desktop/use-desktop/images/)
+- [Explore the Image view in Docker Desktop](/manuals/desktop/use-desktop/images.md)
-- [Packaging your software](/build/building/packaging/)
+- [Docker Build overview](/manuals/build/concepts/overview.md)
 - [Docker Hub](https://hub.docker.com)
 
 ## Next steps