Skip to content

Commit d1915d1

Browse files
committed
Improving Acrolinx score for OSM doc
1 parent 66f0960 commit d1915d1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/aks/open-service-mesh-about.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.author: pgibson
1212

1313
OSM runs an Envoy-based control plane on Kubernetes and can be configured with [SMI](https://smi-spec.io/) APIs. OSM works by injecting an Envoy proxy as a sidecar container with each instance of your application. The Envoy proxy contains and executes rules around access control policies, implements routing configuration, and captures metrics. The control plane continually configures the Envoy proxies to ensure policies and routing rules are up to date and proxies are healthy.
1414

15-
The OSM project was originated by Microsoft and has since been donate. It's now governed by the [Cloud Native Computing Foundation (CNCF)](https://www.cncf.io/).
15+
Microsoft started the OSM project, but it's now governed by the [Cloud Native Computing Foundation (CNCF)](https://www.cncf.io/).
1616

1717
## Enable the OSM add-on
1818

@@ -43,13 +43,13 @@ OSM provides the following capabilities and features:
4343
- Integrate with external certificate management.
4444
- Integrate with existing ingress solutions such as [NGINX][nginx], [Contour][contour], and [Web Application Routing][web-app-routing].
4545

46-
For more details on ingress and OSM, see [Using ingress to manage external access to services within the cluster][osm-ingress] and [Integrate OSM with Contour for ingress][osm-contour]. For an example on integrating OSM with ingress controllers using the `networking.k8s.io/v1` API, such as NGINX, see [Ingress with Kubernetes Nginx ingress controller][osm-nginx]. For more details on using Web Application Routing, which automatically integrates with OSM, see [Web Application Routing][web-app-routing].
46+
For more information on ingress and OSM, see [Using ingress to manage external access to services within the cluster][osm-ingress] and [Integrate OSM with Contour for ingress][osm-contour]. For an example of how to integrate OSM with ingress controllers using the `networking.k8s.io/v1` API, see [Ingress with Kubernetes Nginx ingress controller][osm-nginx]. For more information on using Web Application Routing, which automatically integrates with OSM, see [Web Application Routing][web-app-routing].
4747

4848
## Limitations
4949

5050
The OSM AKS add-on has the following limitations:
5151

52-
- After installation, you must enable Iptables redirection for port IP address and port range exclusion using `kubectl patch`. For more details, see [iptables redirection][ip-tables-redirection].
52+
- After installation, you must enable Iptables redirection for port IP address and port range exclusion using `kubectl patch`. For more information, see [iptables redirection][ip-tables-redirection].
5353
- Any pods that need access to IMDS, Azure DNS, or the Kubernetes API server must have their IP addresses added to the global list of excluded outbound IP ranges using [Global outbound IP range exclusions][global-exclusion].
5454
- OSM doesn't support Windows Server containers.
5555

0 commit comments

Comments
 (0)