v.build.polylines: Fix typo in the manual

git-svn-id: https://svn.osgeo.org/grass/grass/trunk@70591 15284696-431f-4ddb-bdfa-cd5b030d7da7

vector/v.build.polylines/v.build.polylines.html

@@ -4,11 +4,11 @@
 boundaries in a vector map.
 
 <p>A line is defined by one start node, one end node and any number of
-vertices between the start and end node. The shortest possible line
+vertices between the start and end nodes. The shortest possible line
 consists of only two vertices where the coordinates of the start and end
-node are identical to those of the two vertices.
+nodes are identical to those of the two vertices.
 
-<p><em>v.build.polyline</em> picks a line and from its start node, walks
+<p><em>v.build.polylines</em> picks a line and from its start node, walks
 back as long as exactly one other line of the same type is connected to
 this node. Line directions are reversed as required, i.e. it does not
 matter if the next line is connected to the current node by its start or
@@ -23,12 +23,12 @@ either <em><a href="v.edit.html">v.edit</a></em> or
 the <em><a href="wxGUI.vdigit.html">wxGUI vector
 digitizer</a></em>.
 
-<p>Polylines provide the most appropriate representation of curved lines when it 
-is important that nodes serve to define topology rather than geometry. Curved 
-lines are usually digitized as polylines, but these are sometimes broken into 
-their constituent straight line segments during conversion from one data 
-format to another. <em>v.build.polylines</em> can be used to rebuild such broken 
-polylines. 
+<p>Polylines provide the most appropriate representation of curved lines when
+it is important that nodes serve to define topology rather than geometry.
+Curved lines are usually digitized as polylines, but these are sometimes broken
+into their constituent straight line segments during conversion from one data
+format to another. <em>v.build.polylines</em> can be used to rebuild such
+broken polylines. 
 
 <h2>NOTES</h2>