Merge pull request #303280 from flang-msft/fxl---correct-port-details

Fxl---correct port details--ado-- BUG 33917167

Author: denrea

articles/redis/migrate/migrate-overview.md

@@ -54,8 +54,8 @@ Here are some other differences that aren't covered by the previous mapping. Con
 | DNS suffix (only for PROD cloud) | `.redis.cache.windows.net` | `<region>.redis.azure.net`                    |
 | TLS port                         | 6380                       | 10000                                         |
 | Non-TLS port                     | 6379                       | Not supported                                 |
-| Individual node TLS ports        | 130XX                      | 85xx                                          |
-| Individual node non-TLS port     | 150XX                      | Not supported                                 |
+| Individual node TLS ports        | 13XXX                      | 85xx                                          |
+| Individual node non-TLS port     | 15XXX                      | Not supported                                 |
 | Clustering support               | OSS clustering mode        | OSS and Enterprise cluster modes              |
 | Unsupported commands             | Unsupported commands       | Multi-key commands                            |
 | Regional availability            | All Azure regions          | * See the list of regions after this section. |

articles/redis/overview.md

@@ -117,7 +117,7 @@ The following table helps describe some of the features supported by tier:
 
 ### Other considerations when picking a tier
 
-- **Network performance**: If you have a workload that requires high throughput, network bandwidth might cause a bottleneck. You can increase bandwidth by moving up to a higher performance tier or by moving to a large instance size. Larger size instances have more bandwidth because of the underlying VM that hosts the cache. Higher bandwidth limits help you avoid network saturation that cause time-outs in your application. For more information on bandwidth performance, see [Performance testing](best-practices-performance.md)
+- **Network performance**: If you have a workload that requires high throughput, network bandwidth might cause a bottleneck. You can increase bandwidth by moving up to a higher performance tier or by moving to a large instance size. Larger size instances have more bandwidth because of the underlying VM that hosts the cache. Higher bandwidth limits help you avoid network saturation that causes timeouts in your application. For more information on bandwidth performance, see [Performance testing](best-practices-performance.md)
 - **Maximum number of client connections**: Each SKU has a maximum number of client connections. This limit increases with higher performance tiers and larger instances sizes. The following table shows the maximum client connections allowed per Azure Managed Redis SKU.