CloudCannon · bglw · Sep 19, 2023 · Sep 16, 2023 · Sep 19, 2023
diff --git a/docs/content/docs/filtering.md b/docs/content/docs/filtering.md
@@ -5,7 +5,7 @@ nav_section: Filtering
 weight: 10
 ---
 
-To configure filters in Pagefind, pages are assocated to filter keys and values using data attributes.
+To configure filters in Pagefind, pages are associated to filter keys and values using data attributes.
 
 ## Capturing a filter value from an element
 
@@ -68,7 +68,7 @@ This will tag this page as `author: ["CloudCannon"]`. The element this is set on
 
 ## Specifying multiple filters on a single element
 
-Filter captures may be comma seperated and all will apply. The exception is specifying a filter inline, which may only be the last item in a list.
+Filter captures may be comma separated and all will apply. The exception is specifying a filter inline, which may only be the last item in a list.
 
 For example:
 

diff --git a/docs/content/docs/metadata.md b/docs/content/docs/metadata.md
@@ -65,7 +65,7 @@ This will give this page the metadata `date: "2022-06-01"`. The element this is
 
 ## Defining multiple metadata keys on a single element
 
-Metadata captures may be comma seperated and all will apply. The exception is specifying metadata inline, which may only be the last item in a list.
+Metadata captures may be comma separated and all will apply. The exception is specifying metadata inline, which may only be the last item in a list.
 
 Usage:
 

diff --git a/docs/content/docs/node-api.md b/docs/content/docs/node-api.md
@@ -41,7 +41,7 @@ await index.writeFiles({
 });
 ```
 
-All interations with Pagefind are asynchronous, as they communicate with the native Pagefind binary in the background.
+All interactions with Pagefind are asynchronous, as they communicate with the native Pagefind binary in the background.
 
 ## pagefind.createIndex
 

diff --git a/docs/content/docs/sorts.md b/docs/content/docs/sorts.md
@@ -41,7 +41,7 @@ This will tag this page as `date: 2022-06-01`. The element this is set on does n
 
 ## Specifying multiple sorts on a single element
 
-Sort captures may be comma seperated and all will apply. The exception is specifying a sort value inline, which may only be the last item in a list.
+Sort captures may be comma separated and all will apply. The exception is specifying a sort value inline, which may only be the last item in a list.
 
 For example:
 

diff --git a/docs/content/docs/ui-usage.md b/docs/content/docs/ui-usage.md
@@ -63,7 +63,7 @@ The classnames within Pagefind UI that begin with `pagefind-ui` should be target
 
 ## Using custom Pagefind UI strings
 
-Pagefind UI will attempt to use translated text based on the language tag of the active page. If built in tanslations are not found, the UI will fall back to English text. Custom text can instead be supplied using the [translations](/docs/ui/#translations) option.
+Pagefind UI will attempt to use translated text based on the language tag of the active page. If built in translations are not found, the UI will fall back to English text. Custom text can instead be supplied using the [translations](/docs/ui/#translations) option.
 
 Languages with built in translations are listed in the [language support table](/docs/multilingual/#language-support).
 
@@ -97,6 +97,6 @@ The Pagefind UI will look for values under the metadata keys `title`, `image`, a
 ```
 {{< /diffcode >}}
 
-## Futher customization
+## Further customization
 
 See the [Pagefind UI Configuration Reference](/docs/ui/) for all available options.
diff --git a/pagefind/features/characters.feature b/pagefind/features/characters.feature
@@ -32,7 +32,7 @@ Feature: Character Tests
         Then The selector "[data-result]" should contain "/apiary/"
 
     Scenario: Pagefind matches emoji
-        Given I have a "public/fam-seperate/index.html" file with the body:
+        Given I have a "public/fam-separate/index.html" file with the body:
             """
             <h1>Fam 👨‍👩‍👧‍👦</h1>
             """
@@ -57,7 +57,7 @@ Feature: Character Tests
             }
             """
         Then There should be no logs
-        Then The selector "[data-result]" should contain "/fam-middled/, /fam-seperate/"
+        Then The selector "[data-result]" should contain "/fam-middled/, /fam-separate/"
 
     Scenario: Pagefind doesn't match HTML entities as their text
         Given I have a "public/apiary/index.html" file with the body:

diff --git a/pagefind/features/frozen-pre-1.0/multilingual.feature b/pagefind/features/frozen-pre-1.0/multilingual.feature
@@ -71,7 +71,7 @@ Feature: Multilingual
         Then There should be no logs
         Then The selector "[data-result]" should contain "1 — /en/"
 
-    Scenario: LEGACY Pagefind searches for Portugese with Portugese stemming
+    Scenario: LEGACY Pagefind searches for Portuguese with Portuguese stemming
         Given I have a "public/index.html" file with the content:
             """
             <!DOCTYPE html>
@@ -116,7 +116,7 @@ Feature: Multilingual
                     <title>Document</title>
                 </head>
                 <body>
-                    <p>I am a different Portugese document (trust me — quilométricas — see?)</p>
+                    <p>I am a different Portuguese document (trust me — quilométricas — see?)</p>
                 </body>
             </html>
             """

diff --git a/pagefind/features/multilingual.feature b/pagefind/features/multilingual.feature
@@ -62,7 +62,7 @@ Feature: Multilingual
         Then There should be no logs
         Then The selector "[data-result]" should contain "1 — /en/"
 
-    Scenario: Pagefind searches for Portugese with Portugese stemming
+    Scenario: Pagefind searches for Portuguese with Portuguese stemming
         Given I have a "public/index.html" file with the content:
             """
             <!DOCTYPE html>
@@ -106,7 +106,7 @@ Feature: Multilingual
                     <title>Document</title>
                 </head>
                 <body>
-                    <p>I am a different Portugese document (trust me — quilométricas — see?)</p>
+                    <p>I am a different Portuguese document (trust me — quilométricas — see?)</p>
                 </body>
             </html>
             """

diff --git a/pagefind/features/multisite/multisite_lang.feature b/pagefind/features/multisite/multisite_lang.feature
@@ -22,7 +22,7 @@ Feature: Multisite Search Languages
             <html lang="pt-br">
                 <head></head>
                 <body>
-                    <h1>Website site B Portugese</h1>
+                    <h1>Website site B Portuguese</h1>
                 </body>
             </html>
             """
@@ -32,7 +32,7 @@ Feature: Multisite Search Languages
             <html lang="pt-br">
                 <head></head>
                 <body>
-                    <h1>Website site B Portugese</h1>
+                    <h1>Website site B Portuguese</h1>
                 </body>
             </html>
             """

diff --git a/pagefind/src/fossick/mod.rs b/pagefind/src/fossick/mod.rs
@@ -255,7 +255,7 @@ impl Fossicker {
                     // Run a segmenter only for any languages which require it.
                     Either::Right(seg.segment_str())
                 } else {
-                    // Currently hesistant to run segmentation during indexing
+                    // Currently hesitant to run segmentation during indexing
                     // that we can't also run during search, since we don't
                     // ship a segmenter to the browser. This logic is easier
                     // to replicate in the JavaScript that parses a search query.

diff --git a/pagefind/src/fossick/parser.rs b/pagefind/src/fossick/parser.rs
@@ -428,7 +428,7 @@ impl<'a> DomParser<'a> {
                             }
 
                             // Process filters & meta before we continue
-                            // TODO: Abstract repitition into function
+                            // TODO: Abstract repetition into function
                             if let Some(filters) = &node.filter {
                                 for filter in filters {
                                     if let Some((filter, value)) = node.get_attribute_pair(filter) {
-Original file line number
+Diff line change
@@ Expand Up @@
     ## Defining multiple metadata keys on a single element
-    Metadata captures may be comma seperated and all will apply. The exception is specifying metadata inline, which may only be the last item in a list.
+    Metadata captures may be comma separated and all will apply. The exception is specifying metadata inline, which may only be the last item in a list.
     Usage:
@@ Expand Down @@