From cbae535cad6790b60affc5391d3cab194701ee65 Mon Sep 17 00:00:00 2001 From: mundry <1453314+mundry@users.noreply.github.com> Date: Thu, 12 Aug 2021 20:24:06 +0200 Subject: [PATCH] Fix typos in the docs/ content (#1093) Co-authored-by: mundry --- docs/src/pages/core-concepts/routing.md | 2 +- docs/src/pages/de/getting-started.md | 4 ++-- docs/src/pages/guides/deploy.md | 6 +++--- docs/src/pages/guides/rss.md | 2 +- docs/src/pages/guides/styling.md | 4 ++-- docs/src/pages/installation.md | 6 +++--- docs/src/pages/reference/api-reference.md | 2 +- docs/src/pages/reference/renderer-reference.md | 2 +- 8 files changed, 14 insertions(+), 14 deletions(-) diff --git a/docs/src/pages/core-concepts/routing.md b/docs/src/pages/core-concepts/routing.md index 42ed0d35df..be86d94740 100644 --- a/docs/src/pages/core-concepts/routing.md +++ b/docs/src/pages/core-concepts/routing.md @@ -7,7 +7,7 @@ Astro uses **file-based routing** to generate your build URLs based on the file ## Static routes -Astro Components (`.astro`) and Markdown Files (`.md`) in the `src/pages` directory become pages on your website. Each page's route is decided based on it's filename and path within the `src/pages` directory. This means that there is no separate "routing config" to maintain in an Astro project. +Astro Components (`.astro`) and Markdown Files (`.md`) in the `src/pages` directory become pages on your website. Each page's route is decided based on its filename and path within the `src/pages` directory. This means that there is no separate "routing config" to maintain in an Astro project. ```bash # Example: Static routes diff --git a/docs/src/pages/de/getting-started.md b/docs/src/pages/de/getting-started.md index f953d50caa..70553a9566 100644 --- a/docs/src/pages/de/getting-started.md +++ b/docs/src/pages/de/getting-started.md @@ -32,7 +32,7 @@ Es kommen eine Menge verschiedener Menschen mit unterschiedlichen Hintergründen - Falls du lieber **theoretisch lernst**, kannst du mit unseren [grundlegenden Konzepten und Anleitungen](/core-concepts/project-structure) anfangen. -Wie alle unbekannten Technologien, hat auch Astro einen leichte Lernkurve. Mit ein bisschen Übung und Geduld, sind wir aber _sicher_, dass du schnell lernst, wie du mit Astro umgehen kannst. +Wie alle unbekannten Technologien, hat auch Astro eine leichte Lernkurve. Mit ein bisschen Übung und Geduld, sind wir aber _sicher_, dass du schnell lernst, wie du mit Astro umgehen kannst. ### Lerne die `.astro` Syntax @@ -56,7 +56,7 @@ Unser [@astrodotbuild](https://twitter.com/astrodotbuild) Twitter Account ist di Zusätzlich veröffentlichen wir alle Release Ankündigungen in unserer [Discord Community](https://astro.build/chat) im `#announcements` Kanal. -Obwohl nicht jeder Astro Release einenen eigenen Blogpost verdient, kannst du alle Änderungen für jedes Release in unserem detaillierten [`CHANGELOG.md` im Astro Repository](https://github.com/snowpackjs/astro/blob/main/packages/astro/CHANGELOG.md) nachlesen. +Obwohl nicht jeder Astro Release einen eigenen Blogpost verdient, kannst du alle Änderungen für jedes Release in unserem detaillierten [`CHANGELOG.md` im Astro Repository](https://github.com/snowpackjs/astro/blob/main/packages/astro/CHANGELOG.md) nachlesen. ## Fehlt etwas? diff --git a/docs/src/pages/guides/deploy.md b/docs/src/pages/guides/deploy.md index de11619456..de8aa69b6e 100644 --- a/docs/src/pages/guides/deploy.md +++ b/docs/src/pages/guides/deploy.md @@ -68,15 +68,15 @@ By default, the build output will be placed at `dist/`. You may deploy this `dis ### GitHub Actions -1. In the astro project repo, create `gh-pages` branch then go to Settings > Pages and set to `gh-pages` branch for Github Pages and set directory to `/` (root). +1. In the astro project repo, create `gh-pages` branch then go to Settings > Pages and set to `gh-pages` branch for GitHub Pages and set directory to `/` (root). 2. Set the correct `buildOptions.site` in `astro.config.mjs`. 3. Create the file `.github/workflows/main.yml` and add in the yaml below. Make sure to edit in your own details. -4. In Github go to Settings > Developer settings > Personal Access tokens. Generate a new token with repo permissions. +4. In GitHub go to Settings > Developer settings > Personal Access tokens. Generate a new token with repo permissions. 5. In the astro project repo (not \.github.io) go to Settings > Secrets and add your new personal access token with the name `API_TOKEN_GITHUB`. 6. When you push changes to the astro project repo CI will deploy them to \.github.io for you. ```yaml -# Workflow to build and deploy to your Github Pages repo. +# Workflow to build and deploy to your GitHub Pages repo. # Edit your project details here. # Remember to add API_TOKEN_GITHUB in repo Settings > Secrets as well! diff --git a/docs/src/pages/guides/rss.md b/docs/src/pages/guides/rss.md index d4ac14d5f6..3c98db6614 100644 --- a/docs/src/pages/guides/rss.md +++ b/docs/src/pages/guides/rss.md @@ -5,7 +5,7 @@ title: RSS Astro supports fast, automatic RSS feed generation for blogs and other content websites. -You can create an RSS feed from any Astro page that uses a `getStaticPaths()` function for routing. Only dynamic routes can use `getStaticPaths()` today (see [Routing](/core-concepts/routing). +You can create an RSS feed from any Astro page that uses a `getStaticPaths()` function for routing. Only dynamic routes can use `getStaticPaths()` today (see [Routing](/core-concepts/routing)). > We hope to make this feature available to all other pages before v1.0. As a workaround, you can convert a static route to a dynamic route that only generates a single page. See [Routing](/core-concepts/routing) for more information about dynamic routes. diff --git a/docs/src/pages/guides/styling.md b/docs/src/pages/guides/styling.md index ed1ebc1f64..bdeb3a22ff 100644 --- a/docs/src/pages/guides/styling.md +++ b/docs/src/pages/guides/styling.md @@ -272,7 +272,7 @@ import Button from './Button.astro'; ``` -This is undesirable because now `