AWS neptune-analytics documentation change
Summary
Fixed terminology inconsistencies ('common neighbors' → 'total unique neighbors'), corrected algorithm spelling, and updated performance warning phrasing
Security assessment
Changes improve documentation accuracy and consistency. No security-related content added or modified.
Diff
diff --git a/neptune-analytics/latest/userguide/total-neighbors.md b/neptune-analytics/latest/userguide/total-neighbors.md index 47af84d1b..3e167a655 100644 --- a//neptune-analytics/latest/userguide/total-neighbors.md +++ b//neptune-analytics/latest/userguide/total-neighbors.md @@ -9 +9 @@ SyntaxInputsOutputsIntegration exampleSample output -Total neighbors is an algoithm that counts the total number of unique neighbors of two input vertices, which is the union of the neighborhoods of those vertices. +Total neighbors is an algorithm that counts the total number of unique neighbors of two input vertices, which is the union of the neighborhoods of those vertices. @@ -30 +30 @@ Total neighbors is an algoithm that counts the total number of unique neighbors -One or more nodes of which to find the common neighbors with the corresponding second nodes. +One or more nodes of which to find the total unique neighbors with the corresponding second nodes. @@ -34 +34 @@ One or more nodes of which to find the common neighbors with the corresponding s -One or more nodes of which to find the common neighbors with the corresponding first nodes. +One or more nodes of which to find the total unique neighbors with the corresponding first nodes. @@ -72 +72 @@ This example returns a row for each combination of a US airport and a UK airport -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.