Merge pull request #45992 from southpolesteve/patch-9

Clarify note on ORDER BY on undefined values

Author: ktoliver

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

@@ -47,7 +47,7 @@ ORDER BY <sort_specification>
    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.
+> If the properties being sorted against might be undefined for some documents and you want to retrieve them in an ORDER BY query, you must explicitly create an index on those properties. The default indexing policy won't allow for the retrieval of the documents where the sort property is undefined.
 
 ## Examples