From 0a01df18857c90575d36c1b8f713d64d8544c9e6 Mon Sep 17 00:00:00 2001 From: Robert Kaussow Date: Tue, 30 Aug 2022 21:41:03 +0200 Subject: [PATCH] docs: fix spelling and grammar (#303) --- exampleSite/content/posts/features/theming/index.md | 4 ++-- exampleSite/content/posts/usage/getting-started.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/exampleSite/content/posts/features/theming/index.md b/exampleSite/content/posts/features/theming/index.md index 3ef0e14..a15aedb 100644 --- a/exampleSite/content/posts/features/theming/index.md +++ b/exampleSite/content/posts/features/theming/index.md @@ -28,7 +28,7 @@ All the necessary CSS customization properties are listed below. If you want to ## Favicons -The Theme is shipped with a set of default Favicons in various formats generated by a [Favicon Generator](https://realfavicongenerator.net/). All files can be found in the `static/favicon` folder of the release tarball. To make the replacement of the default Favicons as simple as possible, the theme loads only a very small subset of the Favicon formats. +The Theme is shipped with a set of default Favicons in various formats generated by the [Favicon Generator](https://realfavicongenerator.net/). All files can be found in the `static/favicon` folder of the release tarball. To make the replacement of the default Favicons as simple as possible, the theme loads only a very small subset of the Favicon formats. ```tpl @@ -39,7 +39,7 @@ The Theme is shipped with a set of default Favicons in various formats generated ### Simple replacement -The minimal steps to load a custom Favicon is to overwrite tree default Favicon files. Therefor place these files into your projects root folder: +The minimal steps to load a custom Favicon is to overwrite the three default Favicon files. Therefor place these files into your projects root folder: - `static/favicon/favicon.svg` - `static/favicon/favicon-32x32.png` diff --git a/exampleSite/content/posts/usage/getting-started.md b/exampleSite/content/posts/usage/getting-started.md index e426c74..f37668c 100644 --- a/exampleSite/content/posts/usage/getting-started.md +++ b/exampleSite/content/posts/usage/getting-started.md @@ -219,7 +219,7 @@ As deploying Hugo sites on subdirectories is not as robust as on subdomains, we If you have a choice, using a domain/subdomain should always be the preferred solution! {{< /hint >}} -If you want to deploy your side to a subdirectory of your domain, some extra steps are required: +If you want to deploy your site to a subdirectory of your domain, some extra steps are required: - Configure your Hugo base URL e.g. `baseURL = http://localhost/demo/`. - Don't use `relativeURLs: false` nor `canonifyURLs: true` as is can cause unwanted side effects!