Apply suggestions from code review

Co-authored-by: Cary Chai <[email protected]>

Author: craigshoemaker

articles/container-apps/ingress-how-to.md

@@ -28,13 +28,15 @@ You can set the following ingress template properties:
 | `external` | Allow ingress to your app from outside its Container Apps environment. |`true` or `false`(default) | Yes |
 | `ipSecurityRestrictions` | IP ingress restrictions. See [Set up IP ingress restrictions](ip-restrictions.md) | An array of rules | No |
 | `stickySessions.affinity` | Enables [session affinity](sticky-sessions.md). | `none` (default), `sticky` | No |
-| `targetPort` | The port your container app listens to for incoming requests. | Set this value to the port number that your container uses. For HTTP ingress, your application ingress endpoint is always exposed on port `443`. | Yes |
+| `targetPort` | The port your container app listens to for incoming requests. | Set this value to the port number that your container app uses. For HTTP ingress, your application ingress endpoint is always exposed on port `443`. | Yes |
 | `traffic` | [Traffic splitting](traffic-splitting.md) weights split between revisions. | An array of rules | No |
 | `transport` | The transport protocol type. | auto (default) detects HTTP/1 or HTTP/2, `http` for HTTP/1, `http2` for HTTP/2, `tcp` for TCP. | No |
 
 ### Automatic port detection
 
-If your container app listens on ports 80 or 443, Container Apps detects this automatically.
+If your container app has HTTP ingress enabled and you have not set a target port, Azure Container Apps will automatically detect the target port by scanning all listening ports on your container. If there is only one port detected, that port will be set as the target port for your container app. If there is more than 1 port detected, the container app will not automatically set the target port, and you will need to set the target port manually. 
+ 
+Health probes by default are configured to use the same target port as your container. If the application has health endpoints configured to listen on a secondary port on your app, this may lead to issues with the automatic port detection. Sidecars such as Dapr which expose additional ports may also interfere with automatic port detection.
     - Automatic port detection only works for HTTP traffic, not TCP traffic.
     - If you have HTTP health probes listening on ports 80 or 443, this can interfere with automatic port detection. The default ingress configuration uses TCP health probes. For more information see [health probes](health-probes.md).