AWS neptune-analytics documentation change
Summary
Fixed typo ('ia' → 'is') and corrected same performance warning phrasing as in sssp-deltaStepping.md
Security assessment
Minor grammatical correction and consistent performance warning update. No security context or vulnerabilities addressed.
Diff
diff --git a/neptune-analytics/latest/userguide/topk-sssp.md b/neptune-analytics/latest/userguide/topk-sssp.md index 5e44fe93e..be5fe4875 100644 --- a//neptune-analytics/latest/userguide/topk-sssp.md +++ b//neptune-analytics/latest/userguide/topk-sssp.md @@ -97 +97 @@ For every node that can be reached from the specified source list, the algorithm -This ia a standalone query, where the source node list is explicitly provided in the query: +This is a standalone query, where the source node list is explicitly provided in the query: @@ -130 +130 @@ This is a query integration example, where `.topksssp` follows a `MATCH` clause -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.