[Bf-docboard-svn] bf-manual: [8651] branches/blender-3.0-release/blender_docs/manual: some fixes

Tobias Heinke noreply at blender.org
Sun Nov 21 04:37:42 CET 2021


Revision: 8651
          https://developer.blender.org/rBM8651
Author:   TobiasH
Date:     2021-11-21 04:37:41 +0100 (Sun, 21 Nov 2021)
Log Message:
-----------
some fixes

Modified Paths:
--------------
    branches/blender-3.0-release/blender_docs/manual/grease_pencil/modes/draw/tools/draw.rst
    branches/blender-3.0-release/blender_docs/manual/grease_pencil/modes/draw/tools/erase.rst
    branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/attribute/capture_attribute.rst
    branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/attributes_reference.rst
    branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/fields.rst
    branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/geometry/transform.rst
    branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/inspection.rst
    branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/instances/rotate_instances.rst
    branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/instances/scale_instances.rst
    branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/instances/translate_instances.rst
    branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/instances.rst
    branches/blender-3.0-release/blender_docs/manual/render/cycles/render_settings/sampling.rst
    branches/blender-3.0-release/blender_docs/manual/render/layers/passes.rst
    branches/blender-3.0-release/blender_docs/manual/video_editing/sequencer/sidebar/strip.rst
    branches/blender-3.0-release/blender_docs/manual/video_editing/sequencer/strips/introduction.rst

Modified: branches/blender-3.0-release/blender_docs/manual/grease_pencil/modes/draw/tools/draw.rst
===================================================================
--- branches/blender-3.0-release/blender_docs/manual/grease_pencil/modes/draw/tools/draw.rst	2021-11-20 22:36:32 UTC (rev 8650)
+++ branches/blender-3.0-release/blender_docs/manual/grease_pencil/modes/draw/tools/draw.rst	2021-11-21 03:37:41 UTC (rev 8651)
@@ -143,7 +143,6 @@
 Adds randomness to the position of the points along the stroke.
 You can toggle the use of Randomize using the checkbox in the section panel header.
 
-
 .. _bpy.types.BrushGpencilSettings.use_stroke_random_radius:
 .. _bpy.types.BrushGpencilSettings.use_random_press_radius:
 .. _bpy.types.BrushGpencilSettings.random:

Modified: branches/blender-3.0-release/blender_docs/manual/grease_pencil/modes/draw/tools/erase.rst
===================================================================
--- branches/blender-3.0-release/blender_docs/manual/grease_pencil/modes/draw/tools/erase.rst	2021-11-20 22:36:32 UTC (rev 8650)
+++ branches/blender-3.0-release/blender_docs/manual/grease_pencil/modes/draw/tools/erase.rst	2021-11-21 03:37:41 UTC (rev 8651)
@@ -29,7 +29,7 @@
    .. _bpy.types.BrushGpencilSettings.use_default_eraser:
 
    Default Eraser
-      Use this brush when enabling the eraser tool with fast switch key (:kbd:`Ctrl`).
+      Use this brush when enabling the eraser tool with the fast switch key (:kbd:`Ctrl`).
 
 
 .. _bpy.types.BrushGpencilSettings.eraser_mode:

Modified: branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/attribute/capture_attribute.rst
===================================================================
--- branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/attribute/capture_attribute.rst	2021-11-20 22:36:32 UTC (rev 8650)
+++ branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/attribute/capture_attribute.rst	2021-11-21 03:37:41 UTC (rev 8651)
@@ -25,8 +25,8 @@
 .. note::
 
    Because this node stores an :ref:`anonymous attribute <anonymous-attributes>` in the geometry,
-   it's essential use the geometry output for further operations in the node tree. The anonymous
-   attribute will not exist for any other geometry besides the output.
+   it's essential to use the geometry output for further operations in the node tree.
+   The anonymous attribute will not exist for any other geometry besides the output.
 
 
 Inputs
@@ -60,10 +60,10 @@
 
 .. figure:: /images/modeling_geometry-nodes_attribute_capture-attribute_example.png
 
-Here, a noise texture is evaluated in along the path of the curve in 1 dimension
-and rendered with a shader. The capture node is essential because the output of
-the :doc:`/modeling/geometry_nodes/curve/curve_to_mesh` does not have "Curve Parameter",
-since it is a mesh and not a curve. So the :doc:`/modeling/geometry_nodes/curve/curve_parameter`
+Here, a noise texture is evaluated in along the path of the curve in one dimension
+and rendered with a shader. The capture node is required because the output of
+the :doc:`/modeling/geometry_nodes/curve/curve_to_mesh` does not have a "curve parameter",
+since it is a mesh and not a curve. So, the :doc:`/modeling/geometry_nodes/curve/curve_parameter`
 must be evaluated while the geometry is still a curve.
 
 Internally, after the noise texture is evaluated on the curve,

Modified: branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/attributes_reference.rst
===================================================================
--- branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/attributes_reference.rst	2021-11-20 22:36:32 UTC (rev 8650)
+++ branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/attributes_reference.rst	2021-11-21 03:37:41 UTC (rev 8651)
@@ -30,6 +30,7 @@
 To the left of the menu, the attribute domain is shown followed by the attribute name.
 To the right of the menu, the attribute data type is shown.
 
+
 .. _anonymous-attributes:
 
 Anonymous Attributes
@@ -42,7 +43,6 @@
    which refer to an attribute stored on a geometry.
 
 An anonymous attribute is a set of generic data stored on a geometry that doesn't have a name.
-
 Usually, attributes exposed in Blender's interface all have names. However,
 in geometry nodes, attributes can be passed around with node sockets.
 In these cases, an *Attribute Field* output is created, which is used by
@@ -51,9 +51,8 @@
 Anonymous attributes are still stored on the geometry like other attributes, and they are even
 automatically interpolated when the geometry changes with other nodes, except for a few cases.
 So generally, if the node link is still accessible, the attribute it references will be too.
-
 However, anonymous attributes cannot be connected to a completely separate geometry
-that was not created from their source. To transfer attributes between separate geometries,
+that was not created from their source. To transfer attributes between separate pieces of geometry,
 the :doc:`/modeling/geometry_nodes/attribute/transfer_attribute` can be used.
 
 

Modified: branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/fields.rst
===================================================================
--- branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/fields.rst	2021-11-20 22:36:32 UTC (rev 8650)
+++ branches/blender-3.0-release/blender_docs/manual/modeling/geometry_nodes/fields.rst	2021-11-21 03:37:41 UTC (rev 8651)
@@ -9,19 +9,15 @@
 
    A field input to a node.
 
-
-What Are Fields?
-================
-
 Fundamentally, a field is a function: a set of instructions that can transform an arbitrary number
-of inputs into a single output. A field's result can then be calculated many times with different
-input data. They are used all over geometry nodes to allow calculations that have different results
+of inputs into a single output. A field's result can then be calculated many times with different input data.
+They are used all over geometry nodes to allow calculations that have different results
 for every element (mesh vertices, faces, etc.).
 
 For example, in the figure above, the field connected to the "Set Position" node
-depends on two inputs, :doc:`position </modeling/geometry_nodes/input/position>` and 
+depends on two inputs, :doc:`position </modeling/geometry_nodes/input/position>` and
 :doc:`index </modeling/geometry_nodes/input/index>`, and transforms them into
-into a vector using a single instruction.
+a vector using a single instruction.
 
 
 Field Visualization
@@ -28,7 +24,7 @@
 ===================
 
 Socket shapes are used to convey which sockets are fields and which regular data.
-There are three possible socket shapes, each conveying the socket's "field status":
+There are three possible socket shapes, each visualizing its "field status":
 
 :Circle:
    The socket requires a single real value, it cannot accept a field input.
@@ -47,12 +43,12 @@
    :align: center
 
    The socket shape is a diamond with a dot, meaning the field has the same value
-   for every element. Every point will be moved up by 5m.
+   for every element. Every point will be moved up by 5 m.
 
 .. figure:: /images/modeling_geometry-nodes_fields_varying.png
    :align: center
 
-   The socket shape is a diamond and the field input now has a varying input. In other words, 
+   The socket shape is a diamond and the field input now has a varying input. In other words,
    the value can be different for every element. In this case, the position will be doubled,
    since the offset for every point is the point's position.
 
@@ -64,26 +60,27 @@
    or the :doc:`/modeling/geometry_nodes/attribute/attribute_statistic` can be used
    to retrieve a single value from a field evaluated on a geometry.
 
-
 When a connection is made between two node sockets that support
 fields the node connection will be drawn as a dashed line.
-If you make the mistake of connecting a non field socket to a field socket,
-the connection will be drawn as a solid red line indicating that there is an error in the connection.
+If you make the mistake of connecting a non-field socket to a field socket,
+the connection will be drawn as a solid red line indicating that there is an error.
 
 
 Node Types
 ==========
 
-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. Field nodes can be input nodes that
+Nodes can be separated into two categories: data flow nodes that usually pass geometry,
+and field nodes that operate on data per-element. Field nodes can be input nodes that
 bring geometry data into the node tree, or function nodes that operate on that data.
 
+
 Data Flow Nodes
 ---------------
 
-Nodes with a geometry input and a geometry output will almost always be data flow nodes, meaning
-they actually change geometry data that will be outputed from the geometry nodes modifier.
+Nodes with a geometry input and a geometry output will almost always be data flow nodes.
+Meaning that they actually change geometry data that will be outputted from the geometry nodes modifier.
 
+
 Function Nodes
 --------------
 
@@ -91,45 +88,46 @@
 that will be evaluated by data flow nodes. Examples of function nodes are the math nodes
 and also more complex nodes like the :doc:`/modeling/geometry_nodes/geometry/geometry_proximity`.
 
+
 Input Nodes
 -----------
 
 Input nodes provide data to the field evaluation process. By themselves, they mean nothing; they
 must be evaluated within the context of a data flow node (geometry) to actually output a value.
-Examples of input nodes are the built-in attribute input nodes like 
-:doc:`position </modeling/geometry_nodes/input/position>` and 
-:doc:`ID </modeling/geometry_nodes/input/id>`, but also selection nodes like 
+Examples of input nodes are the built-in attribute input nodes like
+:doc:`position </modeling/geometry_nodes/input/position>` and
+:doc:`ID </modeling/geometry_nodes/input/id>`, but also selection nodes like
 :doc:`endpoint selection </modeling/geometry_nodes/curve/endpoint_selection>`.
 
-Field inputs may also come from other nodes that process geometry like the 
-:doc:`/modeling/geometry_nodes/point/distribute_points_on_faces`, 

@@ Diff output truncated at 10240 characters. @@


More information about the Bf-docboard-svn mailing list