[Bf-blender-cvs] [fd901517b57] temp-lineart-contained: Cleanup: Typo

[YimingWu]

Commit: fd901517b57d34c5ef6ec9c315f92e6372da4a8e
Author: YimingWu
Date:   Mon Nov 15 19:56:19 2021 +0800
Branches: temp-lineart-contained
https://developer.blender.org/rBfd901517b57d34c5ef6ec9c315f92e6372da4a8e

Cleanup: Typo

===================================================================

M	source/blender/gpencil_modifiers/intern/lineart/lineart_cpu.c

===================================================================

diff --git a/source/blender/gpencil_modifiers/intern/lineart/lineart_cpu.c b/source/blender/gpencil_modifiers/intern/lineart/lineart_cpu.c
index 9b635ffb8dc..628a7442a25 100644
--- a/source/blender/gpencil_modifiers/intern/lineart/lineart_cpu.c
+++ b/source/blender/gpencil_modifiers/intern/lineart/lineart_cpu.c
@@ -2453,12 +2453,12 @@ static bool lineart_edge_from_triangle(const LineartTriangle *tri,
  *
  * 2) Currently using discrete a/b/c/pa/pb/pc/is[3] values for storing
  * intersection/edge_aligned/intersection_order info, which isn't optimal, needs a better
- * representation (likely a struct) for redability and clarity of code path.
+ * representation (likely a struct) for readability and clarity of code path.
  *
  * I keep this function as-is because it's still fast, and more importantly the output value
  * threshold is already in tune with the cutting function in the next stage.
  * While current "edge aligned" fix isn't ideal, it does solve most of the precision issue
- * expecially in ortho camera mode.
+ * especially in ortho camera mode.
  */
 static bool lineart_triangle_edge_image_space_occlusion(SpinLock *UNUSED(spl),
                                                         const LineartTriangle *tri,