AWS neptune-analytics documentation change
Summary
Corrected grammar in query performance warning
Security assessment
Typo fix in a performance warning does not relate to security issues or documentation.
Diff
diff --git a/neptune-analytics/latest/userguide/bfs-levels.md b/neptune-analytics/latest/userguide/bfs-levels.md index a55bd04b9..20520af47 100644 --- a//neptune-analytics/latest/userguide/bfs-levels.md +++ b//neptune-analytics/latest/userguide/bfs-levels.md @@ -142 +142 @@ This query illustrates various ways to constrain the input and output: -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.