Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCampbell Barton <ideasman42@gmail.com>2021-11-30 01:04:50 +0300
committerCampbell Barton <ideasman42@gmail.com>2021-11-30 02:15:17 +0300
commit4e45265dc6cafe0bf6f36a14a469288183059858 (patch)
tree899ea04187908aafbcc590fd026b33d2d3b021c1 /source/blender/depsgraph
parent262ef26ea3fe457ff077224662eaecc1b912aed1 (diff)
Cleanup: spelling in comments & strings
Diffstat (limited to 'source/blender/depsgraph')
-rw-r--r--source/blender/depsgraph/intern/node/deg_node.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/source/blender/depsgraph/intern/node/deg_node.h b/source/blender/depsgraph/intern/node/deg_node.h
index 6274066ba25..01d49640053 100644
--- a/source/blender/depsgraph/intern/node/deg_node.h
+++ b/source/blender/depsgraph/intern/node/deg_node.h
@@ -106,7 +106,7 @@ enum class NodeType {
/* Component which is used to define visibility relation between IDs, on the ID level.
*
* Consider two ID nodes NodeA and NodeB, with the relation between visibility components going
- * as NodeA -> NodeB. If NodeB is considreed visible on screen, then the relation will ensure
+ * as NodeA -> NodeB. If NodeB is considered visible on screen, then the relation will ensure
* that NodeA is also visible. The way how relation is oriented could be seen as a inverted from
* visibility dependency point of view, but it follows the same direction as data dependency
* which simplifies common algorithms which are dealing with relations and visibility.