AWS neptune-analytics documentation change
Summary
Fixed typo in example description and grammatical error in MATCH clause warning
Security assessment
Changes are editorial (typo fixes and grammar) with no evidence of addressing security vulnerabilities or documenting security features.
Diff
diff --git a/neptune-analytics/latest/userguide/overlap-similarity.md b/neptune-analytics/latest/userguide/overlap-similarity.md index bf6606d95..ad46c852e 100644 --- a//neptune-analytics/latest/userguide/overlap-similarity.md +++ b//neptune-analytics/latest/userguide/overlap-similarity.md @@ -63 +63 @@ If either input node list is empty, the output is empty. -This is a query integration examples, where `.overlapSimilarity` takes its input node lists from the output of a `MATCH` clause: +This is a query integration example, where `.overlapSimilarity` takes its input node lists from the output of a `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.