fix

Rich-Harris · Rich-Harris · commit 5bea390dfdf0 · 2022-06-24T10:44:26.000-04:00
diff --git a/.gitattributes b/.gitattributes
@@ -1 +1,2 @@
-* text eol=lf
+* text=auto eol=lf
+*.gif binary
diff --git a/content/tutorial/01-svelte/01-introduction/03-dynamic-attributes/app-a/static/image.gif b/content/tutorial/01-svelte/01-introduction/03-dynamic-attributes/app-a/static/image.gif
diff --git a/content/tutorial/02-sveltekit/01-concepts/02-project-structure/README.md b/content/tutorial/02-sveltekit/01-concepts/02-project-structure/README.md
@@ -10,6 +10,6 @@ On the right, in the file tree viewer, you'll see a handful of files that Svelte
 
 `svelte.config.js` contains your project configuration. We don't need to worry about this file for now, but if you're curious, [visit the documentation](https://kit.svelte.dev/docs/configuration).
 
-`src` is where your app's source code goes. `src/app.html` is your page template (SvelteKit replaces the `%sveltekit.head%` and `%sveltekit.body%` as appropriate), and `src/routes` defines the [routes](/tutorial/filesystem-based-routing) of your app.
+`src` is where your app's source code goes. `src/app.html` is your page template (SvelteKit replaces the `%sveltekit.head%` and `%sveltekit.body%` as appropriate), and `src/routes` defines the [routes](/tutorial/pages) of your app.
 
 Finally, `static` contains any assets (like a `favicon.png` or a `robots.txt`) that should be included when your app is deployed.
