Update README to better match support doc

README.md

@@ -1,47 +1,33 @@
-# 🚀 *Help make the NGINX Ingress Controller better by participating in our [survey](https://forms.office.com/Pages/ResponsePage.aspx?id=L_093Ttq0UCb4L-DJ9gcUKLQ7uTJaE1PitM_37KR881UMEs0Rk5PMkYzMTJTWVA0V1hUVTRLUUMyNS4u)!* 🚀
-
 # NGINX Service Mesh
 
----
-
-## Support
-
-Thank you for your interest in NGINX Service Mesh (NSM). NSM is currently
-available to download via downloads.f5.com, under the NGINX Product Family.
+Thank you for your interest in NGINX Service Mesh. NGINX Service Mesh can be installed via helm charts, or by [downloading nginx-meshctl](https://downloads.f5.com/esd/product.jsp?sw=NGINX-Public&pro=NGINX_Service_Mesh), under the NGINX Product Family.
 
 ### Resources
 
 - [Product Details](https://www.nginx.com/products/nginx-service-mesh/)
-- [Download NSM](https://downloads.f5.com/esd/product.jsp?sw=NGINX-Public&pro=NGINX_Service_Mesh)
-- [NSM Documentation](https://docs.nginx.com/nginx-service-mesh)
+- [NGINX Service Mesh Documentation](https://docs.nginx.com/nginx-service-mesh)
 - [NGINX Plus Kubernetes Ingress Controller](https://www.nginx.com/products/nginx-ingress-controller/)
 - [NGINX Plus Product Details](https://www.nginx.com/products/nginx/)
 
+### Commercial Support
+
+For paid customers of NGINX Service Mesh, commercial support is available at the [NGINX Support](https://www.nginx.com/support/) website.
+
 ### Git Issues
 
-For NSM support or issues not addressed by documentation, please reach out
-via the issues tab, [NSM Git Issues](https://github.com/nginxinc/nginx-service-mesh/issues).
+For NGINX Service Mesh support or issues not addressed by documentation, you can reach out via the [Issues tab](https://github.com/nginxinc/nginx-service-mesh/issues).
+
+We use issues for bug reports and to discuss new features. Creating issues is good, creating good issues is even better. Filing meaningful bug reports with lots of information in them helps us figure out what to fix when and how it impacts our users. We like bugs because it means people are using our code, and we like fixing them even more. 
 
-We use issues for bug reports and to discuss new features.
-Creating issues is good, creating good issues is even better.
-Filing meaningful bug reports with lots of information in them helps us
-figure out what to fix when and how it impacts our users. We like bugs
-because it means people are using our code, and we like fixing them even
-more. Please follow these guidelines for filing issues:
+All issues should follow these guidelines:
 
-- Describe the problem. Include version of k8s, `nginx-meshctl version`, and what K8s platform. 
+- Describe the problem. Include version of Kubernetes, `nginx-meshctl version`, and what Kubernetes platform.
 - Include detailed information about how to recreate the issue.
 - Include relevant configurations, error messages, and logs.
-- Sanitize the data. For example, be mindful of IPs, ports, application names, and URLs
-
-## NOTE
-
-Support for NSM is not currently available via traditional NGINX or F5
-support channels. All support is through the community at [NSM Git
-Issues](https://github.com/nginxinc/nginx-service-mesh/issues).
+- Sanitize the data. For example, be mindful of IPs, ports, application names, and URLs.
 
-## NGINX Plus KIC Support
+### NGINX Plus Kubernetes Ingress Controller Support
 
-If you are using NSM with NGINX Plus Ingress Controller for Kubernetes, you can get support through your usual channels.
+If you are using NGINX Service Mesh with NGINX Plus Ingress Controller for Kubernetes, you can get support through your usual channels.
 
 Existing NGINX and F5 customers can reach out to their account team(s) for help and support with NGINX Service Mesh.