Apply suggestions from code review

Co-authored-by: Nathan Coleman <nathan.coleman@hashicorp.com>

website/content/api-docs/agent/service.mdx

@@ -635,7 +635,7 @@ The `/agent/service/register` endpoint supports camel case and _snake case_ for
   - `"connect-proxy"` for [service mesh](/consul/docs/connect) proxies representing another service
   - `"mesh-gateway"` for instances of a [mesh gateway](/consul/docs/connect/gateways/mesh-gateway#service-mesh-proxy-configuration)
   - `"terminating-gateway"` for instances of a [terminating gateway](/consul/docs/connect/gateways/terminating-gateway)
-  - `"ingress-gateway"` for instances of a [ingress gateway](/consul/docs/connect/gateways/ingress-gateway)
+  - `"ingress-gateway"` for instances of an [ingress gateway](/consul/docs/connect/gateways/ingress-gateway)
 
 - `Proxy` `(Proxy: nil)` - From 1.2.3 on, specifies the configuration for a
   service mesh proxy instance. This is only valid if `Kind` defines a proxy or gateway.

website/content/docs/connect/gateways/ingress-gateway/ingress-gateways-usage.mdx

@@ -98,7 +98,7 @@ $ consul connect envoy -gateway=ingress ingress-service'
 You can also automatically register the ingress gateway service when starting the Envoy proxy. Specify the following flags with the `consul connect envoy` command:  
 
 - `-gateway=ingress`
-- `-register`: This  
+- `-register`
 - `-service=<name of the service>`
 
 The following example starts Envoy and registers an ingress gateway service named `ingress-service` bound to the agent address at port `8888`: