Merge pull request #99559 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)

Author: huypub

articles/cosmos-db/how-to-use-stored-procedures-triggers-udfs.md

@@ -139,7 +139,7 @@ The following example shows how to register a stored procedure by using the Java
 ```javascript
 const container = client.database("myDatabase").container("myContainer");
 const sprocId = "spCreateToDoItem";
-await container.storedProcedures.create({
+await container.scripts.storedProcedures.create({
     id: sprocId,
     body: require(`../js/${sprocId}`)
 });
@@ -156,7 +156,7 @@ const newItem = [{
 }];
 const container = client.database("myDatabase").container("myContainer");
 const sprocId = "spCreateToDoItem";
-const {body: result} = await container.storedProcedure(sprocId).execute(newItem, {partitionKey: newItem[0].category});
+const {body: result} = await container.scripts.storedProcedure(sprocId).execute(newItem, {partitionKey: newItem[0].category});
 ```
 
 ### Stored procedures - Python SDK

articles/cosmos-db/sql-query-order-by.md

@@ -45,6 +45,9 @@ ORDER BY <sort_specification>
 ## Remarks  
 
    The ORDER BY clause requires that the indexing policy include an index for the fields being sorted. The Azure Cosmos DB query runtime supports sorting against a property name and not against computed properties. Azure Cosmos DB supports multiple ORDER BY properties. In order to run a query with multiple ORDER BY properties, you should define a [composite index](index-policy.md#composite-indexes) on the fields being sorted.
+   
+> [!Note] 
+> When using the .NET SDK 3.4.0 or above, if the properties being sorted against might be undefined for some documents then you need to explicitly create an index on those properties. The default indexing policy will not allow for the retrieval of the documents where the sort property is undefined.
 
 ## Examples