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

Syntax error here

I think many people are struggling with this node, an example such as "old position on displaced geometry" could help - even though it clutters the tooltip.

I am not sure about this tooltip, my English is okay (although I am by no means a native), and I am not sure I would understand this tooltip without knowing the node functionality beforehand. IMO sometimes it is better to resort to the more simple/common/obvious terms.

I usually use "Generate" instead of "Make".

Sample values from an image texture

• I don't think there is a need to mention pixels.

The term "Traveling" seems a little bit strange in this context, but I don't know, does it common to use it as a substitute for Tangent? Maybe using something like "The curve's flow" would sound better.

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

• As you said, true sounds like function doc-string

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

• Is there a reason to mention fog?

I don't know, why is it useful?

I think "island" works better than "split".

Yeah, this is probably a good node for a brief example like that. What about something like this?

Store the result of a field on a geometry and output the data as a node socket. Allows remembering or interpolating data as the geometry changes, such as positions before deformation

Hmm, fair enough. How about something like Convert curves into a mesh, optionally with a custom shape defined by profile curves?

Yeah, good call

How about even simpler? Retrieve the direction of curves at each control point

Yeah, good catch

Yes, as opposed to an SDF volume-- we're planning on adding more nodes for those in the future

I think it might not be clear that you're responsible for positioning all of the points yourself otherwise

Yeah, it might! And it would be consistent with the pack islands description too

That's fine, maybe sweeping the order would be better:

Convert curves into a mesh, optionally with a custom profile shape defined by curves

Sound good, but shouldn't it be "Spline" instead of "curves" I mean, curves don't really have a direction.
Retrieve the direction of the spline at each control point

Fair enough, but if so, should we add the same clarification to Duplicate Element as well?

That sounds great!

The distinction between splines and curves is really vague, I think each has a direction just as much as the other. We've been moving towards "Curves" naming recently because of that meaningless difference, I'd prefer to stick to that. It matches up with the node name too anyway.

I guess we could add "at the same location" to the end?

Do you mean, keeping the "point node" the same and adding "at the same location" just for the "duplicate element"?
Point: Generate a point cloud with positions and radii defined by fields
Duplicate: Generate an arbitrary number of copies at the same location for each selected input element
Well, I am actually okay with keeping the duplicate node as is, what do you think?

I'm okay with keeping it the same too. I tried rearranging the duplicate tooltip a bit but didn't find something better