From 5b399b7d0a611cb82e544acc212e8456b1186f26 Mon Sep 17 00:00:00 2001
From: lnielsen <lnielsen@users.noreply.github.com>
Date: Tue, 26 Mar 2024 10:35:01 +0000
Subject: [PATCH] deploy: 8c7f3b32cf711ddb6cb7536f8a9843f4f8873d86

---
 CNAME      | 2 +-
 index.html | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/CNAME b/CNAME
index 6375e7c..5864d79 100644
--- a/CNAME
+++ b/CNAME
@@ -1 +1 @@
-developers.zenodo.org
\ No newline at end of file
+developers.zenodo.org
diff --git a/index.html b/index.html
index 82d915e..9f0933d 100644
--- a/index.html
+++ b/index.html
@@ -2296,7 +2296,7 @@ <h2 id="add-metadata-to-your-github-repository-release">Add metadata to your Git
 </code></pre>
 <p>We automatically extract metadata about your release from GitHub APIs. For example, the authors are determined from the repository&rsquo;s contributor statistics. To overwrite some of the default metadata that would come from a regular GitHub release you can include a <code class="prettyprint">.zenodo.json</code> file at the root of your GitHub repository.</p>
 
-<p>The contents of the <code class="prettyprint">.zenodo.json</code> file are based on our <a href="https://developers.zenodo.org/#deposit-metadata">deposit metadata documentation</a> and can be structurally validated by our <a href="https://zenodo.org/schemas/deposits/records/legacyrecord.json">deposit JSON Schema</a>.</p>
+<p>The contents of the <code class="prettyprint">.zenodo.json</code> file are based on our <a href="https://developers.zenodo.org/#deposit-metadata">deposit metadata documentation</a> and can be structurally validated using our <a href="https://github.com/zenodo/zenodo/blob/master/zenodo/modules/deposit/jsonschemas/deposits/records/legacyrecord.json">legacy deposit JSON Schema</a>.</p>
 
 <p>In the example shown, we add metadata regarding:</p>