From a18cae36f2a33ae7253d5fde097147f5a079d762 Mon Sep 17 00:00:00 2001
From: Shay Bagants <shayb@jfrog.com>
Date: Sun, 20 Dec 2020 21:43:27 +0200
Subject: [PATCH] Fixing broken content negotiation link in spec.md

Signed-off-by: Shay Bagants <shayb@jfrog.com>
---
 spec.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec.md b/spec.md
index 1b2a6a5d..83266e50 100644
--- a/spec.md
+++ b/spec.md
@@ -144,7 +144,7 @@ The `<reference>` MUST NOT be in any other format. Throughout this document, `<n
 
 The client SHOULD include an `Accept` header indicating which manifest content types it supports.
 In a successful response, the `Content-Type` header will indicate the type of the returned manifest.
-For more information on the use of `Accept` headers and content negotiation, please see [Content Negotiation](./content-negortiation.md)
+For more information on the use of `Accept` headers and content negotiation, please see [Content Negotiation](./content-negotiation.md)
 
 A GET request to an existing manifest URL MUST provide the expected manifest, with a response code that MUST be `200 OK`.
 A successful response SHOULD contain the digest of the uploaded blob in the header `Docker-Content-Digest`.