Rebranded from 'ferdi' to 'ferdium' (companion changes for the main repo PR #2)

5 files changed, 77 insertions, 77 deletions

diff --git a/docs/backend_api.md b/docs/backend_api.md
index a9d29ac..a46927b 100644
--- a/docs/backend_api.md
+++ b/docs/backend_api.md
@@ -1,8 +1,8 @@
 # Backend API
 
-Provides a set of helper functions to integrate the recipe into [Ferdi](https://ferdium.org).
+Provides a set of helper functions to integrate the recipe into [Ferdium](https://ferdium.org).
 
-## Ferdi Backend Class Methods
+## Ferdium Backend Class Methods
 
 * [validateUrl](#validateurl)
 * [overrideUserAgent](#overrideuseragent)
@@ -29,7 +29,7 @@ Validate if the given URL is a valid service instance.
 
 ```js
 // RocketChat integration
-module.exports = Ferdi => class RocketChat extends Ferdi {
+module.exports = Ferdium => class RocketChat extends Ferdium {
   async validateUrl(url) {
     try {
       const resp = await window.fetch(`${url}/api/info`, {
@@ -61,11 +61,11 @@ Override the user agent used inside the service webview.
 #### Usage
 
 ```js
-module.exports = Ferdi => class Discord extends Ferdi {
+module.exports = Ferdium => class Discord extends Ferdium {
   overrideUserAgent() {
-    // Remove Ferdi's signature from the user agent
+    // Remove Ferdium's signature from the user agent
     return window.navigator.userAgent.replace(
-    /(Ferdi|Electron)\/\S+ \([^)]+\)/g,
+    /(Ferdium|Electron)\/\S+ \([^)]+\)/g,
     ""
   );
   }
@@ -73,7 +73,7 @@ module.exports = Ferdi => class Discord extends Ferdi {
 ```
 
 ```js
-module.exports = Ferdi => class Example extends Ferdi {
+module.exports = Ferdium => class Example extends Ferdium {
   overrideUserAgent() {
     // Use a completely different user agent
     return "Mozilla/2.02Gold (Win95; I)";
@@ -98,7 +98,7 @@ Valid URL patterns can be referred from [here](https://www.electronjs.org/docs/a
 
 ```js
 // Hangouts Chat integration
-module.exports = Ferdi => class HangoutsChat extends Ferdi {
+module.exports = Ferdium => class HangoutsChat extends Ferdium {
     modifyRequestHeaders() {
       return [{
         // Adding an origin header for all http requests from this recipe
@@ -123,7 +123,7 @@ Specify an array of known hosts from where certificates can be issued for this s
 
 ```js
 // msteams Chat integration
-module.exports = Ferdi => class MicrosoftTeams extends Ferdi {
+module.exports = Ferdium => class MicrosoftTeams extends Ferdium {
   knownCertificateHosts() {
     return [
       'aka.ms',
@@ -152,14 +152,14 @@ module.exports = Ferdi => class MicrosoftTeams extends Ferdi {
 
 ### Events
 
-Ferdi recipes can hook into the [electron webview events](https://electron.atom.io/docs/api/webview-tag/#dom-events) to trigger custom functions.
+Ferdium recipes can hook into the [electron webview events](https://electron.atom.io/docs/api/webview-tag/#dom-events) to trigger custom functions.
 
 This is necessary for services like TweetDeck where custom URL forwarding is needed during login.
 
 #### Usage
 
 ```js
-module.exports = Ferdi => class Tweetdeck extends Ferdi {
+module.exports = Ferdium => class Tweetdeck extends Ferdium {
   events = {
     'did-get-redirect-request': '_redirectFix',
   }
diff --git a/docs/configuration.md b/docs/configuration.md
index a53c99d..8dff91b 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -1,6 +1,6 @@
 # Integration Config
 
-A [Ferdi](https://ferdium.org) recipe is a node module. In order to learn more about node modules and their configuration check the official [Node.js documentation](https://nodejs.org/api/modules.html) / [npm package.json documentation](https://docs.npmjs.com/files/package.json).
+A [Ferdium](https://ferdium.org) recipe is a node module. In order to learn more about node modules and their configuration check the official [Node.js documentation](https://nodejs.org/api/modules.html) / [npm package.json documentation](https://docs.npmjs.com/files/package.json).
 
 ## Table of Contents
 
@@ -21,7 +21,7 @@ Display name of the service.
 
 `string` **version** _mandatory_<br />
 Version number. Will be used for auto updating the integrations. The version number must be in a semver compatible format: eg `1.0.0`.
-**important:** the version will be used to figure out if a new recipe update should be deployed to the user. If you make changes to a recipe, **always** increase the version number or Ferdi won't update your recipe.
+**important:** the version will be used to figure out if a new recipe update should be deployed to the user. If you make changes to a recipe, **always** increase the version number or Ferdium won't update your recipe.
 
 `string` **license**<br />
 The license of the integration. We prefer MIT, but here is a list of all the available SPDX licenses http://spdx.org/licenses/
@@ -33,10 +33,10 @@ Link to your Github, Gitlab or Bitbucket public repository. Not used in the appl
 The list of alternate names that this recipe can be called
 
 `object` **config** _mandatory_<br />
-This is the Ferdi-specific integration config.
+This is the Ferdium-specific integration config.
 
 * `string` **serviceURL**<br/>
-Defines the URL that should be loaded into the Ferdi webview.
+Defines the URL that should be loaded into the Ferdium webview.
 <br /><br />
 If you want to load a simple URL like `https://www.messenger.com`, you can simply define it via the `serviceURL` parameter. If your service URL is team based, e.g. Slack or HipChat you can use `https://{teamId}.slack.com`.
 <br /><br />
diff --git a/docs/frontend_api.md b/docs/frontend_api.md
index 35b0918..af9acf8 100644
--- a/docs/frontend_api.md
+++ b/docs/frontend_api.md
@@ -1,5 +1,5 @@
 - [Frontend API](#frontend-api)
-  - [Ferdi Class Methods](#ferdi-class-methods)
+  - [Ferdium Class Methods](#ferdium-class-methods)
     - [setBadge(directMessages, [indirectMessages])](#setbadgedirectmessages-indirectmessages)
       - [Arguments](#arguments)
       - [Usage](#usage)
@@ -35,9 +35,9 @@
 
 # Frontend API
 
-Provides a set of helper functions to integrate the service into [Ferdi](https://ferdium.org).
+Provides a set of helper functions to integrate the service into [Ferdium](https://ferdium.org).
 
-## Ferdi Class Methods
+## Ferdium Class Methods
 
 ### setBadge(directMessages, [indirectMessages])
 
@@ -56,11 +56,11 @@ Sets the unread message badge
 #### Usage
 
 ```js
-Ferdi.setBadge(4, 2);
+Ferdium.setBadge(4, 2);
 
 // or
 
-Ferdi.setBadge(3);
+Ferdium.setBadge(3);
 ```
 
 ### setDialogTitle(title)
@@ -76,7 +76,7 @@ Sets the active dialog title to the app title
 #### Usage
 
 ```js
-Ferdi.setDialogTitle('Dialog title');
+Ferdium.setDialogTitle('Dialog title');
 ```
 
 ### injectCSS(pathToCssFile)
@@ -95,20 +95,20 @@ Injects the contents of one or more CSS files into the current webview
 const path = require('path');
 
 // inject a single css file
-Ferdi.injectCSS(path.join(__dirname, 'style.css'));
+Ferdium.injectCSS(path.join(__dirname, 'style.css'));
 
 // inject multiple css files
 const globalStyles = path.join(__dirname, 'global.css');
 const focusModeStyles = path.join(__dirname, 'focusmode.css');
 
-Ferdi.injectCSS(globalStyles, focusModeStyles);
+Ferdium.injectCSS(globalStyles, focusModeStyles);
 ```
 
 ### injectJSUnsafe(pathToJsFile)
 
 Injects the contents of one or more JavaScript files into the current webview without context isolation
 
-Ferdi uses context isolation to prevent services from accessing Node.js APIs in the webview.
+Ferdium uses context isolation to prevent services from accessing Node.js APIs in the webview.
 If you want to expose objects to the service (eg. via the `window` object) or interact with the Javascript loaded by the service you must do so from a script injected with this method.
 Trying to overwrite properties of the `window` object or other objects or trying to interact with the Javascript loaded by the service from `webview.js` will fail due to context isolation.
 
@@ -126,18 +126,18 @@ The code is executed as if part of the body of a Javascript function, ie. you sh
 const path = require('path');
 
 // inject a single css file
-Ferdi.injectJSUnsafe(path.join(__dirname, 'webview-unsafe.js'));
+Ferdium.injectJSUnsafe(path.join(__dirname, 'webview-unsafe.js'));
 
 // inject multiple css files
 const globalScripts = path.join(__dirname, 'global.js);
 const focusModeScripts = path.join(__dirname, 'focusmode.js);
 
-Ferdi.injectCSS(globalScripts, focusModeScripts);
+Ferdium.injectCSS(globalScripts, focusModeScripts);
 ```
 
 ### loop(action)
 
-Runs an action every X milliseconds (Ferdi default is currently 1s)
+Runs an action every X milliseconds (Ferdium default is currently 1s)
 
 #### Arguments
 
@@ -149,19 +149,19 @@ Runs an action every X milliseconds (Ferdi default is currently 1s)
 // slack integration
 const path = require('path');
 
-module.exports = Ferdi => {
+module.exports = Ferdium => {
   const getMessages = () => {
     const directMessages = $('.unread_highlights, .unread_highlight').not(
       '.hidden',
     ).length;
     const indirectMessages = $('.unread').length - directMessages;
 
-    Ferdi.setBadge(directMessages, indirectMessages);
+    Ferdium.setBadge(directMessages, indirectMessages);
   };
 
-  Ferdi.loop(getMessages);
+  Ferdium.loop(getMessages);
 
-  Ferdi.injectCSS(path.join(__dirname, 'style.css'));
+  Ferdium.injectCSS(path.join(__dirname, 'style.css'));
 };
 ```
 
@@ -177,22 +177,22 @@ Runs `fn` on every notification created by the service before sending them to th
 
 ```js
 // messenger integration
-module.exports = Ferdi => {
+module.exports = Ferdium => {
   const getMessages = () => {
     let count = document.querySelectorAll(
       '._5fx8:not(._569x),._1ht3:not(._569x)',
     ).length;
     const messageRequestsElement = document.querySelector('._5nxf');
     if (messageRequestsElement) {
-      count += Ferdi.safeParseInt(messageRequestsElement.textContent);
+      count += Ferdium.safeParseInt(messageRequestsElement.textContent);
     }
 
-    Ferdi.setBadge(count);
+    Ferdium.setBadge(count);
   };
 
-  Ferdi.loop(getMessages);
+  Ferdium.loop(getMessages);
 
-  Ferdi.onNotify(notification => {
+  Ferdium.onNotify(notification => {
     if (typeof notification.title !== 'string') {
       notification.title =
         ((notification.title.props || {}).content || [])[0] || 'Messenger';
@@ -209,7 +209,7 @@ You can use a `darkmode.css` to automatically get the service into a dark theme.
 
 This handler should take the necessary steps to (de-)activate dark mode on the page, e.g. by clicking a button or flipping a switch.
 
-Ferdi won't activate DarkReader or inject `darkmode.css` if the recipe has defined a custom handler. If you still need to do this, you can use the `injectDarkModeStyle` or `enableDarkMode` function provided as the second argument.
+Ferdium won't activate DarkReader or inject `darkmode.css` if the recipe has defined a custom handler. If you still need to do this, you can use the `injectDarkModeStyle` or `enableDarkMode` function provided as the second argument.
 
 #### Arguments
 
@@ -229,7 +229,7 @@ Ferdi won't activate DarkReader or inject `darkmode.css` if the recipe has defin
 
 ```JavaScript
 // Handler that works for Reddit
-Ferdi.handleDarkMode((isEnabled, helpers) => {
+Ferdium.handleDarkMode((isEnabled, helpers) => {
   // Open dropdown menu if not already open
   const menu = document.querySelector('#USER_DROPDOWN_ID');
   if (menu.getAttribute('aria-expanded') === 'false') {
@@ -251,7 +251,7 @@ Ferdi.handleDarkMode((isEnabled, helpers) => {
 // --- or ---
 
 // Helper that activates DarkReader and injects your darkmode.css at the same time
-Ferdi.handleDarkMode((isEnabled, helpers) => {
+Ferdium.handleDarkMode((isEnabled, helpers) => {
   if (isEnabled) {
     helpers.enableDarkMode();
     if (!helpers.isDarkModeStyleInjected()) {
@@ -276,7 +276,7 @@ While exiting/closing/disabling the service, if you want to clear the local stor
 #### Usage
 
 ```JavaScript
-  Ferdi.clearStorageData(settings.id, {
+  Ferdium.clearStorageData(settings.id, {
       storages: [
         'appcache',
         'serviceworkers',
@@ -302,12 +302,12 @@ A utility method that can be used to safely parse the text content (handles null
 #### Usage
 
 ```JavaScript
-Ferdi.safeParseInt(mySelector.innerText)
+Ferdium.safeParseInt(mySelector.innerText)
 ```
 
 ### setDialogTitle(title)
 
-When you want to set the title of the Ferdi window (while this service is active or in focus), you can use this function
+When you want to set the title of the Ferdium window (while this service is active or in focus), you can use this function
 
 #### Arguments
 
@@ -316,5 +316,5 @@ When you want to set the title of the Ferdi window (while this service is active
 #### Usage
 
 ```JavaScript
-Ferdi.setDialogTitle(element ? element.textContent : null);
+Ferdium.setDialogTitle(element ? element.textContent : null);
 ```
diff --git a/docs/integration.md b/docs/integration.md
index 1115454..d0b1460 100644
--- a/docs/integration.md
+++ b/docs/integration.md
@@ -1,10 +1,10 @@
-# Ferdi Recipe Documentation / Overview
+# Ferdium Recipe Documentation / Overview
 
-Recipes are responsible for providing the connection between the service itself (e.g. WhatsApp) and Ferdi, providing information like the number of current notifications or handling dark mode.
+Recipes are responsible for providing the connection between the service itself (e.g. WhatsApp) and Ferdium, providing information like the number of current notifications or handling dark mode.
 
-A Ferdi recipe is basically nothing else than a node module and is currently initialized on `dom-ready`. You access all of the [electron](http://electron.atom.io) modules as well.
+A Ferdium recipe is basically nothing else than a node module and is currently initialized on `dom-ready`. You access all of the [electron](http://electron.atom.io) modules as well.
 
-> ℹ️ New to Ferdi recipes and Electron? Then we recommend you read Jake Lee's ["Super simple guide to adding a new Ferdi service recipe"](https://blog.jakelee.co.uk/super-simple-guide-to-adding-a-new-ferdi-service-recipe/) which gives you an easy step-by-step guide on how to create and publish your recipe!
+> ℹ️ New to Ferdium recipes and Electron? Then we recommend you read Jake Lee's ["Super simple guide to adding a new Ferdium service recipe"](https://blog.jakelee.co.uk/super-simple-guide-to-adding-a-new-ferdium-service-recipe/) which gives you an easy step-by-step guide on how to create and publish your recipe!
 
 > ℹ️ If you have any problems packaging your recipes, if you are inexperienced with the tools used or have any other problems, we are here to help! Just open a new issue at https://github.com/ferdium/ferdium-recipes/issues/new and we can help you develop, test and publish your recipe
 
@@ -12,7 +12,7 @@ A Ferdi recipe is basically nothing else than a node module and is currently ini
 
 ## Table of Contents
 
-- [Ferdi Recipe Documentation / Overview](#ferdi-recipe-documentation--overview)
+- [Ferdium Recipe Documentation / Overview](#ferdium-recipe-documentation--overview)
   - [Table of Contents](#table-of-contents)
   - [Preparing](#preparing)
   - [Create a recipe](#create-a-recipe)
@@ -49,7 +49,7 @@ pnpm run create "Service Name"
 ```
 
 Replace `Service Name` with the name of your service, e.g. `pnpm run create "Google Hangouts"`.
-This command will automatically create the development recipe in the correct folder, prepares it for your service and opens the new recipe in your file explorer or Finder. 5. Reload Ferdi (`CMD/CTRL + SHIFT + R`) in order for it to register the new recipe 6. You can now develop your recipe as described below. Please continue down below with "[Publishing](#Publishing)" after you are done creating your recipe.
+This command will automatically create the development recipe in the correct folder, prepares it for your service and opens the new recipe in your file explorer or Finder. 5. Reload Ferdium (`CMD/CTRL + SHIFT + R`) in order for it to register the new recipe 6. You can now develop your recipe as described below. Please continue down below with "[Publishing](#Publishing)" after you are done creating your recipe.
 
 5. (Mandatory) Please run the following step before raising a PR:
 ```Bash
@@ -59,10 +59,10 @@ Fix any issues that are reported.
 
 ## Recipe structure
 
-Every recipe needs a specific file structure in order to work as a Ferdi recipe
+Every recipe needs a specific file structure in order to work as a Ferdium recipe
 
 - icon.svg - Icon for the service in SVG form (must be square)
-- index.js - Backend script, this script is NOT included in the service webview but only in Ferdi itself
+- index.js - Backend script, this script is NOT included in the service webview but only in Ferdium itself
 - package.json - Information about the recipe
 - webview.js - Optional frontend script, this script is injected into the service itself but still has access to all NodeJS APIs
 - darkmode.css - CSS File that gets included when dark mode is activated
@@ -75,7 +75,7 @@ The `package.json` is structured like any other node module and allows to comple
 {
   "id": "tweetdeck",
   "name": "Tweetdeck",
-  "version": "1.0.1",
+  "version": "1.0.0",
   "license": "MIT",
   "repository": "https://github.com/meetfranz/recipe-tweetdeck",
   "config": {
@@ -90,18 +90,18 @@ Please note that the fields `id`, `name`, `version` and `config` are mandatory.
 
 ### index.js
 
-This is your "backend" code. Right now the options are very limited and most of the services don't need a custom handling here. If your service is relatively straight forward and has a static URL eg. _messenger.com_, _`[TEAMID]`.slack.com_ or _web.skype.com_ all you need to do to return the Ferdi Class:
+This is your "backend" code. Right now the options are very limited and most of the services don't need a custom handling here. If your service is relatively straight forward and has a static URL eg. _messenger.com_, _`[TEAMID]`.slack.com_ or _web.skype.com_ all you need to do to return the Ferdium Class:
 
 ```js
-module.exports = Ferdi => Ferdi;
+module.exports = Ferdium => Ferdium;
 ```
 
 If your service can be hosted on custom servers, you can validate the given URL to detect if it's your server and not e.g. google.com. To enable validation you can override the function `validateServer`
 
 ```js
 // RocketChat integration
-module.exports = Ferdi =>
-  class RocketChat extends Ferdi {
+module.exports = Ferdium =>
+  class RocketChat extends Ferdium {
     async validateUrl(url) {
       try {
         const resp = await window.fetch(`${url}/api/info`, {
@@ -124,20 +124,20 @@ module.exports = Ferdi =>
 
 `validateServer` needs to return a [`Promise`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Promise), otherwise validation will fail.
 
-By default, Ferdi's user agent looks like this:
+By default, Ferdium's user agent looks like this:
 
 ```text
-Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.141 Safari/537.36 Ferdi/5.4.4-beta.3 (Electron 8.1.1)
+Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.141 Safari/537.36 Ferdium/5.4.4-beta.3 (Electron 8.1.1)
 ```
 
-Some services may not be compatible with Ferdi adding it's signature to the user agent.
+Some services may not be compatible with Ferdium adding it's signature to the user agent.
 
 If you encounter such a service, please remove this signature with the following snippet of code
 
 ```js
 overrideUserAgent() {
   return window.navigator.userAgent.replace(
-    /(Ferdi|Electron)\/\S+ \([^)]+\)/g,
+    /(Ferdium|Electron)\/\S+ \([^)]+\)/g,
     ""
   );
 }
@@ -153,11 +153,11 @@ overrideUserAgent() {
 
 ### webview.js
 
-The optional `webview.js` is the actual script that will be loaded into the webview. Here you can do whatever you want to do in order perfectly integrate the service into Ferdi. For convenience, we have provided a very simple set of functions to set unread message badges (`Ferdi.setBadge()`), set active dialog title (`Ferdi.setDialogTitle()`) and inject CSS files (`Ferdi.injectCSS()`).
+The optional `webview.js` is the actual script that will be loaded into the webview. Here you can do whatever you want to do in order perfectly integrate the service into Ferdium. For convenience, we have provided a very simple set of functions to set unread message badges (`Ferdium.setBadge()`), set active dialog title (`Ferdium.setDialogTitle()`) and inject CSS files (`Ferdium.injectCSS()`).
 
 ```js
 // telegram integration
-module.exports = Ferdi => {
+module.exports = Ferdium => {
   const getMessages = () => {
     let direct = 0;
     let indirect = 0;
@@ -165,7 +165,7 @@ module.exports = Ferdi => {
     for (const element of elements) {
       const subtitleBadge = element.querySelector('.dialog-subtitle-badge');
       if (subtitleBadge) {
-        const parsedValue = Ferdi.safeParseInt(subtitleBadge.textContent);
+        const parsedValue = Ferdium.safeParseInt(subtitleBadge.textContent);
         if (element.dataset.peerId > 0) {
           direct += parsedValue;
         } else {
@@ -174,13 +174,13 @@ module.exports = Ferdi => {
       }
     }
 
-    Ferdi.setBadge(direct, indirect);
+    Ferdium.setBadge(direct, indirect);
   };
 
   const getActiveDialogTitle = () => {
     const element = document.querySelector('.top .peer-title');
 
-    Ferdi.setDialogTitle(element ? element.textContent : '');
+    Ferdium.setDialogTitle(element ? element.textContent : '');
   };
 
   const loopFunc = () => {
@@ -188,9 +188,9 @@ module.exports = Ferdi => {
     getActiveDialogTitle();
   };
 
-  Ferdi.loop(loopFunc);
+  Ferdium.loop(loopFunc);
 
-  Ferdi.injectCSS(_path.default.join(__dirname, 'service.css'));
+  Ferdium.injectCSS(_path.default.join(__dirname, 'service.css'));
 };
 ```
 
@@ -198,22 +198,22 @@ To get more information about the provided functions, check the [API docs](front
 
 ## Icons
 
-In order to show every service icon crystal clear within the Ferdi UI, we require the icon in .svg (square, 1024x1024px) format.
+In order to show every service icon crystal clear within the Ferdium UI, we require the icon in .svg (square, 1024x1024px) format.
 
 ## Dark Mode
 
 You can provide a custom Dark Mode Theme for your recipes just by putting the `darkmode.css` into your recipe folder. Once the `darkmode.css` exists, you can enable the Dark Mode in your service settings.
 
-Recipe Dark Mode is only supported by Ferdi 5.0.0-beta.19+. Even then, certain services do not allow clients like Ferdi to override these styles (an example of this is google calendar).
+Recipe Dark Mode is only supported by Ferdium 5.0.0-beta.19+. Even then, certain services do not allow clients like Ferdium to override these styles (an example of this is google calendar).
 
 ## Debugging
 
-In order to debug your service integration, open Ferdi and use the shortcut `Cmd/Ctrl+Alt+Shift+I` to open the recipes developer tools.
+In order to debug your service integration, open Ferdium and use the shortcut `Cmd/Ctrl+Alt+Shift+I` to open the recipes developer tools.
 
 ## Publishing
 
-Ferdi uses its recipe repository at <https://github.com/ferdium/ferdium-recipes> to publish recipes to all clients.
+Ferdium uses its recipe repository at <https://github.com/ferdium/ferdium-recipes> to publish recipes to all clients.
 
-Publishing your recipes to Ferdi is super easy! When you used our recipe creation script, we have created a folder for your recipe inside Ferdi's internal folders (the one that got automatically opened after you ran our script).
+Publishing your recipes to Ferdium is super easy! When you used our recipe creation script, we have created a folder for your recipe inside Ferdium's internal folders (the one that got automatically opened after you ran our script).
 
 Simply copy that whole folder into the repositories "recipes" folder. You'll now need to push your changes to Git and create a Pull Request from your fork repository to our repository using the GitHub website.
diff --git a/docs/updating.md b/docs/updating.md
index f840f50..b5d35c3 100644
--- a/docs/updating.md
+++ b/docs/updating.md
@@ -4,16 +4,16 @@ If you want to improve or update an existing recipe, please follow this guide.
 
 ## 1. Implement your updates
 
-We highly suggest that you implement and test your updates to the recipe inside Ferdi before implementing them into the recipe repository. This will save you time on debugging and repackaging the recipe later.
+We highly suggest that you implement and test your updates to the recipe inside Ferdium before implementing them into the recipe repository. This will save you time on debugging and repackaging the recipe later.
 
-You can find the recipe source Ferdi uses at:
+You can find the recipe source Ferdium uses at:
   * Mac: `~/Library/Application Support/Ferdium/recipes/<recipe id>/`
   * Windows: `%appdata%/Ferdium/recipes/<recipe id>/`
   * Linux: `~/.config/Ferdium/recipes/<recipe id>`
 
-> If you can't find the recipe's folder, please make sure that you have created a service inside Ferdi with that recipe - otherwise Ferdi will not load it into the folder
+> If you can't find the recipe's folder, please make sure that you have created a service inside Ferdium with that recipe - otherwise Ferdium will not load it into the folder
 
-After changing the files in that folder, you can reload the service inside Ferdi using `CTRL/CMD + R`.
+After changing the files in that folder, you can reload the service inside Ferdium using `CTRL/CMD + R`.
 
 ## 2. Setting up the recipe repository
 
@@ -27,7 +27,7 @@ Simply add your changes to the recipe inside this repository.
 
 You'll need to increase the version number inside recipe's `package.json`.
 
-Ferdi uses this version to determine if it should update the local copy of the recipe. If you do not increase the version number, no Ferdi user will get your updated recipe 😔
+Ferdium uses this version to determine if it should update the local copy of the recipe. If you do not increase the version number, no Ferdium user will get your updated recipe 😔
 
 ## 5. Running the validation checks