Update vectordistance.md

Author: jcodella

articles/cosmos-db/nosql/query/vectordistance.md

@@ -69,7 +69,7 @@ ORDER BY VectorDistance(c.vector1, c.vector2)
 - This function requires enrollment in the [Azure Cosmos DB NoSQL Vector Search preview feature](../vector-search.md#enroll-in-the-vector-search-preview-feature).
 - This function benefits from a [vector index](../../index-policy.md#vector-indexes)
 - if `false` is given as the optional `bool_expr`, then the vector index defined on the path is used, if one exists. If no index is defined on the vector path, then this reverts to full scan and incurs higher RU charges and higher latency than if using a vector index. 
-- When `VectorDistance` is used in an `ORDER BY` clause, no direction can be specified for the `ORDER BY`, as the results are always sorted in order of most similar (first) to least similar (last) based on the similarity metric used. If a direction such as `ASC` or `DESC` is specified, an error occurs. 
+- When `VectorDistance` is used in an `ORDER BY` clause, no direction needs to be specified for the `ORDER BY` as the results are always sorted in order of most similar (first) to least similar (last) based on the similarity metric used.
 - The result is expressed as a similarity score.
 
 ## Related content