Merge pull request #108692 from TimShererWithAquent/us1679050x

Change SSL to TLS per 1679050

Author: PRMerger6

articles/application-gateway/ingress-controller-annotations.md

@@ -22,7 +22,7 @@ For an Ingress resource to be observed by AGIC, it **must be annotated** with `k
 | Annotation Key | Value Type | Default Value | Allowed Values
 | -- | -- | -- | -- |
 | [appgw.ingress.kubernetes.io/backend-path-prefix](#backend-path-prefix) | `string` | `nil` | |
-| [appgw.ingress.kubernetes.io/ssl-redirect](#ssl-redirect) | `bool` | `false` | |
+| [appgw.ingress.kubernetes.io/ssl-redirect](#tls-redirect) | `bool` | `false` | |
 | [appgw.ingress.kubernetes.io/connection-draining](#connection-draining) | `bool` | `false` | |
 | [appgw.ingress.kubernetes.io/connection-draining-timeout](#connection-draining) | `int32` (seconds) | `30` | |
 | [appgw.ingress.kubernetes.io/cookie-based-affinity](#cookie-based-affinity) | `bool` | `false` | |
@@ -65,7 +65,7 @@ In the example above, we have defined an ingress resource named `go-server-ingre
 > [!NOTE] 
 > In the above example we have only one rule defined. However, the annotations are applicable to the entire ingress resource, so if a user had defined multiple rules, the backend path prefix would be set up for each of the paths specified. Thus, if a user wants different rules with different path prefixes (even for the same service) they would need to define different ingress resources.
 
-## SSL Redirect
+## TLS Redirect
 
 Application Gateway [can be configured](https://docs.microsoft.com/azure/application-gateway/application-gateway-redirect-overview)
 to automatically redirect HTTP URLs to their HTTPS counterparts. When this

articles/application-gateway/ingress-controller-overview.md

@@ -26,8 +26,8 @@ Using Application Gateway in addition to AGIC also helps protect your AKS cluste
 AGIC is configured via the Kubernetes [Ingress resource](https://kubernetes.io/docs/user-guide/ingress/), along with Service and Deployments/Pods. It provides a number of features, leveraging Azure’s native Application Gateway L7 load balancer. To name a few:
   - URL routing
   - Cookie-based affinity
-  - SSL termination
-  - End-to-end SSL
+  - TLS termination
+  - End-to-end TLS
   - Support for public, private, and hybrid web sites
   - Integrated web application firewall