A few doc layout and clarity improvements (#12115)

content/en/docs/setup/getting-started/index.md

@@ -14,7 +14,7 @@ test: yes
 {{< tip >}}
 Istio intends to make the Kubernetes [Gateway API](https://gateway-api.sigs.k8s.io/) the default API for traffic management
 [in the future](/blog/2022/gateway-api-beta/).
-Although the Gateway API is currently a beta feature in Istio you can still get started with Istio using the
+Although the Gateway API is currently a beta feature in Istio, you can still get started with Istio using the
 future API if you prefer.
 Refer to the [future getting started instructions](/docs/setup/additional-setup/getting-started/) instead of the following.
 {{< /tip >}}

content/en/docs/tasks/traffic-management/ingress/ingress-control/index.md

@@ -10,7 +10,7 @@ owner: istio/wg-networking-maintainers
 test: yes
 ---
 
-Along with support for Kubernetes [Ingress](/docs/tasks/traffic-management/ingress/kubernetes-ingress/), Istio also allows you to configure ingress traffic
+Along with support for Kubernetes [Ingress](/docs/tasks/traffic-management/ingress/kubernetes-ingress/) resources, Istio also allows you to configure ingress traffic
 using either an [Istio Gateway](/docs/concepts/traffic-management/#gateways) or [Kubernetes Gateway](https://gateway-api.sigs.k8s.io/api-types/gateway/) resource.
 A `Gateway` provides more extensive customization and flexibility than `Ingress`, and allows Istio features such as monitoring and route rules to be applied to traffic entering the cluster.
 
@@ -22,14 +22,28 @@ This task describes how to configure Istio to expose a service outside of the se
 
 *   Setup Istio by following the instructions in the [Installation guide](/docs/setup/).
 
-*   Make sure your current directory is the `istio` directory.
+    {{< tip >}}
+    If you are going to use the `Gateway API` instructions, you can install Istio using the `minimal`
+    profile, because you will not need the `istio-ingressgateway`, which is otherwise installed
+    by default:
 
-*   Start the [httpbin]({{< github_tree >}}/samples/httpbin) sample:
+    {{< text bash >}}
+    $ istioctl install profile=minimal
+    {{< /text >}}
+
+    {{< /tip >}}
+
+*   Start the [httpbin]({{< github_tree >}}/samples/httpbin) sample, which will serve as the target service
+    for ingress traffic:
 
     {{< text bash >}}
     $ kubectl apply -f @samples/httpbin/httpbin.yaml@
     {{< /text >}}
 
+    Note that for the purpose of this document, which shows how to use a gateway to control ingress traffic
+    into your "Kubernetes cluster", you can start the `httpbin` service with or without
+    sidecar injection enabled (i.e., the target service can be either inside or outside of the Istio mesh).
+
 ## Configuring ingress using a gateway
 
 An ingress `Gateway` describes a load balancer operating at the edge of the mesh that receives incoming HTTP/TCP connections.
@@ -220,7 +234,7 @@ If the `EXTERNAL-IP` value is set, your environment has an external load balance
 If the `EXTERNAL-IP` value is `<none>` (or perpetually `<pending>`), your environment does not provide an external load balancer for the ingress gateway.
 
 If your environment does not support external load balancers, you can try
-[accessing the ingress gateway using node ports](#accessing-the-ingress-gateway-using-node-ports).
+[accessing the ingress gateway using node ports](#using-node-ports-of-the-ingress-gateway-service).
 Otherwise, set the ingress IP and ports using the following commands:
 
 {{< text bash >}}

content/en/docs/tasks/traffic-management/ingress/ingress-control/snips.sh

@@ -22,6 +22,10 @@
 source "content/en/boilerplates/snips/gateway-api-support.sh"
 
 snip_before_you_begin_1() {
+istioctl install profile=minimal
+}
+
+snip_before_you_begin_2() {
 kubectl apply -f samples/httpbin/httpbin.yaml
 }
 

content/en/docs/tasks/traffic-management/ingress/secure-ingress/index.md

@@ -80,6 +80,7 @@ You can use your favorite tool to create them or use the commands below to gener
     $ openssl x509 -req -sha256 -days 365 -CA example_certs1/example.com.crt -CAkey example_certs1/example.com.key -set_serial 1 -in example_certs1/client.example.com.csr -out example_certs1/client.example.com.crt
     {{< /text >}}
 
+{{< tip >}}
 You can confirm that you have all of the needed files by running the following command:
 
 {{< text bash >}}
@@ -95,6 +96,8 @@ example.com.crt         httpbin.example.com.crt httpbin.example.com.key
 example.com.key         httpbin.example.com.csr
 {{< /text >}}
 
+{{< /tip >}}
+
 ### Configure a TLS ingress gateway for a single host
 
 1.  Create a secret for the ingress gateway: