[Bf-blender-cvs] [cc004fd13cc] soc-2018-bevel: Some more minor typo fixes in comments.

[Bastien Montagne]

Commit: cc004fd13cc6d5cf77d8bb1e33594662d63c7b13
Author: Bastien Montagne
Date:   Wed Aug 1 14:37:24 2018 +0200
Branches: soc-2018-bevel
https://developer.blender.org/rBcc004fd13cc6d5cf77d8bb1e33594662d63c7b13

Some more minor typo fixes in comments.

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

M	source/blender/blenkernel/intern/editmesh.c

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

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? */