AWS neptune-analytics documentation change
Summary
Formatting adjustments for `vertexLabels` parameter documentation, including example syntax and rephrased filtering explanation.
Security assessment
Changes involve syntax formatting and clarification of vertex filtering behavior. No security-related context or vulnerabilities addressed.
Diff
diff --git a/neptune-analytics/latest/userguide/louvain.md b/neptune-analytics/latest/userguide/louvain.md index 18ebc9ca3..b04ceca84 100644 --- a//neptune-analytics/latest/userguide/louvain.md +++ b//neptune-analytics/latest/userguide/louvain.md @@ -82 +82 @@ The node or nodes for which the algorithm will return the computed community ids - * **vertexLabels** _(optional)_ – _type:_ `a list of vertex label strings; example ["airport", ...]`; _default: no vertex filtering_. + * **vertexLabels** _(optional)_ – _type:_ a list of vertex label strings; _example:_ `["airport", `...`]`; _default:_ no vertex filtering. @@ -84 +84 @@ The node or nodes for which the algorithm will return the computed community ids -Node labels for node filtering. To filter on one or more vertex labels, provide a list of node labels. Vertices matching any label in the vertexLabels list are the only vertices that are passed to the algorithm computation. If no vertexLabels field is provided then all vertices are passed to the Louvain algorithm. +To filter on one more vertex labels, provide a list of the ones to filter on. If no `vertexLabels` field is provided then all vertex labels are processed during traversal.