From ab11a3296424cf47adfad7db54acfae6ba628b8f Mon Sep 17 00:00:00 2001
From: archangel7431 <49980988+archangel7431@users.noreply.github.com>
Date: Mon, 13 Jul 2026 13:10:21 +0530
Subject: [PATCH] Fix typos in OCR tutorial documentation

---
 docs/example/parse_ocr/index.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/example/parse_ocr/index.rst b/docs/example/parse_ocr/index.rst
index d0592e3..da28982 100644
--- a/docs/example/parse_ocr/index.rst
+++ b/docs/example/parse_ocr/index.rst
@@ -24,7 +24,7 @@ Initiate GCV OCR engine and check the image
 
 Currently, ``layoutparser`` supports two types of OCR engines: Google
 Cloud Vision and Tesseract OCR engine. And we are going to provide more
-support in the future. In this toturial, we will use the Google Cloud
+support in the future. In this tutorial, we will use the Google Cloud
 Vision engine as an example.
 
 .. code:: python
@@ -76,7 +76,7 @@ response:
 
    | In this format, GCV automatically find the best aggregation level
      for the text, and return the results in a list. We can
-   | use the ``ocr_agent.gather_text_annotations`` to reterive this type
+   | use the ``ocr_agent.gather_text_annotations`` to retrieve this type
      of information.
 
 2. full_text_annotations