github/hugo-geekblog
0
0
Fork 0
mirror of https://github.com/thegeeklab/hugo-geekblog.git synced 2024-11-14 01:00:41 +00:00
Code Issues Projects Releases Wiki Activity

docs: fix spelling and grammar (#303)

Browse Source
This commit is contained in:
Robert Kaussow 2022-08-30 21:41:03 +02:00 committed by GitHub
parent fbfaec50b6
commit 0a01df1885
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
exampleSite/content/posts/features/theming/index.md
View File

@ -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.
<!-- prettier-ignore -->
```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`

2
exampleSite/content/posts/usage/getting-started.md
View File

@ -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!