Skip to content

Commit 6d753d3

Browse files
Update how-to-multi-master.md
1 parent 249c26a commit 6d753d3

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/cosmos-db/nosql/how-to-multi-master.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ CosmosClient client = cosmosClientBuilder.Build();
7676

7777
## <a id="java4-multi-region-writes"></a> Java V4 SDK
7878

79-
To enable multi-region writes in your application, call `.multipleWriteRegionsEnabled(true)` and `.preferredRegions(preferredRegions)` in the client builder, where `preferredRegions` is a `List` containing one element. That element is the region in which the application is being deployed and where Azure Cosmos DB is replicated:
79+
To enable multi-region writes in your application, call `.multipleWriteRegionsEnabled(true)` and `.preferredRegions(preferredRegions)` in the client builder, where `preferredRegions` is a `List` of regions the data is replicated into ordered by preference - ideally the regions with shortest distance/best latency first:
8080

8181
# [Async](#tab/api-async)
8282

@@ -94,7 +94,7 @@ To enable multi-region writes in your application, call `.multipleWriteRegionsEn
9494

9595
## <a id="java2-multi-region-writes"></a> Async Java V2 SDK
9696

97-
The Java V2 SDK used the Maven [com.microsoft.azure::azure-cosmosdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-cosmosdb). To enable multi-region writes in your application, set `policy.setUsingMultipleWriteLocations(true)` and set `policy.setPreferredLocations` to the region in which the application is being deployed and where Azure Cosmos DB is replicated:
97+
The Java V2 SDK used the Maven [com.microsoft.azure::azure-cosmosdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-cosmosdb). To enable multi-region writes in your application, set `policy.setUsingMultipleWriteLocations(true)` and set `policy.setPreferredLocations` to the `List` of regions the data is replicated into ordered by preference - ideally the regions with shortest distance/best latency first:
9898

9999
```java
100100
ConnectionPolicy policy = new ConnectionPolicy();
@@ -111,7 +111,7 @@ AsyncDocumentClient client =
111111

112112
## <a id="javascript"></a>Node.js, JavaScript, and TypeScript SDKs
113113

114-
To enable multi-region writes in your application, set `connectionPolicy.UseMultipleWriteLocations` to `true`. Also, set `connectionPolicy.PreferredLocations` to the region in which the application is being deployed and where Azure Cosmos DB is replicated:
114+
To enable multi-region writes in your application, set `connectionPolicy.UseMultipleWriteLocations` to `true`. Also, set `connectionPolicy.PreferredLocations` to the regions the data is replicated into ordered by preference - ideally the regions with shortest distance/best latency first:
115115

116116
```javascript
117117
const connectionPolicy: ConnectionPolicy = new ConnectionPolicy();
@@ -128,7 +128,7 @@ const client = new CosmosClient({
128128

129129
## <a id="python"></a>Python SDK
130130

131-
To enable multi-region writes in your application, set `connection_policy.UseMultipleWriteLocations` to `true`. Also, set `connection_policy.PreferredLocations` to the region in which the application is being deployed and where Azure Cosmos DB is replicated.
131+
To enable multi-region writes in your application, set `connection_policy.UseMultipleWriteLocations` to `true`. Also, set `connection_policy.PreferredLocations` to the regions the data is replicated into ordered by preference - ideally the regions with shortest distance/best latency first.
132132

133133
```python
134134
connection_policy = documents.ConnectionPolicy()

0 commit comments

Comments
 (0)