fix: correct typos

CHANGELOG.md

@@ -671,7 +671,7 @@ You can now delete unread items via occ:
 
 ### Fixed
 
-- Fix false cron notifaction #823
+- Fix false cron notification #823
 - Fix cron updater not working #819 #824
 - Fix invalid UserId when logged out #822
 - Fix autoPurge not working #824
@@ -718,7 +718,7 @@ You can now delete unread items via occ:
 ### Changed
 - JS library updates #737 #741
 - Allow data URI scheme inside the body of an item #733
-- Update to new BackgroudJob logic #704
+- Update to new BackgroundJob logic #704
 - Update feed-io to v4.7.8
 
 ### Fixed
@@ -880,7 +880,7 @@ You can now delete unread items via occ:
 
 ### Fixed
 - Highlight in compact mode #109
-- Prevent raw angluar templates from flashing on page load #429
+- Prevent raw angular templates from flashing on page load #429
 - HTML elements where not rendered #428
 - Provide UserAgent to prevent HTTP 403 errors #428
 

_typos.toml

@@ -1,2 +1,8 @@
 [files]
-extend-exclude = [ "l10n/*.js*", "js-old/**", "/tests/test_helper/feeds/*", "AUTHORS.md" ]
+extend-exclude = [ 
+    "l10n/*.js*",
+    "js-old/**",
+    "/tests/test_helper/feeds/*",
+    "tests/Unit/Db/ItemTest.php",
+    "AUTHORS.md"
+]

docs/api/api-v1-2.md

@@ -50,7 +50,7 @@ All routes are given relative to the base API url (e.g.: <https://yournextcloud.
 
 ### Initial Sync
 
-The intial sync happens, when a user adds a Nextcloud account in your app. In that case you should fetch all feeds, folders and unread or starred articles from the News app. Do not fetch all articles, not only because it syncs faster, but also because the user is primarily interested in unread articles. To fetch all unread and starred articles, you must call 4 routes:
+The initial sync happens, when a user adds a Nextcloud account in your app. In that case you should fetch all feeds, folders and unread or starred articles from the News app. Do not fetch all articles, not only because it syncs faster, but also because the user is primarily interested in unread articles. To fetch all unread and starred articles, you must call 4 routes:
 
 * **unread articles**: GET /items?type=3&getRead=false&batchSize=-1
 * **starred articles**: GET /items?type=2&getRead=true&batchSize=-1
@@ -297,7 +297,7 @@ The following attributes are **not sanitized** meaning: including them in your w
       "ordering": 0, // 0 means no special ordering, 1 means oldest first, 2 newest first, new in 5.1.0
       "link": "http://theoatmeal.com/",
       "pinned": true // if a feed should be sorted before other feeds, added in 6.0.3,
-      "updateErrorCount": 0, // added in 8.6.0, 0 if no errors occured during the last update,
+      "updateErrorCount": 0, // added in 8.6.0, 0 if no errors occurred during the last update,
                              // otherwise is incremented for each failed update.
                              // Once it reaches a threshold, a message should be displayed to the user
                              // indicating that the feed has failed to update that many times.

docs/api/api-v1-3.md

@@ -50,7 +50,7 @@ All routes are given relative to the base API url (e.g.: <https://yournextcloud.
 
 ### Initial Sync
 
-The intial sync happens, when a user adds a Nextcloud account in your app. In that case you should fetch all feeds, folders and unread or starred articles from the News app. Do not fetch all articles, not only because it syncs faster, but also because the user is primarily interested in unread articles. To fetch all unread and starred articles, you must call 4 routes:
+The initial sync happens, when a user adds a Nextcloud account in your app. In that case you should fetch all feeds, folders and unread or starred articles from the News app. Do not fetch all articles, not only because it syncs faster, but also because the user is primarily interested in unread articles. To fetch all unread and starred articles, you must call 4 routes:
 
 * **unread articles**: GET /items?type=3&getRead=false&batchSize=-1
 * **starred articles**: GET /items?type=2&getRead=true&batchSize=-1
@@ -297,7 +297,7 @@ The following attributes are **not sanitized** meaning: including them in your w
       "ordering": 0, // 0 means no special ordering, 1 means oldest first, 2 newest first, new in 5.1.0
       "link": "http://theoatmeal.com/",
       "pinned": true // if a feed should be sorted before other feeds, added in 6.0.3,
-      "updateErrorCount": 0, // added in 8.6.0, 0 if no errors occured during the last update,
+      "updateErrorCount": 0, // added in 8.6.0, 0 if no errors occurred during the last update,
                              // otherwise is incremented for each failed update.
                              // Once it reaches a threshold, a message should be displayed to the user
                              // indicating that the feed has failed to update that many times.

docs/api/api-v2.md

@@ -194,7 +194,7 @@ There are two usecases for syncing:
 
 ### Initial Sync
 
-The intial sync happens when a user adds an Nextcloud account in your app. In that case you want to download all folders, feeds and unread/starred items. To do this, make the following request:
+The initial sync happens when a user adds an Nextcloud account in your app. In that case you want to download all folders, feeds and unread/starred items. To do this, make the following request:
 
 * **Method**: GET
 * **Route**: /sync

js-old/app/Config.js

@@ -129,7 +129,7 @@ app.config(function ($routeProvider, $provide, $httpProvider, $locationProvider)
                     if (type === FEED_TYPE.FEED) {
                         var feed = FeedResource.getById(parameters.id);
 
-                        // on intial load, the feed ordering is undefined
+                        // on initial load, the feed ordering is undefined
                         if (feed === undefined || feed.ordering === 2) {
                             parameters.oldestFirst = false;
                         } else if (feed.ordering === 1) {