Fix typos

CONTRIBUTING.md

@@ -8,7 +8,7 @@ However, if you notice an error or typo in the documentation, feel free to direc
 If you want a feature added or modified, please open a thread on the [forum](https://zola.discourse.group/) to discuss it before doing a PR.
 
 Requested features will not be all added: an ever-increasing features set makes for a hard to use and explain softwares.
-Having something simple and easy to use for 90% of the usecases is more interesting than covering 100% usecases after sacrificing simplicity.
+Having something simple and easy to use for 90% of the use cases is more interesting than covering 100% use cases after sacrificing simplicity.
 
 ## Issues tagging
 

README.md

@@ -17,7 +17,7 @@ Hugo that I was using before for 6+ sites.
 - [Syntax highlighting](https://www.getzola.org/documentation/content/syntax-highlighting/)
 - [Sass compilation](https://www.getzola.org/documentation/content/sass/)
 - Assets co-location
-- [Multilingual site suport](https://www.getzola.org/documentation/content/multilingual/) (Basic currently)
+- [Multilingual site support](https://www.getzola.org/documentation/content/multilingual/) (Basic currently)
 - [Image processing](https://www.getzola.org/documentation/content/image-processing/)
 - [Themes](https://www.getzola.org/documentation/themes/overview/)
 - [Shortcodes](https://www.getzola.org/documentation/content/shortcodes/)

components/config/src/config/search.rs

@@ -43,7 +43,7 @@ pub struct Search {
     pub include_date: bool,
     /// Include the path of the page in the search index. `false` by default.
     pub include_path: bool,
-    /// Foramt of the search index to be produced. 'elasticlunr_javascript' by default.
+    /// Format of the search index to be produced. 'elasticlunr_javascript' by default.
     pub index_format: IndexFormat,
 }
 

components/content/src/page.rs

@@ -548,7 +548,7 @@ And here's another. [^3]
 
 [^1]: This is the first footnote.
 
-[^2]: This is the secund footnote.
+[^2]: This is the second footnote.
 
 [^3]: This is the third footnote."#
             .to_string();

components/utils/src/site.rs

@@ -88,7 +88,7 @@ mod tests {
     }
 
     #[test]
-    fn errors_resolve_inexistant_internal_link() {
+    fn errors_resolve_inexistent_internal_link() {
         let res = resolve_internal_link("@/pages/about.md#hello", &HashMap::new());
         assert!(res.is_err());
     }

components/utils/src/templates.rs

@@ -186,7 +186,7 @@ mod tests {
         // Check finding existing template
         assert_eq!(check_template_fallbacks("index.html", &tera, &None), Some("index.html"));
 
-        // Check trying to find non-existant template
+        // Check trying to find non-existent template
         assert_eq!(check_template_fallbacks("not-here.html", &tera, &None), None);
 
         // Check theme fallback

docs/content/documentation/content/shortcodes.md

@@ -73,7 +73,7 @@ In both cases, the arguments must be named and they will all be passed to the te
 Parentheses are mandatory even if there are no arguments.
 
 Note that while shortcodes look like normal Tera expressions, they are not Tera at all -- they can
-pretty much just shuttle arguments to their template. Several limitions of note are:
+pretty much just shuttle arguments to their template. Several limitations of note are:
 
 - All arguments are required
 - The shortcode cannot reference Tera variables
@@ -208,7 +208,7 @@ This is useful for presenting/filtering information in a shortcode depending in
 ```
 
 ### `page` or `section`
-You can access a slighty stripped down version of the equivalent variables in the normal templates.
+You can access a slightly stripped down version of the equivalent variables in the normal templates.
 The following attributes will be empty:
 
 - translations

docs/content/documentation/deployment/aws-s3.md

@@ -57,7 +57,7 @@ Under **Repository secrets** click **Add repository secret**. In the *Name* fiel
 
 ## GitHub Actions
 
-Next we need to create the *Github Action* to build and deploy our files to S3. We need to create a workflow file in `.github/workflows` directory of our repository. This can be done by navigating to the *Actions* tab in GitHub or by commiting the file from your machine.
+Next we need to create the *Github Action* to build and deploy our files to S3. We need to create a workflow file in `.github/workflows` directory of our repository. This can be done by navigating to the *Actions* tab in GitHub or by committing the file from your machine.
 
 `.github/workflows/publish.yml`:
 

docs/content/documentation/getting-started/configuration.md

@@ -188,7 +188,7 @@ include_content = true
 # become too big to load on the site. Defaults to not being set.
 # truncate_content_length = 100
 
-# Wether to produce the search index as a javascript file or as a JSON file
+# Whether to produce the search index as a javascript file or as a JSON file
 # Accepted values:
 # - "elasticlunr_javascript", "elasticlunr_json"
 # - "fuse_javascript", "fuse_json"