diff --git a/docs_source_files/content/webdriver/page_loading_strategy.de.md b/docs_source_files/content/webdriver/page_loading_strategy.de.md
index a0e9d58c18aa..2bc77578f133 100644
--- a/docs_source_files/content/webdriver/page_loading_strategy.de.md
+++ b/docs_source_files/content/webdriver/page_loading_strategy.de.md
@@ -9,6 +9,20 @@ it follows the _normal_ pageLoadStrategy.
 It is always recommended to stop downloading additional 
 resources (like images, css, js) when the page loading takes lot of time.
 
+The `document.readyState` property of a document describes the loading state of the current document.
+By default, WebDriver will hold off on responding to a `driver.get()` (or) `driver.navigate().to()` 
+call until the document ready state is `complete`
+
+In SPA applications (like Angular, react, Ember) once the dynamic content 
+is already loaded (I.e once the pageLoadStrategy status is COMPLETE), 
+clicking on a link or performing some action within the page will not make a new request 
+to the server as the content is dynamically loaded at the client side without a pull page refresh. 
+
+SPA applications can load many views dynamically 
+without any server requests, So pageLoadStrategy 
+will always show `COMPLETE` status until 
+we do a new `driver.get()` and `driver.naviagte().to()`
+
 WebDriver _pageLoadStrategy_ supports the following values:
 
 ## normal
diff --git a/docs_source_files/content/webdriver/page_loading_strategy.en.md b/docs_source_files/content/webdriver/page_loading_strategy.en.md
index 8532ff9f029b..528d258f2523 100644
--- a/docs_source_files/content/webdriver/page_loading_strategy.en.md
+++ b/docs_source_files/content/webdriver/page_loading_strategy.en.md
@@ -9,6 +9,20 @@ it follows the _normal_ pageLoadStrategy.
 It is always recommended to stop downloading additional 
 resources (like images, css, js) when the page loading takes lot of time.
 
+The `document.readyState` property of a document describes the loading state of the current document.
+By default, WebDriver will hold off on responding to a `driver.get()` (or) `driver.navigate().to()` 
+call until the document ready state is `complete`
+
+In SPA applications (like Angular, react, Ember) once the dynamic content 
+is already loaded (I.e once the pageLoadStrategy status is COMPLETE), 
+clicking on a link or performing some action within the page will not make a new request 
+to the server as the content is dynamically loaded at the client side without a pull page refresh. 
+
+SPA applications can load many views dynamically 
+without any server requests, So pageLoadStrategy 
+will always show `COMPLETE` status until 
+we do a new `driver.get()` and `driver.naviagte().to()`
+
 WebDriver _pageLoadStrategy_ supports the following values:
 
 ## normal
@@ -247,3 +261,4 @@ fun main() {
 }
   {{< / code-panel >}}
 {{< / code-tab >}}
+
diff --git a/docs_source_files/content/webdriver/page_loading_strategy.es.md b/docs_source_files/content/webdriver/page_loading_strategy.es.md
index 2215f1c45f26..680831202fda 100644
--- a/docs_source_files/content/webdriver/page_loading_strategy.es.md
+++ b/docs_source_files/content/webdriver/page_loading_strategy.es.md
@@ -15,6 +15,20 @@ it follows the _normal_ pageLoadStrategy.
 It is always recommended to stop downloading additional 
 resources (like images, css, js) when the page loading takes lot of time.
 
+The `document.readyState` property of a document describes the loading state of the current document.
+By default, WebDriver will hold off on responding to a `driver.get()` (or) `driver.navigate().to()` 
+call until the document ready state is `complete`
+
+In SPA applications (like Angular, react, Ember) once the dynamic content 
+is already loaded (I.e once the pageLoadStrategy status is COMPLETE), 
+clicking on a link or performing some action within the page will not make a new request 
+to the server as the content is dynamically loaded at the client side without a pull page refresh. 
+
+SPA applications can load many views dynamically 
+without any server requests, So pageLoadStrategy 
+will always show `COMPLETE` status until 
+we do a new `driver.get()` and `driver.naviagte().to()`
+
 WebDriver _pageLoadStrategy_ supports the following values:
 
 ## normal
diff --git a/docs_source_files/content/webdriver/page_loading_strategy.fr.md b/docs_source_files/content/webdriver/page_loading_strategy.fr.md
index 114931af125c..b44ad47475db 100644
--- a/docs_source_files/content/webdriver/page_loading_strategy.fr.md
+++ b/docs_source_files/content/webdriver/page_loading_strategy.fr.md
@@ -15,6 +15,20 @@ it follows the _normal_ pageLoadStrategy.
 It is always recommended to stop downloading additional 
 resources (like images, css, js) when the page loading takes lot of time.
 
+The `document.readyState` property of a document describes the loading state of the current document.
+By default, WebDriver will hold off on responding to a `driver.get()` (or) `driver.navigate().to()` 
+call until the document ready state is `complete`
+
+In SPA applications (like Angular, react, Ember) once the dynamic content 
+is already loaded (I.e once the pageLoadStrategy status is COMPLETE), 
+clicking on a link or performing some action within the page will not make a new request 
+to the server as the content is dynamically loaded at the client side without a pull page refresh. 
+
+SPA applications can load many views dynamically 
+without any server requests, So pageLoadStrategy 
+will always show `COMPLETE` status until 
+we do a new `driver.get()` and `driver.naviagte().to()`
+
 WebDriver _pageLoadStrategy_ supports the following values:
 
 ## normal
diff --git a/docs_source_files/content/webdriver/page_loading_strategy.ja.md b/docs_source_files/content/webdriver/page_loading_strategy.ja.md
index 2f7e703dd08d..735cda56572c 100644
--- a/docs_source_files/content/webdriver/page_loading_strategy.ja.md
+++ b/docs_source_files/content/webdriver/page_loading_strategy.ja.md
@@ -7,6 +7,20 @@ weight: 8
 デフォルトでは、Selenium WebDriverがページを読み込む場合、 pageLoadStrategy は _normal_ となります。
 ページの読み込みに時間がかかる場合は、追加のリソース（画像、CSS、JSなど）のダウンロードを停止することを常にお勧めします。
 
+The `document.readyState` property of a document describes the loading state of the current document.
+By default, WebDriver will hold off on responding to a `driver.get()` (or) `driver.navigate().to()` 
+call until the document ready state is `complete`
+
+In SPA applications (like Angular, react, Ember) once the dynamic content 
+is already loaded (I.e once the pageLoadStrategy status is COMPLETE), 
+clicking on a link or performing some action within the page will not make a new request 
+to the server as the content is dynamically loaded at the client side without a pull page refresh. 
+
+SPA applications can load many views dynamically 
+without any server requests, So pageLoadStrategy 
+will always show `COMPLETE` status until 
+we do a new `driver.get()` and `driver.naviagte().to()`
+
 WebDriverの _pageLoadStrategy_ は以下の値をサポートします。
 
 ## normal
diff --git a/docs_source_files/content/webdriver/page_loading_strategy.ko.md b/docs_source_files/content/webdriver/page_loading_strategy.ko.md
index 96de044f9fab..55dda20e7c06 100644
--- a/docs_source_files/content/webdriver/page_loading_strategy.ko.md
+++ b/docs_source_files/content/webdriver/page_loading_strategy.ko.md
@@ -15,6 +15,20 @@ it follows the _normal_ pageLoadStrategy.
 It is always recommended to stop downloading additional 
 resources (like images, css, js) when the page loading takes lot of time.
 
+The `document.readyState` property of a document describes the loading state of the current document.
+By default, WebDriver will hold off on responding to a `driver.get()` (or) `driver.navigate().to()` 
+call until the document ready state is `complete`
+
+In SPA applications (like Angular, react, Ember) once the dynamic content 
+is already loaded (I.e once the pageLoadStrategy status is COMPLETE), 
+clicking on a link or performing some action within the page will not make a new request 
+to the server as the content is dynamically loaded at the client side without a pull page refresh. 
+
+SPA applications can load many views dynamically 
+without any server requests, So pageLoadStrategy 
+will always show `COMPLETE` status until 
+we do a new `driver.get()` and `driver.naviagte().to()`
+
 WebDriver _pageLoadStrategy_ supports the following values:
 
 ## normal
@@ -253,4 +267,3 @@ fun main() {
 }
   {{< / code-panel >}}
 {{< / code-tab >}}
-
diff --git a/docs_source_files/content/webdriver/page_loading_strategy.nl.md b/docs_source_files/content/webdriver/page_loading_strategy.nl.md
index 684d23ade19a..e9e8cc63c741 100644
--- a/docs_source_files/content/webdriver/page_loading_strategy.nl.md
+++ b/docs_source_files/content/webdriver/page_loading_strategy.nl.md
@@ -15,6 +15,20 @@ it follows the _normal_ pageLoadStrategy.
 It is always recommended to stop downloading additional 
 resources (like images, css, js) when the page loading takes lot of time.
 
+The `document.readyState` property of a document describes the loading state of the current document.
+By default, WebDriver will hold off on responding to a `driver.get()` (or) `driver.navigate().to()` 
+call until the document ready state is `complete`
+
+In SPA applications (like Angular, react, Ember) once the dynamic content 
+is already loaded (I.e once the pageLoadStrategy status is COMPLETE), 
+clicking on a link or performing some action within the page will not make a new request 
+to the server as the content is dynamically loaded at the client side without a pull page refresh. 
+
+SPA applications can load many views dynamically 
+without any server requests, So pageLoadStrategy 
+will always show `COMPLETE` status until 
+we do a new `driver.get()` and `driver.naviagte().to()`
+
 WebDriver _pageLoadStrategy_ supports the following values:
 
 ## normal
@@ -253,3 +267,4 @@ fun main() {
 }
   {{< / code-panel >}}
 {{< / code-tab >}}
+
diff --git a/docs_source_files/content/webdriver/page_loading_strategy.zh-cn.md b/docs_source_files/content/webdriver/page_loading_strategy.zh-cn.md
index d822c0cc55a3..fb49902d6f04 100644
--- a/docs_source_files/content/webdriver/page_loading_strategy.zh-cn.md
+++ b/docs_source_files/content/webdriver/page_loading_strategy.zh-cn.md
@@ -9,6 +9,20 @@ it follows the _normal_ pageLoadStrategy.
 It is always recommended to stop downloading additional 
 resources (like images, css, js) when the page loading takes lot of time.
 
+The `document.readyState` property of a document describes the loading state of the current document.
+By default, WebDriver will hold off on responding to a `driver.get()` (or) `driver.navigate().to()` 
+call until the document ready state is `complete`
+
+In SPA applications (like Angular, react, Ember) once the dynamic content 
+is already loaded (I.e once the pageLoadStrategy status is COMPLETE), 
+clicking on a link or performing some action within the page will not make a new request 
+to the server as the content is dynamically loaded at the client side without a pull page refresh. 
+
+SPA applications can load many views dynamically 
+without any server requests, So pageLoadStrategy 
+will always show `COMPLETE` status until 
+we do a new `driver.get()` and `driver.naviagte().to()`
+
 WebDriver _pageLoadStrategy_ supports the following values:
 
 ## normal
@@ -247,4 +261,3 @@ fun main() {
 }
   {{< / code-panel >}}
 {{< / code-tab >}}
-