From f8a4b6e2b48ace95ef9e11e7a2df10567e6735cb Mon Sep 17 00:00:00 2001
From: Lektor Bot <bot@getlektor.com>
Date: Wed, 13 Dec 2023 09:46:31 +0000
Subject: [PATCH] Synchronized build

---
 .../describe-records/contributors/index.html  |  4 +-
 .../describe-records/creators/index.html      |  4 +-
 .../describe-records/descriptions/index.html  |  4 +-
 docs/deposit/describe-records/index.html      |  8 +--
 .../describe-records/licenses/index.html      |  4 +-
 .../publication-date/index.html               |  4 +-
 .../describe-records/reserve-doi/index.html   |  4 +-
 .../describe-records/resource-type/index.html |  4 +-
 .../describe-records/titles/index.html        |  4 +-
 docs/deposit/index.html                       |  2 +-
 faq/citations/index.html                      |  9 +--
 faq/general/index.html                        | 21 +++---
 faq/github/index.html                         |  6 +-
 faq/index.html                                | 72 +++++++++----------
 faq/policies/index.html                       | 17 ++---
 faq/statistics/index.html                     |  6 +-
 faq/technical/index.html                      |  2 +-
 faq/versioning/index.html                     | 11 ++-
 18 files changed, 89 insertions(+), 97 deletions(-)

diff --git a/docs/deposit/describe-records/contributors/index.html b/docs/deposit/describe-records/contributors/index.html
index 2071216..dbe217b 100644
--- a/docs/deposit/describe-records/contributors/index.html
+++ b/docs/deposit/describe-records/contributors/index.html
@@ -106,10 +106,10 @@
           
           <a href="../" class="list-group-item active"">Describe records</a>
           
-          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
-          
           <a href="../reserve-doi/" class="sub list-group-item">Digital Object Identifier (DOI)</a>
           
+          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
+          
           <a href="../titles/" class="sub list-group-item">Titles</a>
           
           <a href="../publication-date/" class="sub list-group-item">Publication date</a>
diff --git a/docs/deposit/describe-records/creators/index.html b/docs/deposit/describe-records/creators/index.html
index 92c8bd4..6e78e2a 100644
--- a/docs/deposit/describe-records/creators/index.html
+++ b/docs/deposit/describe-records/creators/index.html
@@ -106,10 +106,10 @@
           
           <a href="../" class="list-group-item active"">Describe records</a>
           
-          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
-          
           <a href="../reserve-doi/" class="sub list-group-item">Digital Object Identifier (DOI)</a>
           
+          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
+          
           <a href="../titles/" class="sub list-group-item">Titles</a>
           
           <a href="../publication-date/" class="sub list-group-item">Publication date</a>
diff --git a/docs/deposit/describe-records/descriptions/index.html b/docs/deposit/describe-records/descriptions/index.html
index a091e5f..ee75c10 100644
--- a/docs/deposit/describe-records/descriptions/index.html
+++ b/docs/deposit/describe-records/descriptions/index.html
@@ -106,10 +106,10 @@
           
           <a href="../" class="list-group-item active"">Describe records</a>
           
-          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
-          
           <a href="../reserve-doi/" class="sub list-group-item">Digital Object Identifier (DOI)</a>
           
+          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
+          
           <a href="../titles/" class="sub list-group-item">Titles</a>
           
           <a href="../publication-date/" class="sub list-group-item">Publication date</a>
diff --git a/docs/deposit/describe-records/index.html b/docs/deposit/describe-records/index.html
index 99e776d..aa79497 100644
--- a/docs/deposit/describe-records/index.html
+++ b/docs/deposit/describe-records/index.html
@@ -106,10 +106,10 @@
           
           <a href="./" class="list-group-item active"">Describe records</a>
           
-          <a href="resource-type/" class="sub list-group-item">Resource types</a>
-          
           <a href="reserve-doi/" class="sub list-group-item">Digital Object Identifier (DOI)</a>
           
+          <a href="resource-type/" class="sub list-group-item">Resource types</a>
+          
           <a href="titles/" class="sub list-group-item">Titles</a>
           
           <a href="publication-date/" class="sub list-group-item">Publication date</a>
@@ -159,10 +159,10 @@ <h1>Describe records</h1>
 
 <ul>
     <li>
-    <a href="resource-type/">Resource types</a> &mdash; Select the right resource type.
+    <a href="reserve-doi/">Digital Object Identifier (DOI)</a> &mdash; How to reserve a DOI for inclusion in files before publication.
     </li>
     <li>
-    <a href="reserve-doi/">Digital Object Identifier (DOI)</a> &mdash; How to reserve a DOI for inclusion in files before publication.
+    <a href="resource-type/">Resource types</a> &mdash; Select the right resource type.
     </li>
     <li>
     <a href="titles/">Titles</a> &mdash; How to add main title and additional titles.
diff --git a/docs/deposit/describe-records/licenses/index.html b/docs/deposit/describe-records/licenses/index.html
index a9200cb..f75188f 100644
--- a/docs/deposit/describe-records/licenses/index.html
+++ b/docs/deposit/describe-records/licenses/index.html
@@ -106,10 +106,10 @@
           
           <a href="../" class="list-group-item active"">Describe records</a>
           
-          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
-          
           <a href="../reserve-doi/" class="sub list-group-item">Digital Object Identifier (DOI)</a>
           
+          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
+          
           <a href="../titles/" class="sub list-group-item">Titles</a>
           
           <a href="../publication-date/" class="sub list-group-item">Publication date</a>
diff --git a/docs/deposit/describe-records/publication-date/index.html b/docs/deposit/describe-records/publication-date/index.html
index 713098f..ebdc3ca 100644
--- a/docs/deposit/describe-records/publication-date/index.html
+++ b/docs/deposit/describe-records/publication-date/index.html
@@ -106,10 +106,10 @@
           
           <a href="../" class="list-group-item active"">Describe records</a>
           
-          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
-          
           <a href="../reserve-doi/" class="sub list-group-item">Digital Object Identifier (DOI)</a>
           
+          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
+          
           <a href="../titles/" class="sub list-group-item">Titles</a>
           
           <a href="./" class="sub list-group-item highlight">Publication date</a>
diff --git a/docs/deposit/describe-records/reserve-doi/index.html b/docs/deposit/describe-records/reserve-doi/index.html
index 33c9948..8d960ec 100644
--- a/docs/deposit/describe-records/reserve-doi/index.html
+++ b/docs/deposit/describe-records/reserve-doi/index.html
@@ -106,10 +106,10 @@
           
           <a href="../" class="list-group-item active"">Describe records</a>
           
-          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
-          
           <a href="./" class="sub list-group-item highlight">Digital Object Identifier (DOI)</a>
           
+          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
+          
           <a href="../titles/" class="sub list-group-item">Titles</a>
           
           <a href="../publication-date/" class="sub list-group-item">Publication date</a>
diff --git a/docs/deposit/describe-records/resource-type/index.html b/docs/deposit/describe-records/resource-type/index.html
index f0d1d6c..f34fffd 100644
--- a/docs/deposit/describe-records/resource-type/index.html
+++ b/docs/deposit/describe-records/resource-type/index.html
@@ -106,10 +106,10 @@
           
           <a href="../" class="list-group-item active"">Describe records</a>
           
-          <a href="./" class="sub list-group-item highlight">Resource types</a>
-          
           <a href="../reserve-doi/" class="sub list-group-item">Digital Object Identifier (DOI)</a>
           
+          <a href="./" class="sub list-group-item highlight">Resource types</a>
+          
           <a href="../titles/" class="sub list-group-item">Titles</a>
           
           <a href="../publication-date/" class="sub list-group-item">Publication date</a>
diff --git a/docs/deposit/describe-records/titles/index.html b/docs/deposit/describe-records/titles/index.html
index 00081ff..ed0ddd4 100644
--- a/docs/deposit/describe-records/titles/index.html
+++ b/docs/deposit/describe-records/titles/index.html
@@ -106,10 +106,10 @@
           
           <a href="../" class="list-group-item active"">Describe records</a>
           
-          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
-          
           <a href="../reserve-doi/" class="sub list-group-item">Digital Object Identifier (DOI)</a>
           
+          <a href="../resource-type/" class="sub list-group-item">Resource types</a>
+          
           <a href="./" class="sub list-group-item highlight">Titles</a>
           
           <a href="../publication-date/" class="sub list-group-item">Publication date</a>
diff --git a/docs/deposit/index.html b/docs/deposit/index.html
index c7ad0ea..23893b9 100644
--- a/docs/deposit/index.html
+++ b/docs/deposit/index.html
@@ -150,8 +150,8 @@ <h3 id="overview" class="docs">Overview <small><a href="#overview" class="text-m
     <li>
     <a href="describe-records/">Describe records</a> &mdash; How to fill metadata for each specific field.
     <ul>
-        <li><a href="describe-records/resource-type/">Resource types</a> &mdash; Select the right resource type.
         <li><a href="describe-records/reserve-doi/">Digital Object Identifier (DOI)</a> &mdash; How to reserve a DOI for inclusion in files before publication.
+        <li><a href="describe-records/resource-type/">Resource types</a> &mdash; Select the right resource type.
         <li><a href="describe-records/titles/">Titles</a> &mdash; How to add main title and additional titles.
         <li><a href="describe-records/publication-date/">Publication date</a> &mdash; Learn to use date ranges or imprecise dates.
         <li><a href="describe-records/creators/">Creators</a> &mdash; Learn how to add creators/authors for your record.
diff --git a/faq/citations/index.html b/faq/citations/index.html
index 50d7da5..5671c0f 100644
--- a/faq/citations/index.html
+++ b/faq/citations/index.html
@@ -141,7 +141,7 @@ <h4 class="panel-title">
     </div>
     <div id="ccitations-3" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hcitations-3">
       <div class="panel-body">
-        <p>We display citations if available for all records in Zenodo.</p>
+        <p>We display citations, if available, for all records in Zenodo.</p>
 
       </div>
     </div>
@@ -179,10 +179,7 @@ <h4 class="panel-title">
     </div>
     <div id="ccitations-5" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hcitations-5">
       <div class="panel-body">
-        <p>Currently (January 2019) we primarily cover:</p>
-<ul>
-<li>Astronomy and astrophysics</li>
-</ul>
+        <p>Currently (January 2019) we primarily cover astronomy and astrophysics.</p>
 <p>We also receive citation data from cross-domain citation data sources, however often the coverage is not good as it relies on publishers to make the citation data freely available (which some big publishers do not do).</p>
 
       </div>
@@ -349,7 +346,7 @@ <h4 class="panel-title">
     </div>
     <div id="ccitations-15" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hcitations-15">
       <div class="panel-body">
-        <p>We usually receive citation data as a link between two persistent identifiers (e.g. "DOI A cites DOI B") without any metadata. We therefore have to automatically retrieve metadata such as title, authors and publication year from other services. This automatic fetching of metadata however is sometimes not able to find any available metadata, in which case we only display the persistent identifier.</p>
+        <p>We usually receive citation data as a link between two persistent identifiers (e.g. "DOI A cites DOI B") without any metadata. We therefore have to automatically retrieve metadata such as title, authors and publication year from other services. Sometimes this automatic fetching is not able to find any available metadata, in which case we only display the persistent identifier.</p>
 
       </div>
     </div>
diff --git a/faq/general/index.html b/faq/general/index.html
index 365291b..06de1ff 100644
--- a/faq/general/index.html
+++ b/faq/general/index.html
@@ -101,28 +101,27 @@ <h3 id="general">General</h3>
     <div class="panel-heading" role="tab" id="hgeneral-1">
       <h4 class="panel-title">
         <a role="button" data-toggle="collapse" data-parent="#accordion" href="#cgeneral-1" aria-expanded="true" aria-controls="cgeneral-1">
-          <p>Can I change the file in the already published record?</p>
+          <p>Can I change files in an already published record?</p>
 
         </a>
       </h4>
     </div>
     <div id="cgeneral-1" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hgeneral-1">
       <div class="panel-body">
-        <p>Once the record has been published, you can no longer change the files in the record, nonetheless, there are several options:</p>
+        <p>Once the record has been published you can no longer change its files. Nonetheless, there are several options:</p>
 <ol>
 <li>If the record has a Zenodo DOI (prefix: <code>10.5281</code>):<ul>
-<li>The recommended way is to create a new version of a record (more details available <a href="../../#versioning">here</a>).
-Most of the cases fall under this category, which include modifications of the dataset/software, addition or removal of files, new versions of datasets, software or revisions of the papers, including major revisions as well typos and formatting/styling.</li>
-<li>Exceptionally, we allow small modifications to the record's files, if and only if the record was published recently (less than 1 month). If you have spotted mistakes such as typos, accidental omission of important files/inclusion of hidden files or confidential files and would like to update them, please contact us.</li>
+<li>In most cases it is recommended to create a new version of a record (<a href="../#versioning">more details</a>). For example: modifications of the dataset/software, addition or removal of files, new versions of datasets, software or revisions of the papers, including major revisions as well typos and formatting/styling.</li>
+<li>Exceptionally, we allow small modifications to the record's files, if and only if the record was published recently (in the past month). If you have spotted mistakes such as typos, accidental omission of important files/inclusion of hidden files or confidential files and would like to update them, please contact us.</li>
 </ul>
 </li>
 <li>If the record has a non-Zenodo DOI:<ul>
-<li>Since it is not possible to create new versions for the non-Zenodo DOIs you should contact us about the file update directly.</li>
+<li>Since it is not possible to create new versions for non-Zenodo DOIs you should contact us about updating files directly.</li>
 </ul>
 </li>
 </ol>
 <p>All file update requests need to be submitted through our <a href="https://zenodo.org/support">contact form</a>.</p>
-<p>Meeting above points ensures that we can resolve your case faster.
+<p>Meeting the above points ensures that we can resolve your case faster.
 Please note that we may reject your request if we deem that it is not a small change.</p>
 
       </div>
@@ -139,9 +138,9 @@ <h4 class="panel-title">
     </div>
     <div id="cgeneral-2" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hgeneral-2">
       <div class="panel-body">
-        <p>Zenodo is a strong supporter of open data in all its forms (meaning data that anyone is free to use, reuse, and redistribute) and takes an incentives approach to encourage depositing under an open license.
+        <p>Zenodo is a strong supporter of open data in all its forms (meaning data that anyone is free to use, reuse, and redistribute) and takes an incentive approach to encourage depositing under an open license.
 We therefore only display Open Access uploads on the front-page.
-Your Closed Access upload is still discoverable through search queries, its DOI, and any communities where it is included.</p>
+Closed access uploads are still discoverable through search queries, its DOI, and any communities where it is included.</p>
 
       </div>
     </div>
@@ -157,9 +156,9 @@ <h4 class="panel-title">
     </div>
     <div id="cgeneral-3" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hgeneral-3">
       <div class="panel-body">
-        <p>Since there isn't a unique way of licensing openly and nor a consensus on the practice of adding attribution restrictions, we accept data under a variety of licenses in order to be inclusive.
+        <p>Since there isn't a unique way of licensing openly, nor a consensus on the practice of adding attribution restrictions, we accept data under a variety of licenses in order to be inclusive.
 We will, however, take an active lead in signaling the extra benefits of the most open licenses, in terms of visibility and credit, and offer additional services and upload quotas on such data to encourage using them.
-This follows naturally from the publications policy of the <a href="https://www.openaire.eu">OpenAIRE initiative</a>, which has been supporting Open Access throughout, but since it aims to gather all European Commission/European Research Area research results, it allows submission of material that is not yet Open Access.</p>
+This follows naturally from the publications policy of the <a href="https://www.openaire.eu">OpenAIRE initiative</a> which is a strong supporter of Open Access and allows submission of material that is not yet Open Access since it aims to gather all European Commission/European Research Area research results.</p>
 
       </div>
     </div>
diff --git a/faq/github/index.html b/faq/github/index.html
index b221d92..e121dcc 100644
--- a/faq/github/index.html
+++ b/faq/github/index.html
@@ -109,7 +109,7 @@ <h4 class="panel-title">
     <div id="cgithub-1" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hgithub-1">
       <div class="panel-body">
         <p>In order to see and archive your organizational repositories on Zenodo you will need to have "Admin" permissions on said repository, either as an Admin of the organization or an Admin of one of your organization's repositories.
-Additionally, please make sure that the OAuth application on GitHub is granting permissions not only to your personal repositories but also to your organizational ones - to verify that go to your GitHub OAuth settings in <a href="https://github.com/settings/applications">your profile</a>, and click on the Zenodo application to see more details. Make sure that Zenodo is given access (green tick) to your organization under "Organization access".</p>
+Additionally, please make sure that the OAuth application on GitHub grants permissions not only to your personal repositories but also to your organizational ones: To verify go to your GitHub OAuth settings in <a href="https://github.com/settings/applications">your profile</a>, and click on the Zenodo application to see more details. Also ensure that Zenodo is given access (green tick) to your organization under "Organization access".</p>
 <p>After that, navigate to your Zenodo <a href="https://zenodo.org/account/settings/github/">GitHub settings page</a> and click the "Sync now" button at the top.</p>
 
       </div>
@@ -126,7 +126,7 @@ <h4 class="panel-title">
     </div>
     <div id="cgithub-2" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hgithub-2">
       <div class="panel-body">
-        <p>Make sure the repository was enabled before the release was made, otherwise feel free to contact us.</p>
+        <p>Make sure the repository was enabled before the release was made, otherwise feel free to <a href="https://zenodo.org/support">contact us</a>.</p>
 
       </div>
     </div>
@@ -151,7 +151,7 @@ <h4 class="panel-title">
     <div class="panel-heading" role="tab" id="hgithub-4">
       <h4 class="panel-title">
         <a role="button" data-toggle="collapse" data-parent="#accordion" href="#cgithub-4" aria-expanded="true" aria-controls="cgithub-4">
-          <p>How to change the default metadata for my GitHub releases?</p>
+          <p>How to change the default metadata for my GitHub release?</p>
 
         </a>
       </h4>
diff --git a/faq/index.html b/faq/index.html
index ce121e7..c664670 100644
--- a/faq/index.html
+++ b/faq/index.html
@@ -105,28 +105,27 @@ <h3 id="general">General</h3>
     <div class="panel-heading" role="tab" id="hgeneral-1">
       <h4 class="panel-title">
         <a role="button" data-toggle="collapse" data-parent="#accordion" href="#cgeneral-1" aria-expanded="true" aria-controls="cgeneral-1">
-          <p>Can I change the file in the already published record?</p>
+          <p>Can I change files in an already published record?</p>
 
         </a>
       </h4>
     </div>
     <div id="cgeneral-1" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hgeneral-1">
       <div class="panel-body">
-        <p>Once the record has been published, you can no longer change the files in the record, nonetheless, there are several options:</p>
+        <p>Once the record has been published you can no longer change its files. Nonetheless, there are several options:</p>
 <ol>
 <li>If the record has a Zenodo DOI (prefix: <code>10.5281</code>):<ul>
-<li>The recommended way is to create a new version of a record (more details available <a href="../#versioning">here</a>).
-Most of the cases fall under this category, which include modifications of the dataset/software, addition or removal of files, new versions of datasets, software or revisions of the papers, including major revisions as well typos and formatting/styling.</li>
-<li>Exceptionally, we allow small modifications to the record's files, if and only if the record was published recently (less than 1 month). If you have spotted mistakes such as typos, accidental omission of important files/inclusion of hidden files or confidential files and would like to update them, please contact us.</li>
+<li>In most cases it is recommended to create a new version of a record (<a href="#versioning">more details</a>). For example: modifications of the dataset/software, addition or removal of files, new versions of datasets, software or revisions of the papers, including major revisions as well typos and formatting/styling.</li>
+<li>Exceptionally, we allow small modifications to the record's files, if and only if the record was published recently (in the past month). If you have spotted mistakes such as typos, accidental omission of important files/inclusion of hidden files or confidential files and would like to update them, please contact us.</li>
 </ul>
 </li>
 <li>If the record has a non-Zenodo DOI:<ul>
-<li>Since it is not possible to create new versions for the non-Zenodo DOIs you should contact us about the file update directly.</li>
+<li>Since it is not possible to create new versions for non-Zenodo DOIs you should contact us about updating files directly.</li>
 </ul>
 </li>
 </ol>
 <p>All file update requests need to be submitted through our <a href="https://zenodo.org/support">contact form</a>.</p>
-<p>Meeting above points ensures that we can resolve your case faster.
+<p>Meeting the above points ensures that we can resolve your case faster.
 Please note that we may reject your request if we deem that it is not a small change.</p>
 
       </div>
@@ -143,9 +142,9 @@ <h4 class="panel-title">
     </div>
     <div id="cgeneral-2" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hgeneral-2">
       <div class="panel-body">
-        <p>Zenodo is a strong supporter of open data in all its forms (meaning data that anyone is free to use, reuse, and redistribute) and takes an incentives approach to encourage depositing under an open license.
+        <p>Zenodo is a strong supporter of open data in all its forms (meaning data that anyone is free to use, reuse, and redistribute) and takes an incentive approach to encourage depositing under an open license.
 We therefore only display Open Access uploads on the front-page.
-Your Closed Access upload is still discoverable through search queries, its DOI, and any communities where it is included.</p>
+Closed access uploads are still discoverable through search queries, its DOI, and any communities where it is included.</p>
 
       </div>
     </div>
@@ -161,9 +160,9 @@ <h4 class="panel-title">
     </div>
     <div id="cgeneral-3" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hgeneral-3">
       <div class="panel-body">
-        <p>Since there isn't a unique way of licensing openly and nor a consensus on the practice of adding attribution restrictions, we accept data under a variety of licenses in order to be inclusive.
+        <p>Since there isn't a unique way of licensing openly, nor a consensus on the practice of adding attribution restrictions, we accept data under a variety of licenses in order to be inclusive.
 We will, however, take an active lead in signaling the extra benefits of the most open licenses, in terms of visibility and credit, and offer additional services and upload quotas on such data to encourage using them.
-This follows naturally from the publications policy of the <a href="https://www.openaire.eu">OpenAIRE initiative</a>, which has been supporting Open Access throughout, but since it aims to gather all European Commission/European Research Area research results, it allows submission of material that is not yet Open Access.</p>
+This follows naturally from the publications policy of the <a href="https://www.openaire.eu">OpenAIRE initiative</a> which is a strong supporter of Open Access and allows submission of material that is not yet Open Access since it aims to gather all European Commission/European Research Area research results.</p>
 
       </div>
     </div>
@@ -333,7 +332,7 @@ <h4 class="panel-title">
     <div class="panel-heading" role="tab" id="htechnical-2">
       <h4 class="panel-title">
         <a role="button" data-toggle="collapse" data-parent="#accordion" href="#ctechnical-2" aria-expanded="true" aria-controls="ctechnical-2">
-          <p>Why am I getting an error when trying to upload my files?</p>
+          <p>Why am I getting an error when trying to upload files?</p>
 
         </a>
       </h4>
@@ -361,17 +360,18 @@ <h3 id="policies">Policies</h3>
     <div class="panel-heading" role="tab" id="hpolicies-1">
       <h4 class="panel-title">
         <a role="button" data-toggle="collapse" data-parent="#accordion" href="#cpolicies-1" aria-expanded="true" aria-controls="cpolicies-1">
-          <p>What are the size limits in Zenodo?</p>
+          <p>What are the size limits of Zenodo?</p>
 
         </a>
       </h4>
     </div>
     <div id="cpolicies-1" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hpolicies-1">
       <div class="panel-body">
-        <p>We currently accept up to 50GB per dataset (you can have multiple datasets); there is no size limit on the number of records in communities.
+        <p>We currently accept up to 50GB per dataset (you can have multiple datasets). 
 However, we don't want to turn away use cases for larger datasets.
 If you would like to upload larger files, please <a href="https://zenodo.org/support">contact us</a>, and we will do our best to help you.
 Please be aware that we cannot offer infinite space for free, so donations towards sustainability are encouraged.</p>
+<p>There are no size limit on the number of records in communities.</p>
 
       </div>
     </div>
@@ -406,7 +406,7 @@ <h4 class="panel-title">
     <div id="cpolicies-3" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hpolicies-3">
       <div class="panel-body">
         <p>Where data that was originally <a href="https://www.openaire.eu/sensitive-data-guide">sensitive personal data</a> is being uploaded for open dissemination through Zenodo, the uploader shall ensure that such data is either anonymised to an appropriate degree or fully consent cleared.
-There are several tools that can help uploaders to anonymise their data, being one of them OpenAIRE <a href="https://amnesia.openaire.eu">Amnesia</a>.</p>
+There are several tools that can help uploaders to anonymise their data such as OpenAIRE <a href="https://amnesia.openaire.eu">Amnesia</a>.</p>
 
       </div>
     </div>
@@ -433,17 +433,17 @@ <h4 class="panel-title">
     <div class="panel-heading" role="tab" id="hpolicies-5">
       <h4 class="panel-title">
         <a role="button" data-toggle="collapse" data-parent="#accordion" href="#cpolicies-5" aria-expanded="true" aria-controls="cpolicies-5">
-          <p>Is my data safe with you / What will happen to my uploads in the unlikely event that Zenodo has to close?</p>
+          <p>Is my data safe with you? What will happen to my uploads in the unlikely event that Zenodo has to close?</p>
 
         </a>
       </h4>
     </div>
     <div id="cpolicies-5" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hpolicies-5">
       <div class="panel-body">
-        <p>Yes, your data is stored in CERN Data Center.
+        <p>Yes, your data is safe as it is stored in the CERN Data Center.
 Both data files and metadata are kept in multiple online and independent replicas.
 CERN has considerable knowledge and experience in building and operating large scale digital repositories and a commitment to maintain this data centre to collect and store 100s of PBs of LHC data as it grows over the next 20 years.
-In the highly unlikely event that Zenodo will have to close operations, we guarantee that we will migrate all content to other suitable repositories, and since all uploads have DOIs, all citations and links to Zenodo resources (such as your data) will not be affected.</p>
+In the highly unlikely event that Zenodo will have to close operations, we guarantee that we will migrate all content to other suitable repositories. Since all uploads have DOIs, all citations and links to Zenodo resources (such as your data) will not be affected.</p>
 
       </div>
     </div>
@@ -459,7 +459,7 @@ <h4 class="panel-title">
     </div>
     <div id="cpolicies-6" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hpolicies-6">
       <div class="panel-body">
-        <p>Zenodo and the underlying Invenio Framework for digital repositories were designed according to the OAIS reference model. Full OAIS compliance can only be proven through ISO 16363 certification which is a recent standard with very few repositories worldwide certified to date. See our infrastructure page for further details on Zenodo’s organizational and technical infrastructure.</p>
+        <p>Zenodo and the underlying Invenio Framework for digital repositories were designed according to the OAIS reference model. Full OAIS compliance can only be proven through ISO 16363 certification which is a recent standard with very few repositories worldwide certified to date. See our <a href="https://about.zenodo.org/infrastructure/">infrastructure page</a> for further details on Zenodo’s organizational and technical infrastructure.</p>
 
       </div>
     </div>
@@ -475,7 +475,7 @@ <h4 class="panel-title">
     </div>
     <div id="cpolicies-7" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hpolicies-7">
       <div class="panel-body">
-        <p>Not yet since CoreTrustSeal at the moment only certifies repositories that serve a specifically designated community and therefore not generalist repositories like Zenodo. CoreTrustSeal is considering including generalist repositories in CoreTrustSeal 2022, at which point we would apply for certification. We have provided our input to CoreTrustSeal’s request for community feedback on this issue.</p>
+        <p>Not yet, since CoreTrustSeal at the moment only certifies repositories that serve a specifically designated community and therefore not generalist repositories like Zenodo. CoreTrustSeal is considering including generalist repositories in CoreTrustSeal 2022, at which point we would apply for certification. We have provided our input to CoreTrustSeal’s request for community feedback on this issue.</p>
 
       </div>
     </div>
@@ -599,7 +599,7 @@ <h4 class="panel-title">
 <li><strong>Concept (all versions):</strong> 10.5281/zenodo.705645</li>
 </ul>
 <p>The first two DOIs for versions <strong>v1.0</strong> and <strong>v.1.1</strong> represent the specific versions of the software. The last DOI represents all the versions of the given software package, i.e. the concept of the software package and the ensemble of versions. We therefore also call the them <strong>Version DOIs</strong> and <strong>Concept DOIs</strong> (note, technically both are just normal DOIs).</p>
-<p>You may notice that the version DOIs do not include a “.v1”-suffix. Read below to find out why.</p>
+<p>You may notice that the version DOIs do not include a “.v1”-suffix. <a href="#cversioning-8">Read below</a> to find out why.</p>
 
       </div>
     </div>
@@ -650,8 +650,7 @@ <h4 class="panel-title">
       <div class="panel-body">
         <p>Yes. However, for uploads published before the 30th of May 2017, you have to first upgrade your record to support versioning. This is done by clicking the “Upgrade to versioned record” button on the record page.</p>
 <p>IMPORTANT
-If you have previously uploaded multiple versions of an upload as individual records on Zenodo, then DO NOT click the button to upgrade your record with versioning support. Please <a href="https://zenodo.org/support">contact us</a> so we can link the records under one versioning scheme.</p>
-<p>Clicking the “Upgrade to versioned record” button on any of the records you would like to link, will irreversibly register them as individually-versioned records.</p>
+If you have previously uploaded multiple versions of an upload as individual records on Zenodo, then DO NOT click the button to upgrade your record with versioning support. Please <a href="https://zenodo.org/support">contact us</a> so we can link the records under one versioning scheme. Clicking the “Upgrade to versioned record” button on any of the records you would like to link, will irreversibly register them as individually-versioned records.</p>
 <p>If you used the GitHub integration to archive your software on Zenodo, then we have already migrated and linked your records to support versioning.</p>
 
       </div>
@@ -684,7 +683,7 @@ <h4 class="panel-title">
     </div>
     <div id="cversioning-7" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hversioning-7">
       <div class="panel-body">
-        <p>No, as before you can continue to edit the metadata of your upload without creating a new version of a record. You should only create a new version if you want to update the files of your record.</p>
+        <p>No, you can continue to edit the metadata of your upload without creating a new version of a record. You should only create a new version if you want to update the files of your record.</p>
 
       </div>
     </div>
@@ -721,7 +720,7 @@ <h4 class="panel-title">
     </div>
     <div id="cversioning-9" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hversioning-9">
       <div class="panel-body">
-        <p>Currently DOIs registered by Zenodo follows the pattern “10.5281/zenodo.<integer>” where 10.5281 is the Zenodo DOI prefix and <integer> is a sequentially assigned integer. The word “zenodo” is semantic information, and as mentioned in the previous question it is a bad idea to include semantic information in DOIs as it may change over time. The current practice was introduced when Zenodo was launched in May 2013, and while it is not ideal we did not want to change the existing practice.</p>
+        <p>Currently DOIs registered by Zenodo follows the pattern “10.5281/zenodo.<integer>” where 10.5281 is the Zenodo DOI prefix and <integer> is a sequentially assigned integer. The word “zenodo” is semantic information and, as mentioned in the previous answer, it is a bad idea to include semantic information in DOIs as it may change over time. The current practice was introduced when Zenodo was launched in May 2013, and while it is not ideal we did not want to change the existing practice.</p>
 
       </div>
     </div>
@@ -737,7 +736,7 @@ <h4 class="panel-title">
     </div>
     <div id="cversioning-10" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hversioning-10">
       <div class="panel-body">
-        <p>No, if you change a 10kb README file in 50GB dataset we do not duplicate the entire 50GB dataset. Invenio v3, the underlying digital repository platform that powers Zenodo, efficiently handles the file storage so we only store the new extra 10kb.</p>
+        <p>No, if you change a 10kb README file in 50GB dataset we do not duplicate the entire 50GB dataset. <a href="https://inveniosoftware.org/products/framework/">Invenio v3</a>, the underlying digital repository platform that powers Zenodo, efficiently handles the file storage so we only store the new 10kb.</p>
 
       </div>
     </div>
@@ -1107,14 +1106,14 @@ <h4 class="panel-title">
     <div id="cstatistics-13" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hstatistics-13">
       <div class="panel-body">
         <p>For each view/download event, we track an anonymized visitor ID. This anonymized visitor ID changes for a user every 24 hours, hence a user viewing the same record on two different days will have two different anonymized visitor IDs. The reason we track an anonymized visitor ID is in order to count unique views and downloads.</p>
-<p>For security purposes, we also keep a web server access log which includes your <a href="https://en.wikipedia.org/wiki/IP_address">IP address</a> and your browser’s <a href="https://en.wikipedia.org/wiki/User_agent">user agent</a> string. This web server access log is automatically deleted after maximum 1 year and is also strictly separated from the usage statistics collection.</p>
+<p>For security purposes, we also keep a web server access log which includes your <a href="https://en.wikipedia.org/wiki/IP_address">IP address</a> and your browser’s <a href="https://en.wikipedia.org/wiki/User_agent">user agent</a> string. This web server access log is automatically deleted after 1 year max. and is also strictly separated from the usage statistics collection.</p>
 <p>The anonymized visitor ID is generated from a personal identifier such as:</p>
 <ol>
 <li>a user ID (e.g. if you are logged in on zenodo.org),</li>
 <li>a session ID,</li>
 <li>or an IP address and your browser’s user-agent string.</li>
 </ol>
-<p>We combine the personal identifier with a random text value (a salt) and apply a one-way <a href="https://en.wikipedia.org/wiki/Cryptographic_hash_function">cryptographic hash function</a> to scramble the data. The salt (random text value) is thrown away and regenerated every 24 hours. Using and afterwards throwing away the random salt, ensures that the anonymized visitor ID is fully random.</p>
+<p>We combine the personal identifier with a random text value (a salt) and apply a one-way <a href="https://en.wikipedia.org/wiki/Cryptographic_hash_function">cryptographic hash function</a> to scramble the data. The salt (random text value) is thrown away and regenerated every 24 hours. Using and discarding the random salt afterwards ensures that the anonymized visitor ID is fully random.</p>
 
       </div>
     </div>
@@ -1146,7 +1145,7 @@ <h4 class="panel-title">
     </div>
     <div id="cstatistics-15" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hstatistics-15">
       <div class="panel-body">
-        <p>We share <em>aggregated</em> usage statistics with <a href="https://usagecounts.openaire.eu/">OpenAIRE Usage Counts</a> as well as the <a href="https://github.com/datacite/sashimi">DataCite Sashimi</a> service. Note, that only aggregated usage statistics is being shared, whichdo not include any anonymized visitor IDs.</p>
+        <p>We share <em>aggregated</em> usage statistics with <a href="https://usagecounts.openaire.eu/">OpenAIRE Usage Counts</a> as well as the <a href="https://github.com/datacite/sashimi">DataCite Sashimi</a> service. Note, that only aggregated usage statistics are shared, which do not include any anonymized visitor IDs.</p>
 
       </div>
     </div>
@@ -1248,7 +1247,7 @@ <h4 class="panel-title">
     <div id="cgithub-1" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hgithub-1">
       <div class="panel-body">
         <p>In order to see and archive your organizational repositories on Zenodo you will need to have "Admin" permissions on said repository, either as an Admin of the organization or an Admin of one of your organization's repositories.
-Additionally, please make sure that the OAuth application on GitHub is granting permissions not only to your personal repositories but also to your organizational ones - to verify that go to your GitHub OAuth settings in <a href="https://github.com/settings/applications">your profile</a>, and click on the Zenodo application to see more details. Make sure that Zenodo is given access (green tick) to your organization under "Organization access".</p>
+Additionally, please make sure that the OAuth application on GitHub grants permissions not only to your personal repositories but also to your organizational ones: To verify go to your GitHub OAuth settings in <a href="https://github.com/settings/applications">your profile</a>, and click on the Zenodo application to see more details. Also ensure that Zenodo is given access (green tick) to your organization under "Organization access".</p>
 <p>After that, navigate to your Zenodo <a href="https://zenodo.org/account/settings/github/">GitHub settings page</a> and click the "Sync now" button at the top.</p>
 
       </div>
@@ -1265,7 +1264,7 @@ <h4 class="panel-title">
     </div>
     <div id="cgithub-2" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hgithub-2">
       <div class="panel-body">
-        <p>Make sure the repository was enabled before the release was made, otherwise feel free to contact us.</p>
+        <p>Make sure the repository was enabled before the release was made, otherwise feel free to <a href="https://zenodo.org/support">contact us</a>.</p>
 
       </div>
     </div>
@@ -1290,7 +1289,7 @@ <h4 class="panel-title">
     <div class="panel-heading" role="tab" id="hgithub-4">
       <h4 class="panel-title">
         <a role="button" data-toggle="collapse" data-parent="#accordion" href="#cgithub-4" aria-expanded="true" aria-controls="cgithub-4">
-          <p>How to change the default metadata for my GitHub releases?</p>
+          <p>How to change the default metadata for my GitHub release?</p>
 
         </a>
       </h4>
@@ -1384,7 +1383,7 @@ <h4 class="panel-title">
     </div>
     <div id="ccitations-3" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hcitations-3">
       <div class="panel-body">
-        <p>We display citations if available for all records in Zenodo.</p>
+        <p>We display citations, if available, for all records in Zenodo.</p>
 
       </div>
     </div>
@@ -1422,10 +1421,7 @@ <h4 class="panel-title">
     </div>
     <div id="ccitations-5" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hcitations-5">
       <div class="panel-body">
-        <p>Currently (January 2019) we primarily cover:</p>
-<ul>
-<li>Astronomy and astrophysics</li>
-</ul>
+        <p>Currently (January 2019) we primarily cover astronomy and astrophysics.</p>
 <p>We also receive citation data from cross-domain citation data sources, however often the coverage is not good as it relies on publishers to make the citation data freely available (which some big publishers do not do).</p>
 
       </div>
@@ -1592,7 +1588,7 @@ <h4 class="panel-title">
     </div>
     <div id="ccitations-15" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hcitations-15">
       <div class="panel-body">
-        <p>We usually receive citation data as a link between two persistent identifiers (e.g. "DOI A cites DOI B") without any metadata. We therefore have to automatically retrieve metadata such as title, authors and publication year from other services. This automatic fetching of metadata however is sometimes not able to find any available metadata, in which case we only display the persistent identifier.</p>
+        <p>We usually receive citation data as a link between two persistent identifiers (e.g. "DOI A cites DOI B") without any metadata. We therefore have to automatically retrieve metadata such as title, authors and publication year from other services. Sometimes this automatic fetching is not able to find any available metadata, in which case we only display the persistent identifier.</p>
 
       </div>
     </div>
diff --git a/faq/policies/index.html b/faq/policies/index.html
index 416f3b8..cbf1472 100644
--- a/faq/policies/index.html
+++ b/faq/policies/index.html
@@ -101,17 +101,18 @@ <h3 id="policies">Policies</h3>
     <div class="panel-heading" role="tab" id="hpolicies-1">
       <h4 class="panel-title">
         <a role="button" data-toggle="collapse" data-parent="#accordion" href="#cpolicies-1" aria-expanded="true" aria-controls="cpolicies-1">
-          <p>What are the size limits in Zenodo?</p>
+          <p>What are the size limits of Zenodo?</p>
 
         </a>
       </h4>
     </div>
     <div id="cpolicies-1" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hpolicies-1">
       <div class="panel-body">
-        <p>We currently accept up to 50GB per dataset (you can have multiple datasets); there is no size limit on the number of records in communities.
+        <p>We currently accept up to 50GB per dataset (you can have multiple datasets). 
 However, we don't want to turn away use cases for larger datasets.
 If you would like to upload larger files, please <a href="https://zenodo.org/support">contact us</a>, and we will do our best to help you.
 Please be aware that we cannot offer infinite space for free, so donations towards sustainability are encouraged.</p>
+<p>There are no size limit on the number of records in communities.</p>
 
       </div>
     </div>
@@ -146,7 +147,7 @@ <h4 class="panel-title">
     <div id="cpolicies-3" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hpolicies-3">
       <div class="panel-body">
         <p>Where data that was originally <a href="https://www.openaire.eu/sensitive-data-guide">sensitive personal data</a> is being uploaded for open dissemination through Zenodo, the uploader shall ensure that such data is either anonymised to an appropriate degree or fully consent cleared.
-There are several tools that can help uploaders to anonymise their data, being one of them OpenAIRE <a href="https://amnesia.openaire.eu">Amnesia</a>.</p>
+There are several tools that can help uploaders to anonymise their data such as OpenAIRE <a href="https://amnesia.openaire.eu">Amnesia</a>.</p>
 
       </div>
     </div>
@@ -173,17 +174,17 @@ <h4 class="panel-title">
     <div class="panel-heading" role="tab" id="hpolicies-5">
       <h4 class="panel-title">
         <a role="button" data-toggle="collapse" data-parent="#accordion" href="#cpolicies-5" aria-expanded="true" aria-controls="cpolicies-5">
-          <p>Is my data safe with you / What will happen to my uploads in the unlikely event that Zenodo has to close?</p>
+          <p>Is my data safe with you? What will happen to my uploads in the unlikely event that Zenodo has to close?</p>
 
         </a>
       </h4>
     </div>
     <div id="cpolicies-5" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hpolicies-5">
       <div class="panel-body">
-        <p>Yes, your data is stored in CERN Data Center.
+        <p>Yes, your data is safe as it is stored in the CERN Data Center.
 Both data files and metadata are kept in multiple online and independent replicas.
 CERN has considerable knowledge and experience in building and operating large scale digital repositories and a commitment to maintain this data centre to collect and store 100s of PBs of LHC data as it grows over the next 20 years.
-In the highly unlikely event that Zenodo will have to close operations, we guarantee that we will migrate all content to other suitable repositories, and since all uploads have DOIs, all citations and links to Zenodo resources (such as your data) will not be affected.</p>
+In the highly unlikely event that Zenodo will have to close operations, we guarantee that we will migrate all content to other suitable repositories. Since all uploads have DOIs, all citations and links to Zenodo resources (such as your data) will not be affected.</p>
 
       </div>
     </div>
@@ -199,7 +200,7 @@ <h4 class="panel-title">
     </div>
     <div id="cpolicies-6" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hpolicies-6">
       <div class="panel-body">
-        <p>Zenodo and the underlying Invenio Framework for digital repositories were designed according to the OAIS reference model. Full OAIS compliance can only be proven through ISO 16363 certification which is a recent standard with very few repositories worldwide certified to date. See our infrastructure page for further details on Zenodo’s organizational and technical infrastructure.</p>
+        <p>Zenodo and the underlying Invenio Framework for digital repositories were designed according to the OAIS reference model. Full OAIS compliance can only be proven through ISO 16363 certification which is a recent standard with very few repositories worldwide certified to date. See our <a href="https://about.zenodo.org/infrastructure/">infrastructure page</a> for further details on Zenodo’s organizational and technical infrastructure.</p>
 
       </div>
     </div>
@@ -215,7 +216,7 @@ <h4 class="panel-title">
     </div>
     <div id="cpolicies-7" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hpolicies-7">
       <div class="panel-body">
-        <p>Not yet since CoreTrustSeal at the moment only certifies repositories that serve a specifically designated community and therefore not generalist repositories like Zenodo. CoreTrustSeal is considering including generalist repositories in CoreTrustSeal 2022, at which point we would apply for certification. We have provided our input to CoreTrustSeal’s request for community feedback on this issue.</p>
+        <p>Not yet, since CoreTrustSeal at the moment only certifies repositories that serve a specifically designated community and therefore not generalist repositories like Zenodo. CoreTrustSeal is considering including generalist repositories in CoreTrustSeal 2022, at which point we would apply for certification. We have provided our input to CoreTrustSeal’s request for community feedback on this issue.</p>
 
       </div>
     </div>
diff --git a/faq/statistics/index.html b/faq/statistics/index.html
index 11fa3fa..b68e9a8 100644
--- a/faq/statistics/index.html
+++ b/faq/statistics/index.html
@@ -312,14 +312,14 @@ <h4 class="panel-title">
     <div id="cstatistics-13" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hstatistics-13">
       <div class="panel-body">
         <p>For each view/download event, we track an anonymized visitor ID. This anonymized visitor ID changes for a user every 24 hours, hence a user viewing the same record on two different days will have two different anonymized visitor IDs. The reason we track an anonymized visitor ID is in order to count unique views and downloads.</p>
-<p>For security purposes, we also keep a web server access log which includes your <a href="https://en.wikipedia.org/wiki/IP_address">IP address</a> and your browser’s <a href="https://en.wikipedia.org/wiki/User_agent">user agent</a> string. This web server access log is automatically deleted after maximum 1 year and is also strictly separated from the usage statistics collection.</p>
+<p>For security purposes, we also keep a web server access log which includes your <a href="https://en.wikipedia.org/wiki/IP_address">IP address</a> and your browser’s <a href="https://en.wikipedia.org/wiki/User_agent">user agent</a> string. This web server access log is automatically deleted after 1 year max. and is also strictly separated from the usage statistics collection.</p>
 <p>The anonymized visitor ID is generated from a personal identifier such as:</p>
 <ol>
 <li>a user ID (e.g. if you are logged in on zenodo.org),</li>
 <li>a session ID,</li>
 <li>or an IP address and your browser’s user-agent string.</li>
 </ol>
-<p>We combine the personal identifier with a random text value (a salt) and apply a one-way <a href="https://en.wikipedia.org/wiki/Cryptographic_hash_function">cryptographic hash function</a> to scramble the data. The salt (random text value) is thrown away and regenerated every 24 hours. Using and afterwards throwing away the random salt, ensures that the anonymized visitor ID is fully random.</p>
+<p>We combine the personal identifier with a random text value (a salt) and apply a one-way <a href="https://en.wikipedia.org/wiki/Cryptographic_hash_function">cryptographic hash function</a> to scramble the data. The salt (random text value) is thrown away and regenerated every 24 hours. Using and discarding the random salt afterwards ensures that the anonymized visitor ID is fully random.</p>
 
       </div>
     </div>
@@ -351,7 +351,7 @@ <h4 class="panel-title">
     </div>
     <div id="cstatistics-15" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hstatistics-15">
       <div class="panel-body">
-        <p>We share <em>aggregated</em> usage statistics with <a href="https://usagecounts.openaire.eu/">OpenAIRE Usage Counts</a> as well as the <a href="https://github.com/datacite/sashimi">DataCite Sashimi</a> service. Note, that only aggregated usage statistics is being shared, whichdo not include any anonymized visitor IDs.</p>
+        <p>We share <em>aggregated</em> usage statistics with <a href="https://usagecounts.openaire.eu/">OpenAIRE Usage Counts</a> as well as the <a href="https://github.com/datacite/sashimi">DataCite Sashimi</a> service. Note, that only aggregated usage statistics are shared, which do not include any anonymized visitor IDs.</p>
 
       </div>
     </div>
diff --git a/faq/technical/index.html b/faq/technical/index.html
index 135dccd..08a202c 100644
--- a/faq/technical/index.html
+++ b/faq/technical/index.html
@@ -117,7 +117,7 @@ <h4 class="panel-title">
     <div class="panel-heading" role="tab" id="htechnical-2">
       <h4 class="panel-title">
         <a role="button" data-toggle="collapse" data-parent="#accordion" href="#ctechnical-2" aria-expanded="true" aria-controls="ctechnical-2">
-          <p>Why am I getting an error when trying to upload my files?</p>
+          <p>Why am I getting an error when trying to upload files?</p>
 
         </a>
       </h4>
diff --git a/faq/versioning/index.html b/faq/versioning/index.html
index d03a38c..78a7103 100644
--- a/faq/versioning/index.html
+++ b/faq/versioning/index.html
@@ -142,7 +142,7 @@ <h4 class="panel-title">
 <li><strong>Concept (all versions):</strong> 10.5281/zenodo.705645</li>
 </ul>
 <p>The first two DOIs for versions <strong>v1.0</strong> and <strong>v.1.1</strong> represent the specific versions of the software. The last DOI represents all the versions of the given software package, i.e. the concept of the software package and the ensemble of versions. We therefore also call the them <strong>Version DOIs</strong> and <strong>Concept DOIs</strong> (note, technically both are just normal DOIs).</p>
-<p>You may notice that the version DOIs do not include a “.v1”-suffix. Read below to find out why.</p>
+<p>You may notice that the version DOIs do not include a “.v1”-suffix. <a href="../#cversioning-8">Read below</a> to find out why.</p>
 
       </div>
     </div>
@@ -193,8 +193,7 @@ <h4 class="panel-title">
       <div class="panel-body">
         <p>Yes. However, for uploads published before the 30th of May 2017, you have to first upgrade your record to support versioning. This is done by clicking the “Upgrade to versioned record” button on the record page.</p>
 <p>IMPORTANT
-If you have previously uploaded multiple versions of an upload as individual records on Zenodo, then DO NOT click the button to upgrade your record with versioning support. Please <a href="https://zenodo.org/support">contact us</a> so we can link the records under one versioning scheme.</p>
-<p>Clicking the “Upgrade to versioned record” button on any of the records you would like to link, will irreversibly register them as individually-versioned records.</p>
+If you have previously uploaded multiple versions of an upload as individual records on Zenodo, then DO NOT click the button to upgrade your record with versioning support. Please <a href="https://zenodo.org/support">contact us</a> so we can link the records under one versioning scheme. Clicking the “Upgrade to versioned record” button on any of the records you would like to link, will irreversibly register them as individually-versioned records.</p>
 <p>If you used the GitHub integration to archive your software on Zenodo, then we have already migrated and linked your records to support versioning.</p>
 
       </div>
@@ -227,7 +226,7 @@ <h4 class="panel-title">
     </div>
     <div id="cversioning-7" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hversioning-7">
       <div class="panel-body">
-        <p>No, as before you can continue to edit the metadata of your upload without creating a new version of a record. You should only create a new version if you want to update the files of your record.</p>
+        <p>No, you can continue to edit the metadata of your upload without creating a new version of a record. You should only create a new version if you want to update the files of your record.</p>
 
       </div>
     </div>
@@ -264,7 +263,7 @@ <h4 class="panel-title">
     </div>
     <div id="cversioning-9" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hversioning-9">
       <div class="panel-body">
-        <p>Currently DOIs registered by Zenodo follows the pattern “10.5281/zenodo.<integer>” where 10.5281 is the Zenodo DOI prefix and <integer> is a sequentially assigned integer. The word “zenodo” is semantic information, and as mentioned in the previous question it is a bad idea to include semantic information in DOIs as it may change over time. The current practice was introduced when Zenodo was launched in May 2013, and while it is not ideal we did not want to change the existing practice.</p>
+        <p>Currently DOIs registered by Zenodo follows the pattern “10.5281/zenodo.<integer>” where 10.5281 is the Zenodo DOI prefix and <integer> is a sequentially assigned integer. The word “zenodo” is semantic information and, as mentioned in the previous answer, it is a bad idea to include semantic information in DOIs as it may change over time. The current practice was introduced when Zenodo was launched in May 2013, and while it is not ideal we did not want to change the existing practice.</p>
 
       </div>
     </div>
@@ -280,7 +279,7 @@ <h4 class="panel-title">
     </div>
     <div id="cversioning-10" class="panel-collapse collapse out" role="tabpanel" aria-labelledby="hversioning-10">
       <div class="panel-body">
-        <p>No, if you change a 10kb README file in 50GB dataset we do not duplicate the entire 50GB dataset. Invenio v3, the underlying digital repository platform that powers Zenodo, efficiently handles the file storage so we only store the new extra 10kb.</p>
+        <p>No, if you change a 10kb README file in 50GB dataset we do not duplicate the entire 50GB dataset. <a href="https://inveniosoftware.org/products/framework/">Invenio v3</a>, the underlying digital repository platform that powers Zenodo, efficiently handles the file storage so we only store the new 10kb.</p>
 
       </div>
     </div>