From 2cbe302a4937977c836aa515d1c8a9720b3faf0f Mon Sep 17 00:00:00 2001
From: NewSoupVi <57900059+NewSoupVi@users.noreply.github.com>
Date: Thu, 5 Sep 2024 21:14:45 +0200
Subject: [PATCH] Update docs/world api.md

Co-authored-by: Nicholas Saylor <79181893+nicholassaylor@users.noreply.github.com>
---
 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 ba358ef92c..02fc588758 100644
--- a/docs/world api.md	
+++ b/docs/world api.md	
@@ -329,7 +329,7 @@ You can use `multiworld.register_indirect_condition(region, entrance)` to explic
 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/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.
+avoiding the need for indirect conditions at the expense of performance.
 
 ### Item Rules