AWS neptune-analytics documentation change
Summary
Fixed typos and improved parameter documentation clarity; standardized performance warnings
Security assessment
Changes include typo corrections, parameter description improvements, and consistent performance warnings without security-specific context.
Diff
diff --git a/neptune-analytics/latest/userguide/egonet.md b/neptune-analytics/latest/userguide/egonet.md index 08dbb72ec..acdcf744d 100644 --- a//neptune-analytics/latest/userguide/egonet.md +++ b//neptune-analytics/latest/userguide/egonet.md @@ -20 +20 @@ For each hop, the algorithm gets the `topK` (K is specified per hop by the user - perHopMaxNeighbor: [list of the max number of top neighor vertices at each hop (required)], + perHopMaxNeighbor: [list of the max number of top neighbor vertices at each hop (required)], @@ -77 +77 @@ The direction of edge to follow at each hop. It should have the same size as the -This determines whether the edges having the maximum weights or the minimum weight will be included in the EgoNet adhering the `perHopMaxNeigbor` limits. A `min` value indicates that the edge with minimum weights will be included in the EgoNet, whereas a `max` value indicates that the edge with maximum weights will be included in the EgoNet. +This determines whether the edges having the maximum weights or the minimum weight will be included in the EgoNet adhering the `perHopMaxNeighbor` limits. A `min` value indicates that the edge with minimum weights will be included in the EgoNet, whereas a `max` value indicates that the edge with maximum weights will be included in the EgoNet. @@ -103 +103 @@ The .egonet algorithm returns: -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: @@ -140 +140 @@ This is a query integration example, where `.egonet` follows a `MATCH` clause an -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.