AWS neptune-analytics documentation change
Summary
Fixed typo in example description and standardized performance warning language
Security assessment
Changes are grammatical improvements and standardization of query performance warnings, with no security implications mentioned.
Diff
diff --git a/neptune-analytics/latest/userguide/jaccard-similarity.md b/neptune-analytics/latest/userguide/jaccard-similarity.md index c03d18194..1bd45ffd7 100644 --- a//neptune-analytics/latest/userguide/jaccard-similarity.md +++ b//neptune-analytics/latest/userguide/jaccard-similarity.md @@ -63 +63 @@ If either input node list is empty, the output is empty. -The example below is a query integration examples, where the node list inputs for `.jaccardSimilarity` come from a preceding `MATCH` clause: +The example below is a query integration example, where the node list inputs for `.jaccardSimilarity` come from a preceding `MATCH` clause: @@ -89 +89 @@ Another example: -It is not good practice to use `MATCH(n)` without restriction in query integrations. Keep in mind that every node returned by the `MATCH(n)` clause invokes the algorithm once, which can result a very long-running query if a large number of nodes is returned. Use `LIMIT` or put conditions on the `MATCH` clause to restrict its output appropriately. +It is not good practice to use `MATCH(n)` without restriction in query integrations. Keep in mind that every node returned by the `MATCH(n)` clause invokes the algorithm once, which can result in a very long-running query if a large number of nodes is returned. Use `LIMIT` or put conditions on the `MATCH` clause to restrict its output appropriately.