From c62eda023d2a355d8a68426fdc66844a86affc95 Mon Sep 17 00:00:00 2001 From: Ankit Yadav Date: Sat, 11 Jun 2016 17:56:58 +0530 Subject: [PATCH] Fix typo --- doc/py_tutorials/py_imgproc/py_grabcut/py_grabcut.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/py_tutorials/py_imgproc/py_grabcut/py_grabcut.markdown b/doc/py_tutorials/py_imgproc/py_grabcut/py_grabcut.markdown index 98392b314e..a44a727f70 100644 --- a/doc/py_tutorials/py_imgproc/py_grabcut/py_grabcut.markdown +++ b/doc/py_tutorials/py_imgproc/py_grabcut/py_grabcut.markdown @@ -17,7 +17,7 @@ graph cuts](http://dl.acm.org/citation.cfm?id=1015720) . An algorithm was needed extraction with minimal user interaction, and the result was GrabCut. How it works from user point of view ? Initially user draws a rectangle around the foreground region -(foreground region shoule be completely inside the rectangle). Then algorithm segments it +(foreground region should be completely inside the rectangle). Then algorithm segments it iteratively to get the best result. Done. But in some cases, the segmentation won't be fine, like, it may have marked some foreground region as background and vice versa. In that case, user need to do fine touch-ups. Just give some strokes on the images where some faulty results are there. Strokes