diff options
author | Bastien Montagne <montagne29@wanadoo.fr> | 2018-08-01 15:37:24 +0300 |
---|---|---|
committer | Bastien Montagne <montagne29@wanadoo.fr> | 2018-08-01 15:37:24 +0300 |
commit | cc004fd13cc6d5cf77d8bb1e33594662d63c7b13 (patch) | |
tree | dd6d2bcd4fdb0b952351810b69256ac5b1c49b3f /source | |
parent | 9a43ebdd5b5e7c8f4a4202d7eb2bcb3e33a2d76e (diff) |
Some more minor typo fixes in comments.
Diffstat (limited to 'source')
-rw-r--r-- | source/blender/blenkernel/intern/editmesh.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/source/blender/blenkernel/intern/editmesh.c b/source/blender/blenkernel/intern/editmesh.c index a7f93ca6c49..00e508e4d8f 100644 --- a/source/blender/blenkernel/intern/editmesh.c +++ b/source/blender/blenkernel/intern/editmesh.c @@ -251,10 +251,10 @@ void BKE_editmesh_lnorspace_update(BMEditMesh *em) { BMesh *bm = em->bm; - /* We need to create clnors data is none exist yet, otherwise there is no way to edit them. */ + /* We need to create clnors data if none exist yet, otherwise there is no way to edit them. */ /* Similar code to MESH_OT_customdata_custom_splitnormals_add operator, we want to keep same shading * in case we were using autosmooth so far... */ - /* Note: there is a problem here, which is that is someone starts a normal editing operation on previously + /* Note: there is a problem here, which is that if someone starts a normal editing operation on previously * autosmooth-ed mesh, and cancel that operation, generated clnors data remain, with related sharp edges * (and hence autosmooth is 'lost'). * Not sure how critical this is, and how to fix that issue? */ |