From b60d0b8f41d7ca21e08ef7ba7cdd145ecd2667bb Mon Sep 17 00:00:00 2001
From: NewSoupVi <57900059+NewSoupVi@users.noreply.github.com>
Date: Thu, 5 Sep 2024 17:00:33 +0200
Subject: [PATCH] Update world api.md

---
 docs/world api.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/world api.md b/docs/world api.md
index 5e2a6a8c8a..3460323b96 100644
--- a/docs/world api.md	
+++ b/docs/world api.md	
@@ -328,7 +328,7 @@ Even doing `state.can_reach_location` or `state.can_reach_entrance` is problemat
 You can use `multiworld.register_indirect_condition(region, entrance)` to explicitly tell the generator that, when a given region becomes accessible, it is necessary to re-check a specific entrance.
 You **must** use `multiworld.register_indirect_condition` if you perform this kind of `can_reach` from an entrance access rule, unless you have a **very** good technical understanding of the relevant code and can reason why it will never lead to problems in your case.
 
-Alternatively, you can set [world.explicit_indirect_conditions = False]([https://github.com/ArchipelagoMW/Archipelago/pull/3682](https://github.com/ArchipelagoMW/Archipelago/blob/main/worlds/AutoWorld.py#L298-L301)),
+Alternatively, you can set [world.explicit_indirect_conditions = False](https://github.com/ArchipelagoMW/Archipelago/blob/main/worlds/AutoWorld.py#L298-L301),
 in which case your world takes a flat performance hit to not have to worry about indirect conditions.
 
 ### Item Rules