AWS neptune-analytics documentation change
Summary
Fixed grammar ('result a' to 'result in') in warning about unrestricted MATCH(n) usage.
Security assessment
Grammar correction in performance-related documentation. No evidence of security vulnerability fixes or security feature additions.
Diff
diff --git a/neptune-analytics/latest/userguide/sssp-deltaStepping-parents.md b/neptune-analytics/latest/userguide/sssp-deltaStepping-parents.md index d1f6db48f..822d9eece 100644 --- a//neptune-analytics/latest/userguide/sssp-deltaStepping-parents.md +++ b//neptune-analytics/latest/userguide/sssp-deltaStepping-parents.md @@ -136 +136 @@ This is a query integration example, where where `.sssp.deltaStepping.parents` f -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.