diff --git a/docs/en/1.0.11/publishing.html b/docs/en/1.0.11/publishing.html
index 84fb570b08..f222641eb6 100644
--- a/docs/en/1.0.11/publishing.html
+++ b/docs/en/1.0.11/publishing.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.0.12/publishing/index.html b/docs/en/1.0.12/publishing/index.html
index db0a15cc55..9fee751c5c 100644
--- a/docs/en/1.0.12/publishing/index.html
+++ b/docs/en/1.0.12/publishing/index.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.0.13/publishing.html b/docs/en/1.0.13/publishing.html
index 44a08263aa..5c21415fa2 100644
--- a/docs/en/1.0.13/publishing.html
+++ b/docs/en/1.0.13/publishing.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.0.13/publishing/index.html b/docs/en/1.0.13/publishing/index.html
index 44a08263aa..5c21415fa2 100644
--- a/docs/en/1.0.13/publishing/index.html
+++ b/docs/en/1.0.13/publishing/index.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.0.14/publishing.html b/docs/en/1.0.14/publishing.html
index e95aedb35f..3cc5aab31d 100644
--- a/docs/en/1.0.14/publishing.html
+++ b/docs/en/1.0.14/publishing.html
@@ -98,7 +98,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.0.14/publishing/index.html b/docs/en/1.0.14/publishing/index.html
index e95aedb35f..3cc5aab31d 100644
--- a/docs/en/1.0.14/publishing/index.html
+++ b/docs/en/1.0.14/publishing/index.html
@@ -98,7 +98,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.0.15/publishing.html b/docs/en/1.0.15/publishing.html
index 2af682a1b4..147aaf1304 100644
--- a/docs/en/1.0.15/publishing.html
+++ b/docs/en/1.0.15/publishing.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.0.15/publishing/index.html b/docs/en/1.0.15/publishing/index.html
index 2af682a1b4..147aaf1304 100644
--- a/docs/en/1.0.15/publishing/index.html
+++ b/docs/en/1.0.15/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.0/publishing.html b/docs/en/1.1.0/publishing.html
index 5bc714c098..d38cc55f09 100644
--- a/docs/en/1.1.0/publishing.html
+++ b/docs/en/1.1.0/publishing.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.0/publishing/index.html b/docs/en/1.1.0/publishing/index.html
index 5bc714c098..d38cc55f09 100644
--- a/docs/en/1.1.0/publishing/index.html
+++ b/docs/en/1.1.0/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.1/publishing.html b/docs/en/1.1.1/publishing.html
index 626c57d11a..820dff475e 100644
--- a/docs/en/1.1.1/publishing.html
+++ b/docs/en/1.1.1/publishing.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.1/publishing/index.html b/docs/en/1.1.1/publishing/index.html
index 626c57d11a..820dff475e 100644
--- a/docs/en/1.1.1/publishing/index.html
+++ b/docs/en/1.1.1/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.2/publishing.html b/docs/en/1.1.2/publishing.html
index b00d96cb86..5a97818499 100644
--- a/docs/en/1.1.2/publishing.html
+++ b/docs/en/1.1.2/publishing.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.2/publishing/index.html b/docs/en/1.1.2/publishing/index.html
index b00d96cb86..5a97818499 100644
--- a/docs/en/1.1.2/publishing/index.html
+++ b/docs/en/1.1.2/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.3/publishing.html b/docs/en/1.1.3/publishing.html
index 26e3491218..93d7cd6067 100644
--- a/docs/en/1.1.3/publishing.html
+++ b/docs/en/1.1.3/publishing.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.3/publishing/index.html b/docs/en/1.1.3/publishing/index.html
index 26e3491218..93d7cd6067 100644
--- a/docs/en/1.1.3/publishing/index.html
+++ b/docs/en/1.1.3/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.4/publishing.html b/docs/en/1.1.4/publishing.html
index 33ba97630a..d18832832b 100644
--- a/docs/en/1.1.4/publishing.html
+++ b/docs/en/1.1.4/publishing.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.4/publishing/index.html b/docs/en/1.1.4/publishing/index.html
index 33ba97630a..d18832832b 100644
--- a/docs/en/1.1.4/publishing/index.html
+++ b/docs/en/1.1.4/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.5/publishing.html b/docs/en/1.1.5/publishing.html
index 617b7d6fd3..edc010ea52 100644
--- a/docs/en/1.1.5/publishing.html
+++ b/docs/en/1.1.5/publishing.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.1.5/publishing/index.html b/docs/en/1.1.5/publishing/index.html
index 617b7d6fd3..edc010ea52 100644
--- a/docs/en/1.1.5/publishing/index.html
+++ b/docs/en/1.1.5/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.2.0/publishing.html b/docs/en/1.2.0/publishing.html
index 88a00273cd..ea15796224 100644
--- a/docs/en/1.2.0/publishing.html
+++ b/docs/en/1.2.0/publishing.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.2.0/publishing/index.html b/docs/en/1.2.0/publishing/index.html
index 88a00273cd..ea15796224 100644
--- a/docs/en/1.2.0/publishing/index.html
+++ b/docs/en/1.2.0/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.2.1/publishing.html b/docs/en/1.2.1/publishing.html
index 7f4048d56b..d477e4c1da 100644
--- a/docs/en/1.2.1/publishing.html
+++ b/docs/en/1.2.1/publishing.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.2.1/publishing/index.html b/docs/en/1.2.1/publishing/index.html
index 7f4048d56b..d477e4c1da 100644
--- a/docs/en/1.2.1/publishing/index.html
+++ b/docs/en/1.2.1/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.3.0/publishing.html b/docs/en/1.3.0/publishing.html
index ea04ba8547..ee29bb99f3 100644
--- a/docs/en/1.3.0/publishing.html
+++ b/docs/en/1.3.0/publishing.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.3.0/publishing/index.html b/docs/en/1.3.0/publishing/index.html
index ea04ba8547..ee29bb99f3 100644
--- a/docs/en/1.3.0/publishing/index.html
+++ b/docs/en/1.3.0/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.3.1/publishing.html b/docs/en/1.3.1/publishing.html
index 97976ae4fd..03c89b3d32 100644
--- a/docs/en/1.3.1/publishing.html
+++ b/docs/en/1.3.1/publishing.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.3.1/publishing/index.html b/docs/en/1.3.1/publishing/index.html
index 97976ae4fd..03c89b3d32 100644
--- a/docs/en/1.3.1/publishing/index.html
+++ b/docs/en/1.3.1/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.3.2/publishing.html b/docs/en/1.3.2/publishing.html
index bb6ae526a7..ad0a493bbc 100644
--- a/docs/en/1.3.2/publishing.html
+++ b/docs/en/1.3.2/publishing.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.3.2/publishing/index.html b/docs/en/1.3.2/publishing/index.html
index bb6ae526a7..ad0a493bbc 100644
--- a/docs/en/1.3.2/publishing/index.html
+++ b/docs/en/1.3.2/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.3.3/publishing.html b/docs/en/1.3.3/publishing.html
index 9527874817..f731513ff0 100644
--- a/docs/en/1.3.3/publishing.html
+++ b/docs/en/1.3.3/publishing.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.3.3/publishing/index.html b/docs/en/1.3.3/publishing/index.html
index 9527874817..f731513ff0 100644
--- a/docs/en/1.3.3/publishing/index.html
+++ b/docs/en/1.3.3/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.4.0/publishing.html b/docs/en/1.4.0/publishing.html
index dc13e40b85..d6763a217a 100644
--- a/docs/en/1.4.0/publishing.html
+++ b/docs/en/1.4.0/publishing.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.4.0/publishing/index.html b/docs/en/1.4.0/publishing/index.html
index dc13e40b85..d6763a217a 100644
--- a/docs/en/1.4.0/publishing/index.html
+++ b/docs/en/1.4.0/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.5.0/publishing.html b/docs/en/1.5.0/publishing.html
index 732e0d4d88..e0d00c7912 100644
--- a/docs/en/1.5.0/publishing.html
+++ b/docs/en/1.5.0/publishing.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.5.0/publishing/index.html b/docs/en/1.5.0/publishing/index.html
index 732e0d4d88..e0d00c7912 100644
--- a/docs/en/1.5.0/publishing/index.html
+++ b/docs/en/1.5.0/publishing/index.html
@@ -101,7 +101,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/en/1.5.1/publishing.html b/docs/en/1.5.1/publishing.html
index 0a22c24fa0..fcba7c7be9 100644
--- a/docs/en/1.5.1/publishing.html
+++ b/docs/en/1.5.1/publishing.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/1.5.1/publishing/index.html b/docs/en/1.5.1/publishing/index.html
index 0a22c24fa0..fcba7c7be9 100644
--- a/docs/en/1.5.1/publishing/index.html
+++ b/docs/en/1.5.1/publishing/index.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/1.6.0/publishing.html b/docs/en/1.6.0/publishing.html
index 0e2daebb43..78f2e2e091 100644
--- a/docs/en/1.6.0/publishing.html
+++ b/docs/en/1.6.0/publishing.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/1.6.0/publishing/index.html b/docs/en/1.6.0/publishing/index.html
index 0e2daebb43..78f2e2e091 100644
--- a/docs/en/1.6.0/publishing/index.html
+++ b/docs/en/1.6.0/publishing/index.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/1.6.1/publishing.html b/docs/en/1.6.1/publishing.html
index c2f2fc1eb8..7280dbb994 100644
--- a/docs/en/1.6.1/publishing.html
+++ b/docs/en/1.6.1/publishing.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/1.6.1/publishing/index.html b/docs/en/1.6.1/publishing/index.html
index c2f2fc1eb8..7280dbb994 100644
--- a/docs/en/1.6.1/publishing/index.html
+++ b/docs/en/1.6.1/publishing/index.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/1.6.2/publishing.html b/docs/en/1.6.2/publishing.html
index 4934955438..a231de3a92 100644
--- a/docs/en/1.6.2/publishing.html
+++ b/docs/en/1.6.2/publishing.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/1.6.2/publishing/index.html b/docs/en/1.6.2/publishing/index.html
index 4934955438..a231de3a92 100644
--- a/docs/en/1.6.2/publishing/index.html
+++ b/docs/en/1.6.2/publishing/index.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/1.7.0/publishing.html b/docs/en/1.7.0/publishing.html
index 1ad65b9f18..c50f818c72 100644
--- a/docs/en/1.7.0/publishing.html
+++ b/docs/en/1.7.0/publishing.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/1.7.0/publishing/index.html b/docs/en/1.7.0/publishing/index.html
index 1ad65b9f18..c50f818c72 100644
--- a/docs/en/1.7.0/publishing/index.html
+++ b/docs/en/1.7.0/publishing/index.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/1.7.1/publishing.html b/docs/en/1.7.1/publishing.html
index e8b5d8c444..c1ed2e0fc9 100644
--- a/docs/en/1.7.1/publishing.html
+++ b/docs/en/1.7.1/publishing.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/1.7.1/publishing/index.html b/docs/en/1.7.1/publishing/index.html
index e8b5d8c444..c1ed2e0fc9 100644
--- a/docs/en/1.7.1/publishing/index.html
+++ b/docs/en/1.7.1/publishing/index.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/publishing.html b/docs/en/publishing.html
index 30662af64e..6bafc222a6 100644
--- a/docs/en/publishing.html
+++ b/docs/en/publishing.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/en/publishing/index.html b/docs/en/publishing/index.html
index 30662af64e..6bafc222a6 100644
--- a/docs/en/publishing/index.html
+++ b/docs/en/publishing/index.html
@@ -134,7 +134,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.0.11/publishing.html b/docs/es-ES/1.0.11/publishing.html
index 14fea76a52..23a3983477 100644
--- a/docs/es-ES/1.0.11/publishing.html
+++ b/docs/es-ES/1.0.11/publishing.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.0.12/publishing/index.html b/docs/es-ES/1.0.12/publishing/index.html
index 92f9573c18..01d7c184eb 100644
--- a/docs/es-ES/1.0.12/publishing/index.html
+++ b/docs/es-ES/1.0.12/publishing/index.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.0.13/publishing.html b/docs/es-ES/1.0.13/publishing.html
index 02e2ff9418..9780095d6a 100644
--- a/docs/es-ES/1.0.13/publishing.html
+++ b/docs/es-ES/1.0.13/publishing.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.0.13/publishing/index.html b/docs/es-ES/1.0.13/publishing/index.html
index 02e2ff9418..9780095d6a 100644
--- a/docs/es-ES/1.0.13/publishing/index.html
+++ b/docs/es-ES/1.0.13/publishing/index.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.0.14/publishing.html b/docs/es-ES/1.0.14/publishing.html
index 0c1e135337..064a95aa9b 100644
--- a/docs/es-ES/1.0.14/publishing.html
+++ b/docs/es-ES/1.0.14/publishing.html
@@ -98,7 +98,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.0.14/publishing/index.html b/docs/es-ES/1.0.14/publishing/index.html
index 0c1e135337..064a95aa9b 100644
--- a/docs/es-ES/1.0.14/publishing/index.html
+++ b/docs/es-ES/1.0.14/publishing/index.html
@@ -98,7 +98,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.0.15/publishing.html b/docs/es-ES/1.0.15/publishing.html
index f2efa78c21..5998c12ea2 100644
--- a/docs/es-ES/1.0.15/publishing.html
+++ b/docs/es-ES/1.0.15/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.0.15/publishing/index.html b/docs/es-ES/1.0.15/publishing/index.html
index f2efa78c21..5998c12ea2 100644
--- a/docs/es-ES/1.0.15/publishing/index.html
+++ b/docs/es-ES/1.0.15/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.0/publishing.html b/docs/es-ES/1.1.0/publishing.html
index 39a3d58aef..c8686ef667 100644
--- a/docs/es-ES/1.1.0/publishing.html
+++ b/docs/es-ES/1.1.0/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.0/publishing/index.html b/docs/es-ES/1.1.0/publishing/index.html
index 39a3d58aef..c8686ef667 100644
--- a/docs/es-ES/1.1.0/publishing/index.html
+++ b/docs/es-ES/1.1.0/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.1/publishing.html b/docs/es-ES/1.1.1/publishing.html
index eed24f7a74..d08c871893 100644
--- a/docs/es-ES/1.1.1/publishing.html
+++ b/docs/es-ES/1.1.1/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.1/publishing/index.html b/docs/es-ES/1.1.1/publishing/index.html
index eed24f7a74..d08c871893 100644
--- a/docs/es-ES/1.1.1/publishing/index.html
+++ b/docs/es-ES/1.1.1/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.2/publishing.html b/docs/es-ES/1.1.2/publishing.html
index 58c57a1e65..ea92229474 100644
--- a/docs/es-ES/1.1.2/publishing.html
+++ b/docs/es-ES/1.1.2/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.2/publishing/index.html b/docs/es-ES/1.1.2/publishing/index.html
index 58c57a1e65..ea92229474 100644
--- a/docs/es-ES/1.1.2/publishing/index.html
+++ b/docs/es-ES/1.1.2/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.3/publishing.html b/docs/es-ES/1.1.3/publishing.html
index 4d54932651..1d189d2527 100644
--- a/docs/es-ES/1.1.3/publishing.html
+++ b/docs/es-ES/1.1.3/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.3/publishing/index.html b/docs/es-ES/1.1.3/publishing/index.html
index 4d54932651..1d189d2527 100644
--- a/docs/es-ES/1.1.3/publishing/index.html
+++ b/docs/es-ES/1.1.3/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.4/publishing.html b/docs/es-ES/1.1.4/publishing.html
index b895b3eaaf..8436a13ca9 100644
--- a/docs/es-ES/1.1.4/publishing.html
+++ b/docs/es-ES/1.1.4/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.4/publishing/index.html b/docs/es-ES/1.1.4/publishing/index.html
index b895b3eaaf..8436a13ca9 100644
--- a/docs/es-ES/1.1.4/publishing/index.html
+++ b/docs/es-ES/1.1.4/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.5/publishing.html b/docs/es-ES/1.1.5/publishing.html
index 00653d7c6b..11a60744c9 100644
--- a/docs/es-ES/1.1.5/publishing.html
+++ b/docs/es-ES/1.1.5/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.1.5/publishing/index.html b/docs/es-ES/1.1.5/publishing/index.html
index 00653d7c6b..11a60744c9 100644
--- a/docs/es-ES/1.1.5/publishing/index.html
+++ b/docs/es-ES/1.1.5/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.2.0/publishing.html b/docs/es-ES/1.2.0/publishing.html
index bb61c4f05b..f0d419b0e8 100644
--- a/docs/es-ES/1.2.0/publishing.html
+++ b/docs/es-ES/1.2.0/publishing.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.2.0/publishing/index.html b/docs/es-ES/1.2.0/publishing/index.html
index bb61c4f05b..f0d419b0e8 100644
--- a/docs/es-ES/1.2.0/publishing/index.html
+++ b/docs/es-ES/1.2.0/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.2.1/publishing.html b/docs/es-ES/1.2.1/publishing.html
index 52dc3c503c..8d3eb05be6 100644
--- a/docs/es-ES/1.2.1/publishing.html
+++ b/docs/es-ES/1.2.1/publishing.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.2.1/publishing/index.html b/docs/es-ES/1.2.1/publishing/index.html
index 52dc3c503c..8d3eb05be6 100644
--- a/docs/es-ES/1.2.1/publishing/index.html
+++ b/docs/es-ES/1.2.1/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.3.0/publishing.html b/docs/es-ES/1.3.0/publishing.html
index 4988f9b490..442db6819b 100644
--- a/docs/es-ES/1.3.0/publishing.html
+++ b/docs/es-ES/1.3.0/publishing.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.3.0/publishing/index.html b/docs/es-ES/1.3.0/publishing/index.html
index 4988f9b490..442db6819b 100644
--- a/docs/es-ES/1.3.0/publishing/index.html
+++ b/docs/es-ES/1.3.0/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.3.1/publishing.html b/docs/es-ES/1.3.1/publishing.html
index 70ae4ff411..6797748c30 100644
--- a/docs/es-ES/1.3.1/publishing.html
+++ b/docs/es-ES/1.3.1/publishing.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.3.1/publishing/index.html b/docs/es-ES/1.3.1/publishing/index.html
index 70ae4ff411..6797748c30 100644
--- a/docs/es-ES/1.3.1/publishing/index.html
+++ b/docs/es-ES/1.3.1/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.3.2/publishing.html b/docs/es-ES/1.3.2/publishing.html
index f954a4a3f3..5958deafca 100644
--- a/docs/es-ES/1.3.2/publishing.html
+++ b/docs/es-ES/1.3.2/publishing.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.3.2/publishing/index.html b/docs/es-ES/1.3.2/publishing/index.html
index f954a4a3f3..5958deafca 100644
--- a/docs/es-ES/1.3.2/publishing/index.html
+++ b/docs/es-ES/1.3.2/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.3.3/publishing.html b/docs/es-ES/1.3.3/publishing.html
index 2e42dcfee4..9bdb0329b4 100644
--- a/docs/es-ES/1.3.3/publishing.html
+++ b/docs/es-ES/1.3.3/publishing.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.3.3/publishing/index.html b/docs/es-ES/1.3.3/publishing/index.html
index 2e42dcfee4..9bdb0329b4 100644
--- a/docs/es-ES/1.3.3/publishing/index.html
+++ b/docs/es-ES/1.3.3/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.4.0/publishing.html b/docs/es-ES/1.4.0/publishing.html
index 0bc7a1aa71..e71f74785e 100644
--- a/docs/es-ES/1.4.0/publishing.html
+++ b/docs/es-ES/1.4.0/publishing.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.4.0/publishing/index.html b/docs/es-ES/1.4.0/publishing/index.html
index 0bc7a1aa71..e71f74785e 100644
--- a/docs/es-ES/1.4.0/publishing/index.html
+++ b/docs/es-ES/1.4.0/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.5.0/publishing.html b/docs/es-ES/1.5.0/publishing.html
index 6e0a6a0f97..72f92b61b8 100644
--- a/docs/es-ES/1.5.0/publishing.html
+++ b/docs/es-ES/1.5.0/publishing.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.5.0/publishing/index.html b/docs/es-ES/1.5.0/publishing/index.html
index 6e0a6a0f97..72f92b61b8 100644
--- a/docs/es-ES/1.5.0/publishing/index.html
+++ b/docs/es-ES/1.5.0/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/es-ES/1.5.1/publishing.html b/docs/es-ES/1.5.1/publishing.html
index dbcf2baa8a..639ac7cdc0 100644
--- a/docs/es-ES/1.5.1/publishing.html
+++ b/docs/es-ES/1.5.1/publishing.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.5.1/publishing/index.html b/docs/es-ES/1.5.1/publishing/index.html
index dbcf2baa8a..639ac7cdc0 100644
--- a/docs/es-ES/1.5.1/publishing/index.html
+++ b/docs/es-ES/1.5.1/publishing/index.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.6.0/publishing.html b/docs/es-ES/1.6.0/publishing.html
index 3d5076bac5..0fe212edd2 100644
--- a/docs/es-ES/1.6.0/publishing.html
+++ b/docs/es-ES/1.6.0/publishing.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.6.0/publishing/index.html b/docs/es-ES/1.6.0/publishing/index.html
index 3d5076bac5..0fe212edd2 100644
--- a/docs/es-ES/1.6.0/publishing/index.html
+++ b/docs/es-ES/1.6.0/publishing/index.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.6.1/publishing.html b/docs/es-ES/1.6.1/publishing.html
index eae510eaa0..cc014866dc 100644
--- a/docs/es-ES/1.6.1/publishing.html
+++ b/docs/es-ES/1.6.1/publishing.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.6.1/publishing/index.html b/docs/es-ES/1.6.1/publishing/index.html
index eae510eaa0..cc014866dc 100644
--- a/docs/es-ES/1.6.1/publishing/index.html
+++ b/docs/es-ES/1.6.1/publishing/index.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.6.2/publishing.html b/docs/es-ES/1.6.2/publishing.html
index 709abfc40c..d64716badf 100644
--- a/docs/es-ES/1.6.2/publishing.html
+++ b/docs/es-ES/1.6.2/publishing.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.6.2/publishing/index.html b/docs/es-ES/1.6.2/publishing/index.html
index 709abfc40c..d64716badf 100644
--- a/docs/es-ES/1.6.2/publishing/index.html
+++ b/docs/es-ES/1.6.2/publishing/index.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.7.0/publishing.html b/docs/es-ES/1.7.0/publishing.html
index f9d7ed1517..f6528061c7 100644
--- a/docs/es-ES/1.7.0/publishing.html
+++ b/docs/es-ES/1.7.0/publishing.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.7.0/publishing/index.html b/docs/es-ES/1.7.0/publishing/index.html
index f9d7ed1517..f6528061c7 100644
--- a/docs/es-ES/1.7.0/publishing/index.html
+++ b/docs/es-ES/1.7.0/publishing/index.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.7.1/publishing.html b/docs/es-ES/1.7.1/publishing.html
index c93ecb16af..0623f58dcb 100644
--- a/docs/es-ES/1.7.1/publishing.html
+++ b/docs/es-ES/1.7.1/publishing.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/1.7.1/publishing/index.html b/docs/es-ES/1.7.1/publishing/index.html
index c93ecb16af..0623f58dcb 100644
--- a/docs/es-ES/1.7.1/publishing/index.html
+++ b/docs/es-ES/1.7.1/publishing/index.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/publishing.html b/docs/es-ES/publishing.html
index 9bb13b0327..681d2cd3af 100644
--- a/docs/es-ES/publishing.html
+++ b/docs/es-ES/publishing.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/es-ES/publishing/index.html b/docs/es-ES/publishing/index.html
index 9bb13b0327..681d2cd3af 100644
--- a/docs/es-ES/publishing/index.html
+++ b/docs/es-ES/publishing/index.html
@@ -132,7 +132,7 @@
While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.
-- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
+- Now you have to specify the git user as an environment variable, and run the script
publish-gh-pages
diff --git a/docs/ro/1.0.11/publishing.html b/docs/ro/1.0.11/publishing.html
index d0b170500f..7bb174b1ae 100644
--- a/docs/ro/1.0.11/publishing.html
+++ b/docs/ro/1.0.11/publishing.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
organizationName: The GitHub user or organization that owns the repository. In the case of Docusaurus, that would be the "facebook" GitHub organization.
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.0.12/publishing/index.html b/docs/ro/1.0.12/publishing/index.html
index 57a93c9f11..14ec83338e 100644
--- a/docs/ro/1.0.12/publishing/index.html
+++ b/docs/ro/1.0.12/publishing/index.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.0.13/publishing.html b/docs/ro/1.0.13/publishing.html
index c2a7f002e5..e85d03b094 100644
--- a/docs/ro/1.0.13/publishing.html
+++ b/docs/ro/1.0.13/publishing.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.0.13/publishing/index.html b/docs/ro/1.0.13/publishing/index.html
index c2a7f002e5..e85d03b094 100644
--- a/docs/ro/1.0.13/publishing/index.html
+++ b/docs/ro/1.0.13/publishing/index.html
@@ -93,7 +93,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.0.14/publishing.html b/docs/ro/1.0.14/publishing.html
index 9dd266c0fa..58281a5362 100644
--- a/docs/ro/1.0.14/publishing.html
+++ b/docs/ro/1.0.14/publishing.html
@@ -98,7 +98,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.0.14/publishing/index.html b/docs/ro/1.0.14/publishing/index.html
index 9dd266c0fa..58281a5362 100644
--- a/docs/ro/1.0.14/publishing/index.html
+++ b/docs/ro/1.0.14/publishing/index.html
@@ -98,7 +98,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.0.15/publishing.html b/docs/ro/1.0.15/publishing.html
index 0cc027fb5e..810bfb8e19 100644
--- a/docs/ro/1.0.15/publishing.html
+++ b/docs/ro/1.0.15/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.0.15/publishing/index.html b/docs/ro/1.0.15/publishing/index.html
index 0cc027fb5e..810bfb8e19 100644
--- a/docs/ro/1.0.15/publishing/index.html
+++ b/docs/ro/1.0.15/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.0/publishing.html b/docs/ro/1.1.0/publishing.html
index 02188f0bdb..6d504804c0 100644
--- a/docs/ro/1.1.0/publishing.html
+++ b/docs/ro/1.1.0/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.0/publishing/index.html b/docs/ro/1.1.0/publishing/index.html
index 02188f0bdb..6d504804c0 100644
--- a/docs/ro/1.1.0/publishing/index.html
+++ b/docs/ro/1.1.0/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.1/publishing.html b/docs/ro/1.1.1/publishing.html
index c5e747e46e..284692dffa 100644
--- a/docs/ro/1.1.1/publishing.html
+++ b/docs/ro/1.1.1/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.1/publishing/index.html b/docs/ro/1.1.1/publishing/index.html
index c5e747e46e..284692dffa 100644
--- a/docs/ro/1.1.1/publishing/index.html
+++ b/docs/ro/1.1.1/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.2/publishing.html b/docs/ro/1.1.2/publishing.html
index 778d03a8b8..9de5461c71 100644
--- a/docs/ro/1.1.2/publishing.html
+++ b/docs/ro/1.1.2/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.2/publishing/index.html b/docs/ro/1.1.2/publishing/index.html
index 778d03a8b8..9de5461c71 100644
--- a/docs/ro/1.1.2/publishing/index.html
+++ b/docs/ro/1.1.2/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.3/publishing.html b/docs/ro/1.1.3/publishing.html
index d6961d8495..354ce5bf13 100644
--- a/docs/ro/1.1.3/publishing.html
+++ b/docs/ro/1.1.3/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.3/publishing/index.html b/docs/ro/1.1.3/publishing/index.html
index d6961d8495..354ce5bf13 100644
--- a/docs/ro/1.1.3/publishing/index.html
+++ b/docs/ro/1.1.3/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.4/publishing.html b/docs/ro/1.1.4/publishing.html
index 38c33600ff..a9f05794b4 100644
--- a/docs/ro/1.1.4/publishing.html
+++ b/docs/ro/1.1.4/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.4/publishing/index.html b/docs/ro/1.1.4/publishing/index.html
index 38c33600ff..a9f05794b4 100644
--- a/docs/ro/1.1.4/publishing/index.html
+++ b/docs/ro/1.1.4/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.5/publishing.html b/docs/ro/1.1.5/publishing.html
index 0ea696f81f..f9637512a0 100644
--- a/docs/ro/1.1.5/publishing.html
+++ b/docs/ro/1.1.5/publishing.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.1.5/publishing/index.html b/docs/ro/1.1.5/publishing/index.html
index 0ea696f81f..f9637512a0 100644
--- a/docs/ro/1.1.5/publishing/index.html
+++ b/docs/ro/1.1.5/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repo is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.2.0/publishing.html b/docs/ro/1.2.0/publishing.html
index 7a462c2829..1bd530d8dc 100644
--- a/docs/ro/1.2.0/publishing.html
+++ b/docs/ro/1.2.0/publishing.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.2.0/publishing/index.html b/docs/ro/1.2.0/publishing/index.html
index 7a462c2829..1bd530d8dc 100644
--- a/docs/ro/1.2.0/publishing/index.html
+++ b/docs/ro/1.2.0/publishing/index.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a gh-pages branch will be public.
-Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
+Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.
Two of the required parameters are set in the siteConfig.js:
diff --git a/docs/ro/1.2.1/publishing.html b/docs/ro/1.2.1/publishing.html
index f0a7dd3e27..7c774d32ea 100644
--- a/docs/ro/1.2.1/publishing.html
+++ b/docs/ro/1.2.1/publishing.html
@@ -99,7 +99,7 @@
Even if your repository is private, anything published to a