AWS neptune-analytics documentation change
Summary
Improved warning about unrestricted MATCH(n) clauses by adding missing 'in' (from 'result a' to 'result in a')
Security assessment
Consistent with other files, this change emphasizes query performance rather than security protections. No mention of security controls or vulnerabilities addressed.
Diff
diff --git a/neptune-analytics/latest/userguide/degree.md b/neptune-analytics/latest/userguide/degree.md index 86010b25c..49d6d28d0 100644 --- a//neptune-analytics/latest/userguide/degree.md +++ b//neptune-analytics/latest/userguide/degree.md @@ -134 +134 @@ This is an example of multiple `.degree` invocations chained together, where the -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.