Calculate statistics about a data set from a field evaluated on a geometry

• Just simpler phrasing

Calculate the limits of a geometry's positions and generate a box mesh with those dimensions

• Mention the calculation before the mesh, since the mesh doesn't have to be used

Store the result of a field on a geometry and output the data as a node socket, in order to interpolate the data later as the geometry changes

• Phrase it as a single sentence

Retrieve geometry from a collection

• Since it just has one geometry output

Create a mesh that encloses all points in the input geometry with the smallest number of points

• Grammar
• Try to describe the goal of the convex hull a bit more

Provide a selection for an arbitrary number of endpoints in each spline

• No need for "in a curve" at the end

Provide a selection based on the handle types of Bezier control points

• There is no "the" at this point

Generate a poly spline line with two points

• "Two points" might help someone

Change the type of curves

• Simpler and says the same thing AFAICS

Create a mesh from curves by sweeping a profile curve along another

• I think mentioning "sweeping" is helpful since it's a different way of describing it
• Phrase it as a single sentence

Generate a point cloud by sampling positions along curves

• A bit more specific

Translate and rotate curves based on the changes between the object's original and evaluated surface mesh

Remove the selected elements of a geometry

• There can be multiple "parts"
• "Element" is the standard word for this

Make an arbitrary number copies of each selected input element

• More correct, more specific

Generate points spread out on the surface of the input mesh

• No need to mention attribute interpolation, that is standard in most nodes
• Phrased a bit more consistently

Add the values of an evaluated field together and output the running total for each element

• Simpler, reads less like the manual

Generate new vertices, edges, or faces from selected elements and move them based on an offset while keeping them connected by their boundary

• "The selected elements" -> "selected elements"
• "Transform -> "move"

Retrieve the value of a field on a different domain besides the domain from the context

• No need to mention domain interpolation, that happens everywhere and it's so helpful here

Generate a mesh on the XY plane with faces on the inside of input curves

• The triangulation is a bit misleading when there is an N-gon output
• Mention the XY plane, since people have been confused about that before

Round corners by generating circular arcs on each control point

• Skip mentioning the bevel modifier, since Bevel is a bit different

Reverse the order of the vertices and edges of each selected face, flipping its normal direction

• Just a single sentence

Convert each input geometry into an instance, which can be much faster than the Join Geometry node when the inputs are large

• A single sentence again

Sample values from the pixels of an image texture

• Phrase it like an action

Retrieve the data of a specified attribute

• "data" -> "the data"

Retrieve the position of each Bézier control point's handles

• Each control point has handles, not each spline

Retrieve the angle at each control point used to twist the curve's normal around its tangent

• "turn" -> "twist"
• Somewhat simpler phrasing

Retrieve a stable random identifier value from the \"id\" attribute on the point domain, or the index if the attribute does not exist

• Clearer wording

Retrieve the rotation of each instance in the geometry

• avoid somewhat internal "component" name

Retrieve the scale of each instance in the geometry

• scale shouldn't be capitalized
• avoid somewhat internal "component" name

Retrieve the index of the material used for each element in the geometry's list of materials

• Simpler wording
• "Index" instead of "which"

Output a single material

• The usage hint doesn't add too much IMO, there isn't much to explain for such a simple input node IMO

Calculate the surface area of each face in a mesh

• Makes it clearer that it's not the total surface area

Retrieve whether all triangles in a face are on the same plane-- in other words, whether have the same normal

• Simplify wording
• I think a -- is more correct than a comma here

Retrieve information about separate contiguous regions of a mesh

• Trying to avoid having "separate" and "connected" right next to each other which seems confusing

Retrieve a unit length vector indicating the direction pointing away from the geometry at each element

• Has to work for curves and meshes
• Normals are potentially stored on all four domains

Retrieve a vector indicating the location of each element

• "Evaluated" isn't right
• Use a word besides "position" in the description, just to be consistent about trying not to just repeat the node name in the description

Retrieve the radius at each point on curve or point cloud geometry

• "evaluated" isn't meaningful here
• "used to define specific properties" isn't useful enough to include

Retrieve whether each face is marked for smooth shading

• Avoid "retrieve true" which sounds like a function doc-string
• Simplify wording

Retrieve whether each spline endpoint connects to the beginning

• Avoid "return true" like above
• Avoid using the name of the node in its description

Retrieve the total length of each spline, as a distance or as a number of points

• Remove superfluous comma

Retrieve the number of evaluated points that will be generated for every control point on curves

• "The spline" has no meaning here, since "the" doesn't refer to anything specific
• "curve" is unnecessary earlier in the sentence, that information is obvious here IMO

Retrieve the direction that the curve is traveling at each control point

• "Depending on the direction" seemed redundant with the first part of the description to me
• Add "traveling", since I think it's a bit more specific than "points"

Retrieve true if the nodes are being evaluated for the viewport rather than the final render

• Combine the second sentence into a "rather" clause, which makes the whole thing shorter and simpler

Provide a selection of faces that use the specified material

• "of faces" is simpler and clearer than "for meshes"

Merge vertices or points within a given distance

• "by distance" is the name of the node, but it didn't really make sense in a sentence

Cut, subtract, or join multiple mesh inputs

• "mesh" rather than "geometry" to be more specific
• "multiple" is more correct than "two"

Generate vertices in a line and connect them with edges

• Verb conjugation

Generate a spherical mesh with quads, except for triangles at the top and bottom

• Remove some extra words

Generate a point cloud from a mesh's vertices

• "Vertices" separates it from some other nodes

Create a fog volume with the shape of the input mesh's surface

Retrieve information from an object

• Only one object

Generate a point cloud with positions and radii defined by fields

• Maybe the extra information is helpful

Generate a mesh vertex for each point cloud point

• Add "mesh" for some more context

Cast rays from the context geometry onto a target geometry, and retrieve information from each hit point

• Removing "various" makes it read easier IMO

Delete an attribute with a specified name from a geometry. Typically used to optimize performance

• Works a bit better with the verb-like wording for the rest of the descriptions that don't make the node the subject

Change the direction of the curve by swapping each spline's start and end data

• Makes it clear that it applies to all data

Retrieve data from a point on a curve at a certain distance from its start

• Just removing a few extra words

Set the radius of the curve at each control point

• No need to repeat "curve"

Set the id attribute on the input geometry, mainly used internally for randomizing

• unnecessary capital

Set the material index for each selected geometry element

• A geometry has more than one material index

Assign a material to geometry elements

• Before the node is added, there is no "the material" or "the selection', it's just hypothetical
• "Assign" is less misleading IMO, since the material is assigned indirectly through indices (at least for meshes)

Set display size of point cloud points

• The radius is used in renders as well as the viewport, and even in other places in the future
• I'm not sure it's necessary to mention the selection since almost all nodes have selection

Control the smoothness of mesh normals around each face by changing the \"shade smooth\" attribute

• "Shade Smooth" -> "shade_smooth"
• Use just one sentence
• Mention that it's the normals that are affected
• It's behavior of other things too, not just how they look in the viewport or renders

Control whether each spline loops back on itself by changing the \"cyclic\" attribute

• Similar changes to above

Control how many evaluated points should be generated on every curve segment

• "Set" -> "Control" just seems a bit simpler, plus it's a different word
• Technically it's every segment, rather than every control point

Duplicate mesh edges and break connections with the surrounding faces

• Simpler wording, avoid repeating "split"

Generate a paragraph of text with a specific font, using curve instances to store each character

• Add helpful information
• Specifically mention "font", since it's important to how the shape of the result curves is chosen

Dividing each curve segment into a specified number of pieces

• Phrase it as if it was changing existing curves rather than generating new ones, which is how it works on the user level
• Explain what we're dividing the segments into

Divide mesh faces into smaller ones without changing the shape or volume, using linear interpolation to place the new vertices

• This is just a bit more specific and solves the "faces / number" unit problem

Divide mesh faces to form a smooth surface, using the Catmull-Clark subdivision method

• Similar to above
• Mentioning the subdivision level isn't fundamental to describing what the node does IMO, it's just one of the inputs

Switch between two inputs

• Grammar, "input" should be plural

Translate, rotate or scale the geometry

• Just to be a bit more specific

Shorten curves by removing portions at the start or end

• I think just mentioning "curves" is fine here, it's clear enough
• "Portions" instead of "sections" gives a small hint to how the portion is described (e.g. a portion of the total length)

Generate a dense volume with a density field that controls the density at each grid voxel based on its position

• Hint that the position node can be used in the input field
• Avoid repeating "volume cube"
• Use "controls" or "sets" like above

'surfac' -> \"surface\"\

Scale islands of a UV map and move them so they fill the UV space as much as possible

Generate a UV map split based on seam edges

• Not sure, but something like that should work

Retrieve the number of elements in a geometry for each attribute domain

• "number of elements" is more specific than "size"
• "a geometry" instead of "the geometry"

Syntax error here