From 20f63c13c2d0846ef3ad81b96dc14e1a28201fde Mon Sep 17 00:00:00 2001
From: hal-ey <85878071+hal-ey@users.noreply.github.com>
Date: Thu, 27 Jul 2023 09:31:41 +0200
Subject: [PATCH] Avoid future tense ("will")

The future tense is not needed here, because the described behavior is always valid. This is also a guideline at SAP.
---
 .../using-sap-private-link-service/azure-cosmos-db-663ed56.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/using-sap-private-link-service/azure-cosmos-db-663ed56.md b/docs/using-sap-private-link-service/azure-cosmos-db-663ed56.md
index 214ade2..9734f4c 100644
--- a/docs/using-sap-private-link-service/azure-cosmos-db-663ed56.md
+++ b/docs/using-sap-private-link-service/azure-cosmos-db-663ed56.md
@@ -164,8 +164,8 @@ Object containing DNS entries to connect to the regional endpoints of the Cosmos
 
 ## Known Limitations
 
--   If a region is removed from the Cosmos DB with an existing private endpoint, the regional endpoint of this region will no longer work. However, the existing endpoints \(global and in other regions\) will continue to work.
--   If an additional region is added to a Cosmos DB, the endpoint for the new region will not automatically become available on the private endpoint. To make the endpoint of the additional region available, a new service instance must be created.
+-   If a region is removed from the Cosmos DB with an existing private endpoint, the regional endpoint of this region no longer works. However, the existing endpoints \(global and in other regions\) continues to work.
+-   If an additional region is added to a Cosmos DB, the endpoint for the new region does not automatically become available on the private endpoint. To make the endpoint of the additional region available, a new service instance must be created.