Typos, capitalization of Fields page #93242

New Issue

Garek · 2021-11-20T16:03:07+01:00

Garek commented

2021-11-20 16:03:07 +01:00

Pagename: modeling/geometry_nodes/fields
Blender Version: 3.0
Documentation Language: en
Permanent link

Short description of error
Whar Are Fields? :
Bad: "For example, in the figure above, the field connected to the “Set Position” node depends on two inputs, position and index, and transforms them into into a vector using a single instruction."
Good: "For example, in the figure above, the field connected to the “Set Position” node depends on two inputs, Position and Index, and transforms them into a vector using a single instruction."

Not sure about this one :
Bad: "Socket shapes are used to convey which sockets are fields and which regular data"
Good: "Socket shapes are used to convey which sockets are fields and which are regular data"

Also not sure for this one , because in screenshot we see "5 m":
Bad: "Every point will be moved up by 5m."
Good: "Every point will be moved up by 5 m."

Node Types :
Bad: "Nodes can be separated into two **categories categories–**data flow nodes that usually pass around geometries, and field nodes that operate on data per-element"
Good: "Nodes can be separated into two **categories:**data flow nodes that usually pass around geometries, and field nodes that operate on data per-element"

Input Nodes :
Bad: "Examples of input nodes are the built-in attribute input nodes like position and ID, but also selection nodes like endpoint selection."
Good: "Examples of input nodes are the built-in attribute input nodes like Position and ID, but also selection nodes like Endpoint Selection."

Field Context :
Bad: "Here, the set position node’s input field is evaluated once. To evalautethe field, the node travels backwards to retrieve the inputs from the field input nodes."
Good: "Here, the Set Position node’s input field is evaluated once. To evaluatethe field, the node travels backwards to retrieve the inputs from the field input nodes."
Bad: "When a second set position node is added, the same field network is evaluated twice, once for each data flow node. At the second set position node, the results will be different since its geometry input will already have the changed position from the first node."
Good: "When a second Set Position node is added, the same field network is evaluated twice, once for each data flow node. At the second Set Position node, the results will be different since its geometry input will already have the changed position from the first node."
Bad: "Here, a capture attribute node stores a copy of the initial position. Notice that evaluating the field input of the capture attribute node is an entirely different step. Later on, the input fields to the set position nodes don’t use the actual position, but the anonymous attribute copy of it."
Good: "Here, a Capture Attribute node stores a copy of the initial position. Notice that evaluating the field input of the Capture Attribute node is an entirely different step. Later on, the input fields to the Set Position nodes don’t use the actual position, but the anonymous attribute copy of it."

Pagename: `modeling/geometry_nodes/fields` Blender Version: `3.0` Documentation Language: `en` [Permanent link ](https://docs.blender.org/manual/en/3.0/modeling/geometry_nodes/fields.html) **Short description of error** [Whar Are Fields? ](https://docs.blender.org/manual/en/3.0/modeling/geometry_nodes/fields.html#what-are-fields): Bad: "For example, in the figure above, the field connected to the “Set Position” node depends on two inputs, **p**osition and **i**ndex, and transforms them **into into** a vector using a single instruction." Good: "For example, in the figure above, the field connected to the “Set Position” node depends on two inputs, **P**osition and **I**ndex, and transforms them **into** a vector using a single instruction." Not sure about [this one ](https://docs.blender.org/manual/en/3.0/modeling/geometry_nodes/fields.html#what-are-fields): Bad: "Socket shapes are used to convey which sockets are fields and which regular data" Good: "Socket shapes are used to convey which sockets are fields and which **are** regular data" Also not sure for [this one ](https://docs.blender.org/manual/en/3.0/modeling/geometry_nodes/fields.html#id2), because in screenshot we see "5 m": Bad: "Every point will be moved up by **5m**." Good: "Every point will be moved up by **5 m**." [Node Types ](https://docs.blender.org/manual/en/3.0/modeling/geometry_nodes/fields.html#node-types): Bad: "Nodes can be separated into two **categories categories–**data flow nodes that usually pass around geometries, and field nodes that operate on data per-element" Good: "Nodes can be separated into two **categories:**data flow nodes that usually pass around geometries, and field nodes that operate on data per-element" [Input Nodes ](https://docs.blender.org/manual/en/3.0/modeling/geometry_nodes/fields.html#input-nodes): Bad: "Examples of input nodes are the built-in attribute input nodes like **p**osition and ID, but also selection nodes like **e**ndpoint **s**election." Good: "Examples of input nodes are the built-in attribute input nodes like **P**osition and ID, but also selection nodes like **E**ndpoint **S**election." [Field Context ](https://docs.blender.org/manual/en/3.0/modeling/geometry_nodes/fields.html#field-context): Bad: "Here, the **s**et **p**osition node’s input field is evaluated once. To **evalaute**the field, the node travels backwards to retrieve the inputs from the field input nodes." Good: "Here, the **S**et **P**osition node’s input field is evaluated once. To **evaluate**the field, the node travels backwards to retrieve the inputs from the field input nodes." Bad: "When a second **s**et **p**osition node is added, the same field network is evaluated twice, once for each data flow node. At the second **s**et **p**osition node, the results will be different since its geometry input will already have the changed position from the first node." Good: "When a second **S**et **P**osition node is added, the same field network is evaluated twice, once for each data flow node. At the second **S**et **P**osition node, the results will be different since its geometry input will already have the changed position from the first node." Bad: "Here, a **c**apture **a**ttribute node stores a copy of the initial position. Notice that evaluating the field input of the **c**apture **a**ttribute node is an entirely different step. Later on, the input fields to the **s**et **p**osition nodes don’t use the actual position, but the anonymous attribute copy of it." Good: "Here, a **C**apture **A**ttribute node stores a copy of the initial position. Notice that evaluating the field input of the **C**apture **A**ttribute node is an entirely different step. Later on, the input fields to the **S**et **P**osition nodes don’t use the actual position, but the anonymous attribute copy of it."

Garek commented

2021-11-20 16:03:07 +01:00

Added subscriber: @Garek