From 49ba74413039b83faa74f474322b51af0014b0a5 Mon Sep 17 00:00:00 2001
From: or-toledano <49984106+or-toledano@users.noreply.github.com>
Date: Mon, 14 Sep 2020 14:23:38 +0300
Subject: [PATCH] Fix np row,column to cv y,x

This explanation was created to avoid confusion, but it seems like the author was confused :D
---
 .../py_contour_properties/py_contour_properties.markdown        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/py_tutorials/py_imgproc/py_contours/py_contour_properties/py_contour_properties.markdown b/doc/py_tutorials/py_imgproc/py_contours/py_contour_properties/py_contour_properties.markdown
index a07b5e87b3..461c870343 100644
--- a/doc/py_tutorials/py_imgproc/py_contours/py_contour_properties/py_contour_properties.markdown
+++ b/doc/py_tutorials/py_imgproc/py_contours/py_contour_properties/py_contour_properties.markdown
@@ -78,7 +78,7 @@ pixelpoints = np.transpose(np.nonzero(mask))
 Here, two methods, one using Numpy functions, next one using OpenCV function (last commented line)
 are given to do the same. Results are also same, but with a slight difference. Numpy gives
 coordinates in **(row, column)** format, while OpenCV gives coordinates in **(x,y)** format. So
-basically the answers will be interchanged. Note that, **row = x** and **column = y**.
+basically the answers will be interchanged. Note that, **row = y** and **column = x**.
 
 7. Maximum Value, Minimum Value and their locations
 ---------------------------------------------------