rework on documentation.

Author: saheerb

.github/workflows/docker_management.branch.yml

@@ -196,8 +196,6 @@ jobs:
 
           run: |
             uname -m
-            ls
-            #./mbed-os/docker_images/mbed-os-env/test.sh DEVELOPMENT ${{ steps.build_info.outputs.MBED_OS_VERSION }}
             cd mbed-os-example-blinky
             mbed deploy
             # build using CLI1

docker_images/mbed-os-env/README.md

@@ -42,7 +42,7 @@ To make sure your Mbed targets have been detected, you might want to manually ru
 mount /dev/sdb /mnt
 mbedls
 ```
-If `mbedls` detected  your connected target, then you should be able to run Mbed tests/examples as recommended in Mbed documentation.
+If `mbedls` detected  your connected target, then you should be able to run Mbed tests/examples as recommended in the Mbed documentation.
 ``` bash
 mbed clone https://github.com/ARMmbed/mbed-os.git
 cd mbed-os

docs/design-documents/docker_management/README.md

@@ -3,7 +3,7 @@
 
 ### Overview and background
 
-The docker image mbed-os-env bundles all the necessary tools to provide a minimal environment to build and test mbed-os applications. This docker image shall be used in Continuous Integration pipelines or in other use cases where mbed-os tools and dependencies are required. This document explains versioning strategy of the docker image and github action workflows that creates these docker images.
+The docker image mbed-os-env bundles all the necessary tools to provide a minimal environment to build and test mbed-os applications. This docker image shall be used in Continuous Integration pipelines or in other use cases where mbed-os tools and dependencies are required. This document explains versioning strategy of the docker image and GitHub action workflows that creates these docker images.
 
 
 ### Types of docker images
@@ -106,15 +106,13 @@ There are some details worth mentioning though.
 
 docker buildx command is used for creating multi architecture docker image. To build docker image using buildx, one needs to push the image to a remote repository while building it. Since, we need to "test" before release, the resulting images are pushed to a temporary docker repository just after building.
 
-github container registry doesn't implement yet all the docker manifest APIs. Hence, a few features like deleting tag from an image is not available yet. Once these are implemented, we may remove temporary repository and add temporary tags to the image and delete the temporary tags after workflow.
+GitHub container registry doesn't implement yet all the docker manifest APIs. Hence, a few features like deleting tag from an image is not available yet. Once these are implemented, we may remove temporary repository and add temporary tags to the image and delete the temporary tags after workflow.
 
 **Test**
-Once temporary images are built, we need to verify whether image built is same as the image already available as our intended docker image version. This is achieved by comparing the docker digest of two images. Obviously, if digest is same, there is no need to make another release as docker image available as released version is already up to date.
-
-If the digest is different, (means, new version of docker image is built), test.sh script takes care of all the testing.
+After the temporary docker image is built, GitHub Actions tests the image prior to deploying the image to the production Docker repository. Please refer to the `test-container` job in the workflow for details on the test plan.
 
 **Deploy**
-In Deploy job, depending on the result of test job, temporary images are moved to production repository.
+In `Deploy` job, depending on the result of test job, temporary images are moved to production repository.
 
 ### Docker repository
 GitHub provides free docker image storage for public repositories in GitHub packages. The workflows make use of {{ secrets.GITHUB_TOKEN }}  https://docs.github.com/en/actions/reference/authentication-in-a-workflow 
@@ -127,7 +125,7 @@ There are two repositories being created or used for managing docker image
 
 **mbed-os-env** This is the public repository user can pull the images from.
 
-**mbed-os-env-tmp** This is a private repository created for temporary management of docker images while docker images are being tested. This is a staging area. Unfortunately, github container registry do no support renaming docker tags, hence the need for a temporary repository.
+**mbed-os-env-tmp** This is a private repository created for temporary management of docker images while docker images are being tested. This is a staging area. Unfortunately, GitHub container registry do no support renaming docker tags, hence the need for a temporary repository.
 
 ### Workflow for forks