From 6f63ef1be232dd7dcbc9b073f2aa6222d8a11c72 Mon Sep 17 00:00:00 2001
From: Gabriel Grubba <70247653+Grubba27@users.noreply.github.com>
Date: Fri, 16 Feb 2024 15:49:21 -0300
Subject: [PATCH] Removed "ignoreDeadLinks" options and updated dead links

---
 v3-docs/docs/.vitepress/config.mts             | 1 -
 v3-docs/docs/api/meteor.md                     | 4 ++--
 v3-docs/docs/packages/accounts-passwordless.md | 2 +-
 v3-docs/docs/packages/coffeescript.md          | 2 +-
 4 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/v3-docs/docs/.vitepress/config.mts b/v3-docs/docs/.vitepress/config.mts
index 5be8914f5b..4e9f7575db 100644
--- a/v3-docs/docs/.vitepress/config.mts
+++ b/v3-docs/docs/.vitepress/config.mts
@@ -285,5 +285,4 @@ export default defineConfig({
       text: "Edit this page on GitHub",
     },
   },
-  ignoreDeadLinks: true,
 });
diff --git a/v3-docs/docs/api/meteor.md b/v3-docs/docs/api/meteor.md
index 2671a78080..6d3a8c7a21 100644
--- a/v3-docs/docs/api/meteor.md
+++ b/v3-docs/docs/api/meteor.md
@@ -164,7 +164,7 @@ function Component() {
 :::
 
 Calling `methods` on the server defines functions that can be called remotely by
-clients. They should return an [EJSON](./ejson)-able value or throw an
+clients. They should return an [EJSON](./EJSON)-able value or throw an
 exception. Inside your method invocation, `this` is bound to a method
 invocation object, which provides the following:
 
@@ -189,7 +189,7 @@ but without waiting for the round trip delay. If a stub throws an
 exception it will be logged to the console.
 
 You use methods all the time, because the database mutators
-([`insert`](./mongo#insert), [`update`](./mongo#update), [`remove`](./mongo#remove)) are implemented
+([`insert`](./collections#Mongo-Collection-insert), [`update`](./collections#Mongo-Collection-update), [`remove`](./collections#Mongo-Collection-remove)) are implemented
 as methods. When you call any of these functions on the client, you're invoking
 their stub version that update the local cache, and sending the same write
 request to the server. When the server responds, the client updates the local
diff --git a/v3-docs/docs/packages/accounts-passwordless.md b/v3-docs/docs/packages/accounts-passwordless.md
index 2e029811fa..6c22051365 100644
--- a/v3-docs/docs/packages/accounts-passwordless.md
+++ b/v3-docs/docs/packages/accounts-passwordless.md
@@ -5,7 +5,7 @@ Passwordless package allows you to create a login for users without the need for
 The first step to in the passwordless process is for the user to sign-up or request a token to their email address. You can do that with the following:
 <ApiBox name="Accounts.requestLoginTokenForUser" from="accounts-base"/>
 
-If the user is signing up you can pass in the `userData` object like in [Accounts.createUser](/api/passwords.html#Accounts-createUser).
+If the user is signing up you can pass in the `userData` object like in [Accounts.createUser](/api/accounts#Accounts-createUser).
 
 <ApiBox name="Meteor.passwordlessLoginWithToken" />
 The second step in the passwordless flow. Like all the other `loginWith` functions call this method to login the user with the token they have inputted.
diff --git a/v3-docs/docs/packages/coffeescript.md b/v3-docs/docs/packages/coffeescript.md
index 8a26b44b6a..20be040d27 100644
--- a/v3-docs/docs/packages/coffeescript.md
+++ b/v3-docs/docs/packages/coffeescript.md
@@ -18,7 +18,7 @@ Here's how CoffeeScript works with Meteor's namespacing.
   they are defined.)
 
 * When writing a package, CoffeeScript-defined variables can be
-  exported like any other variable (see [Package.js](/api/packagejs.html)). Exporting a variable pulls it up to
+  exported like any other variable (see [Package.js](/api/package)). Exporting a variable pulls it up to
   package scope, meaning that it will be visible to all of the code in
   your app or package (both `.js` and `.coffee` files).