AWS neptune-analytics documentation change
Summary
Fixed grammar in performance warning ('result a' to 'result in') for MATCH(n) clause usage.
Security assessment
Minor language correction in query optimization advice. Lacks security-specific context or new security documentation.
Diff
diff --git a/neptune-analytics/latest/userguide/sssp-bellmanFord.md b/neptune-analytics/latest/userguide/sssp-bellmanFord.md index d45675834..b9a3f1216 100644 --- a//neptune-analytics/latest/userguide/sssp-bellmanFord.md +++ b//neptune-analytics/latest/userguide/sssp-bellmanFord.md @@ -129 +129 @@ This is a query integration example, where `.sssp.bellmanFord` follows a `MATCH` -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.