AWS neptune-analytics documentation change
Summary
Fixed grammar in performance warning ('result a' to 'result in') when using unrestricted MATCH(n) clauses.
Security assessment
The change improves clarity of a performance warning but does not address security vulnerabilities or document security features. Focuses on query optimization best practices.
Diff
diff --git a/neptune-analytics/latest/userguide/sssp-bellmanFord-parents.md b/neptune-analytics/latest/userguide/sssp-bellmanFord-parents.md index a1171383e..146cad72a 100644 --- a//neptune-analytics/latest/userguide/sssp-bellmanFord-parents.md +++ b//neptune-analytics/latest/userguide/sssp-bellmanFord-parents.md @@ -131 +131 @@ This is a query integration example, where where `.sssp.bellmanFord.parents` fol -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.