Skip to content

Commit 7869b9d

Browse files
committed
fix
1 parent a215066 commit 7869b9d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-cache-for-redis/cache-troubleshoot-connectivity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ If you have a firewall configured for your Azure Redis cache, ensure that your c
7373

7474
#### Third-party firewall or external proxy
7575

76-
If you use a third-party firewall or proxy in your network, make sure they it allows the Azure Cache for Redis endpoint `*.redis.cache.windows.net` and the ports `6379` and `6380`. You might need to allow more ports when you use a clustered cache or geo-replication.
76+
If you use a third-party firewall or proxy in your network, make sure it allows the Azure Cache for Redis endpoint `*.redis.cache.windows.net` and the ports `6379` and `6380`. You might need to allow more ports when you use a clustered cache or geo-replication.
7777

7878
### Private endpoint configuration
7979

@@ -118,7 +118,7 @@ To configure your virtual network effectively and avoid geo-replication issues,
118118

119119
While it's possible to use virtual network injection with Premium caches, it's preferable to use Azure Private Link. For more information, see:
120120

121-
- [Migrate from VNet injection caches to Private Link caches](cache-vnet-migration.md)
121+
- [Migrate from `VNet` injection caches to Private Link caches](cache-vnet-migration.md)
122122
- [What is Azure Cache for Redis with Azure Private Link?](cache-private-link.md)
123123

124124
## Related content

0 commit comments

Comments
 (0)