fix broken links

Author: mProjectsCode

.github/workflows/deploy.yml

@@ -46,4 +46,4 @@ jobs:
     steps:
       - name: Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@v4
+        uses: actions/deploy-pages@v4

src/content/docs/guides/api.mdx

@@ -7,7 +7,7 @@ import { Tabs, TabItem } from '@astrojs/starlight/components';
 
 Meta Bind offers a JavaScript API that allows you to interact with the Meta Bind internals via JavaScript.
 
-Documentation for the API can be found [here](/obsidian-meta-bind-plugin-docs/api/classes/obsidianapi/).
+Documentation for the API can be found [here](/obsidian-meta-bind-plugin-docs/api/classes/obsapi/).
 
 ## Usage
 

src/content/docs/guides/buttons.md

@@ -97,31 +97,31 @@ The YAML configuration of a button must adhere to the following TypeScript inter
 interface ButtonConfig {
 	// Required fields:
 	// The text displayed on the button.
-	label: string; 
+	label: string;
 	// The style of the button.
-	style: 'default' | 'primary' | 'destructive' | 'plain'; 
+	style: 'default' | 'primary' | 'destructive' | 'plain';
 
 	// Optional fields:
 	// An optional lucide icon to display on the button.
 	icon?: string;
 	// Optional CSS classes to add to the button. Multiple classes can be separated by spaces.
 	class?: string;
 	// Optional CSS inline stiles to apply to the button.
-	cssStyle?: string; 
+	cssStyle?: string;
 	// Optional path to a background image for the button.
-	backgroundImage?: string; 
+	backgroundImage?: string;
 	// Optional tooltip to display when hovering over the button. If not set, the label is used.
-	tooltip?: string; 
+	tooltip?: string;
 	// The optional id of the button, used for referencing the button in inline buttons.
-	id?: string; 
+	id?: string;
 	// Whether this button should be hidden, useful when only using the button in inline buttons.
-	hidden?: boolean; 
+	hidden?: boolean;
 
 	// Button Actions:
 	// The action to perform when the button is clicked.
-	action?: ButtonAction; 
+	action?: ButtonAction;
 	// Optionally multiple actions can be performed when the button is clicked.
-	actions?: ButtonAction[]; 
+	actions?: ButtonAction[];
 }
 ```
 

src/content/docs/guides/customMathJS.md

@@ -24,7 +24,7 @@ As an example, we will define a `clamp()` function, which is not part of default
 The function should take in three parameters, the current value, a minimum, and a maximum. It returns the current value as long as its inside the range otherwise the boundary-value.
 
 ```js
-clamp: (val, min, max) => Math.min(Math.max(min, val), max)
+clamp: (val, min, max) => Math.min(Math.max(min, val), max);
 ```
 
 Add this definitions inside a JavaScrypt file stored in you Vault and enable that file to be [run as a startup script](https://www.moritzjung.dev/obsidian-js-engine-plugin-docs/guides/startupscripts/).
@@ -34,11 +34,11 @@ Inside the file you can use the `mathJSImport(dict, options)` function from the
 const mb = engine.getPlugin('obsidian-meta-bind-plugin').api;
 
 mb.mathJSImport({
-    // definition of the clamp function
-    clamp: (val, min, max) => Math.min(Math.max(min, val), max),
+	// definition of the clamp function
+	clamp: (val, min, max) => Math.min(Math.max(min, val), max),
 
-    // we can also define useful constants here
-    foo: 42
+	// we can also define useful constants here
+	foo: 42,
 });
 ```
 

src/content/docs/guides/metaBindEmbed.md

@@ -5,7 +5,7 @@ description: A tutorial for the Meta Bind Embed.
 
 Meta Bind Embeds are a way to embed a note inside another note, which works a bit differently than the normal Obsidian embeds.
 
-Together with Meta Binds other features, they allow you to build dynamic templates. 
+Together with Meta Binds other features, they allow you to build dynamic templates.
 The major disadvantage with a traditional template based approach is that modifications to the templates don't automatically apply to all notes created using that template.
 Meta Bind Embeds on the other hand propagate changes to the "template" to all notes embedding it instantly, since the "template" file is read every time the note renders and not just once when the note is created.