[AIRFLOW-XXX] Fix typo and format error (apache#6149)

BREEZE.rst

@@ -916,7 +916,7 @@ There are three images that we currently manage:
 
 * **Slim CI** image that is used for static code checks (size around 500MB) - tag follows the pattern
   of ``<BRANCH>-python<PYTHON_VERSION>-ci-slim`` (for example ``apache/airflow:master-python3.6-ci-slim``).
-  The image is built using the [Dockerfile](Dockerfile) dockerfile.
+  The image is built using the `<Dockerfile>`_ dockerfile.
 * **Full CI image*** that is used for testing - containing a lot more test-related installed software
   (size around 1GB)  - tag follows the pattern of ``<BRANCH>-python<PYTHON_VERSION>-ci``
   (for example ``apache/airflow:master-python3.6-ci``). The image is built using the

Dockerfile

@@ -38,7 +38,7 @@ ENV AIRFLOW_VERSION=$AIRFLOW_VERSION
 RUN echo "Base image: ${PYTHON_BASE_IMAGE}"
 RUN echo "Airflow version: ${AIRFLOW_VERSION}"
 
-# Make sure noninteractie debian install is used and language variables set
+# Make sure noninteractive debian install is used and language variables set
 ENV DEBIAN_FRONTEND=noninteractive LANGUAGE=C.UTF-8 LANG=C.UTF-8 LC_ALL=C.UTF-8 \
     LC_CTYPE=C.UTF-8 LC_MESSAGES=C.UTF-8
 

scripts/ci/docker_build/ci_build_install_deps.sh

@@ -20,7 +20,7 @@
 set -euxo pipefail
 
 # TODO: We should think about removing those and moving them into docker-compose dependencies.
-# TODO: We might come up with just ine airflow CI image not the SLIM/CI versions. That would simplify a lot.
+# TODO: We might come up with just one airflow CI image not the SLIM/CI versions. That would simplify a lot.
 # TODO: We could likely get rid of the multi-staging approach. It introduces a number of limitations
 # TODO: As long as we decrease the size of the CI image, we should be fine with using single CI image for
 # TODO: everything. Currently the CI image is about 1GB where CI_SLIM is around 0.5 GB.