[OSDOCS-15295] Update nw-customize-ingress-error-pages.adoc

Command correction in Customizing HAProxy error code response pages 
Here is the documentation link:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/networking/networking-operators#nw-customize-ingress-error-pages_configuring-ingress 

Here is the current look:

Procedure

Create a config map named my-custom-error-code-pages in the openshift-config namespace:
$ oc -n openshift-config create configmap my-custom-error-code-pages \
--from-file=error-page-503.http \
--from-file=error-page-404.http 
The above command is not structured properly.
We can use the above command as well, and it will execute perfectly.
But its structure is not as per our standard procedure.
Hence, it needs to be changed.
Here is the updatd look:

Procedure

Create a config map named my-custom-error-code-pages in the openshift-config namespace:
$ oc -n openshift-config create configmap my-custom-error-code-pages \
  --from-file=error-page-503.http \
  --from-file=error-page-404.http

Author: prithvipatil97

modules/nw-customize-ingress-error-pages.adoc

@@ -27,8 +27,8 @@ If you use the {product-title} default 503 error code page as a template for you
 [source,terminal]
 ----
 $ oc -n openshift-config create configmap my-custom-error-code-pages \
---from-file=error-page-503.http \
---from-file=error-page-404.http
+  --from-file=error-page-503.http \
+  --from-file=error-page-404.http
 ----
 
 . Patch the Ingress Controller to reference the `my-custom-error-code-pages` config map by name:
@@ -84,7 +84,7 @@ Verify your custom error code HTTP response:
 +
 [source,terminal]
 ----
-$ oc new-app django-psql-example
+ $ oc new-app django-psql-example
 ----
 
 . For 503 custom http error code response: