diff --git a/pages/version/1.markdown b/pages/version/1.markdown
index e713f927e..0d6c8669a 100644
--- a/pages/version/1.markdown
+++ b/pages/version/1.markdown
@@ -175,7 +175,7 @@ In future versions, defined keys will always adhere to these rules:
 
 ## Suggestions for Publishers
 
-JSON Feed files must be served using the same MIME type — `application/json` — that’s used whenever JSON is served.
+JSON Feed files must be served using the MIME type `application/feed+json`.
 
 The number of items in a feed is unlimited, but practical limits should be observed. A 1MB feed places a burden on feed readers, especially if there are many such feeds. Under 100K is ideal, and 250K is fine. Use your judgment. If you need to provide older items, consider using pagination and `next_url`.
 
@@ -209,7 +209,7 @@ On the issue of which URL to use — `url` or `external_url` — when opening a
 
 A web page should include a `link` tag that specifies the location of the JSON Feed. Like this:
 
-	<link rel="alternate" title="My Feed" type="application/json" href="https://example.org/feed.json" />
+	<link rel="alternate" title="My Feed" type="application/feed+json" href="https://example.org/feed.json" />
 
 This is the same as the feed discovery mechanism used for RSS and Atom.