doc updates

benmccann · benmccann · commit efd5fb75cdc9 · 2021-10-21T08:49:06.000-07:00
diff --git a/documentation/docs/01-routing.md b/documentation/docs/01-routing.md
@@ -130,8 +130,6 @@ The job of this function is to return a `{ status, headers, body }` object repre
 - `4xx` — client error
 - `5xx` — server error
 
-> For successful responses, SvelteKit will generate 304s automatically.
-
 If the returned `body` is an object, and no `content-type` header is returned, it will automatically be turned into a JSON response. (Don't worry about `$lib`, we'll get to that [later](#modules-$lib).)
 
 > Returning nothing is equivalent to an explicit 404 response.
diff --git a/documentation/docs/07-a-options.md b/documentation/docs/07-a-options.md
@@ -34,7 +34,7 @@ In certain cases, you may wish to disable this behaviour. Adding a `sveltekit:no
 
 ### rel=external
 
-By default, the SvelteKit runtime intercepts clicks on `<a>` elements and bypasses the normal browser navigation for relative (same-origin) URLs that match one of your page routes. We sometimes need to tell SvelteKit that certain links need to be handled by normal browser navigation.
+By default, the SvelteKit runtime intercepts clicks on `<a>` elements and bypasses the normal browser navigation for relative (same-origin) URLs that match one of your page routes. We sometimes need to tell SvelteKit that certain links need to be handled by normal browser navigation. Examples of this might be linking to another page on your domain that's not part of your SvelteKit app or linking to an endpoint.
 
 Adding a `rel=external` attribute to a link...
 
