Updating status code references

content/tutorial/01-svelte/common/src/routes/+error.svelte

@@ -11,7 +11,7 @@
 		code
 		<a
 			target="_blank"
-			href="https://httpstatusdogs.com/{$page.status}"
+			href="https://http.dog/{$page.status}"
 			>{$page.status}</a
 		>
 	</p>

content/tutorial/02-advanced-svelte/common/src/routes/+error.svelte

@@ -11,7 +11,7 @@
 		code
 		<a
 			target="_blank"
-			href="https://httpstatusdogs.com/{$page.status}"
+			href="https://http.dog/{$page.status}"
 			>{$page.status}</a
 		>
 	</p>

content/tutorial/03-sveltekit/07-api-routes/02-post-handlers/README.md

@@ -51,7 +51,7 @@ export async function POST({ request, cookies }) {
 
 As with `load` functions and form actions, the `request` is a standard [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object; `await request.json()` returns the data that we posted from the event handler.
 
-We're returning a response with a [201 Created](https://httpstatusdogs.com/201-created) status and the `id` of the newly generated todo in our database. Back in the event handler, we can use this to update the page:
+We're returning a response with a [201 Created](https://http.dog/201) status and the `id` of the newly generated todo in our database. Back in the event handler, we can use this to update the page:
 
 ```svelte
 /// file: src/routes/+page.svelte

content/tutorial/03-sveltekit/07-api-routes/03-other-handlers/README.md

@@ -24,7 +24,7 @@ export async function DELETE({ params, cookies }) {
 }
 ```
 
-Since we don't need to return any actual data to the browser, we're returning an empty [Response](https://developer.mozilla.org/en-US/docs/Web/API/Response) with a [204 No Content](https://httpstatusdogs.com/204-no-content) status.
+Since we don't need to return any actual data to the browser, we're returning an empty [Response](https://developer.mozilla.org/en-US/docs/Web/API/Response) with a [204 No Content](https://http.dog/204) status.
 
 We can now interact with this endpoint inside our event handlers: