Skip to content

Commit 36526a6

Browse files
authored
Merge pull request #270868 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 8c9f822 + fa211e1 commit 36526a6

File tree

5 files changed

+8
-8
lines changed

5 files changed

+8
-8
lines changed

articles/cosmos-db/nosql/javascript-query-api.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -32,20 +32,20 @@ In addition to issuing queries using the API for NoSQL in Azure Cosmos DB, the [
3232

3333
When included inside predicate and/or selector functions, the following JavaScript constructs get automatically optimized to run directly on Azure Cosmos DB indices:
3434

35-
- Simple operators: `=` `+` `-` `*` `/` `%` `|` `^` `&` `==` `!=` `===` `!===` `<` `>` `<=` `>=` `||` `&&` `<<` `>>` `>>>!` `~`
36-
- Literals, including the object literal: {}
35+
- Simple operators: `=` `+` `-` `*` `/` `%` `|` `^` `&` `==` `!=` `===` `!==` `<` `>` `<=` `>=` `||` `&&` `<<` `>>` `>>>` `~`
36+
- Literals, including the object literal: `{}`
3737
- var, return
3838

3939
The following JavaScript constructs do not get optimized for Azure Cosmos DB indices:
4040

41-
- Control flow (for example, if, for, while)
41+
- Control flow: `if` `for` `while`
4242
- Function calls
4343

4444
For more information, see the [Azure Cosmos DB Server Side JavaScript Documentation](https://github.com/Azure/azure-cosmosdb-js-server/).
4545

4646
## SQL to JavaScript cheat sheet
4747

48-
The following table presents various SQL queries and the corresponding JavaScript queries. As with SQL queries, properties (for example, item.id) are case-sensitive.
48+
The following table presents various SQL queries and the corresponding JavaScript queries. As with SQL queries, properties (for example, `item.id`) are case-sensitive.
4949

5050
> [!NOTE]
5151
> `__` (double-underscore) is an alias to `getContext().getCollection()` when using the JavaScript query API.

articles/cosmos-db/nosql/quickstart-python.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ The client library is available through the Python Package Index, as the `azure-
7777
| --- | --- |
7878
| [`CosmosClient`](/python/api/azure-cosmos/azure.cosmos.cosmos_client.cosmosclient) | This class is the primary client class and is used to manage account-wide metadata or databases. |
7979
| [`DatabaseProxy`](/python/api/azure-cosmos/azure.cosmos.database.databaseproxy) | This class represents a database within the account. |
80-
| [`CotnainerProxy`](/python/api/azure-cosmos/azure.cosmos.container.containerproxy) | This class is primarily used to perform read, update, and delete operations on either the container or the items stored within the container. |
80+
| [`ContainerProxy`](/python/api/azure-cosmos/azure.cosmos.container.containerproxy) | This class is primarily used to perform read, update, and delete operations on either the container or the items stored within the container. |
8181
| [`PartitionKey`](/python/api/azure-cosmos/azure.cosmos.partition_key.partitionkey) | This class represents a logical partition key. This class is required for many common operations and queries. |
8282

8383
## Code examples

articles/expressroute/metro.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The following diagram allows for a comparison between the standard ExpressRoute
4545
| Metro location | Peering locations | Location address | Zone | Local Azure Region | ER Direct | Service Provider |
4646
|--|--|--|--|--|--|--|
4747
| Amsterdam Metro | Amsterdam<br>Amsterdam2 | Equinix AM5<br>Digital Reality AMS8 | 1 | West Europe | &check; | Megaport<br>Equinix<sup>1</sup><br>Colt<sup>1</sup><br>Console Connect<sup>1</sup><br>Digital Reality<sup>1</sup> |
48-
| Singapore Metro | Singapore<br>Singapore2 | Equinix SG1<br>Global Switch Tai Seng | 2 | West Europe | &check; | Megaport<sup>1</sup><br>Equinix<sup>1</sup><br>Console Connect<sup>1</sup> |
48+
| Singapore Metro | Singapore<br>Singapore2 | Equinix SG1<br>Global Switch Tai Seng | 2 | Southeast Asia | &check; | Megaport<sup>1</sup><br>Equinix<sup>1</sup><br>Console Connect<sup>1</sup> |
4949
| Zurich Metro | Zurich<br>Zurich2 | Interxion ZUR2<br>Equinix ZH5 | 1 | Switzerland North | &check; | Colt<sup>1</sup><br>Digital Reality<sup>1</sup> |
5050

5151
<sup>1<sup> These service providers will be available in the future.

articles/virtual-machines/workloads/oracle/oracle-database-backup-strategies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ The ability to access backup storage across regions is an important aspect of bu
6767

6868
When you're using Azure Files with either the Server Message Block (SMB) protocol or the Network File System (NFS) 4.1 protocol to mount as backup storage, Azure Files doesn't support RA-GRS or RA-GZRS.
6969

70-
If the backup storage requirement is greater than 5 tebibytes (TiB), Azure Files requires you to enable the [large file shares](../../../storage/files/storage-files-planning.md) feature. This feature doesn't support GRS or GZRS redundancy. It supports only LRS.
70+
Azure Files backup storage can scale up to 100 (TiB), with support for LRS, GRS, and GZRS redundancy options.
7171

7272
Azure Blob Storage mounted via the NFS 3.0 protocol currently supports only LRS and ZRS redundancy. Azure Blob Storage configured with any redundancy option can be mounted via Blobfuse.
7373

articles/virtual-network/ip-services/default-outbound-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.custom:
1717

1818
In Azure, virtual machines created in a virtual network without explicit outbound connectivity defined are assigned a default outbound public IP address. This IP address enables outbound connectivity from the resources to the Internet. This access is referred to as default outbound access.
1919

20-
Examples of explicit outbound connectivity are virtual machines:
20+
Examples of explicit outbound connectivity for virtual machines are:
2121

2222
* Created within a subnet associated to a NAT gateway.
2323

0 commit comments

Comments
 (0)