From d6abd4c560d5a1ba6ae8811c54c85594b10b6308 Mon Sep 17 00:00:00 2001
From: 24bitIO <47846541+24bitIO@users.noreply.github.com>
Date: Mon, 1 Jan 2024 04:22:32 +0000
Subject: [PATCH] Fix broken link

Fixing two broken links pointing to ../custom-state-fields.
Updated to ../state-fields.
---
 .../03.state-machine/03.state-transition-guards/docs.md       | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/user/pages/03.commerce2/02.developer-guide/03.core/00.libraries-and-dependencies/03.state-machine/03.state-transition-guards/docs.md b/user/pages/03.commerce2/02.developer-guide/03.core/00.libraries-and-dependencies/03.state-machine/03.state-transition-guards/docs.md
index 5c5041036..099b638d1 100644
--- a/user/pages/03.commerce2/02.developer-guide/03.core/00.libraries-and-dependencies/03.state-machine/03.state-transition-guards/docs.md
+++ b/user/pages/03.commerce2/02.developer-guide/03.core/00.libraries-and-dependencies/03.state-machine/03.state-transition-guards/docs.md
@@ -12,7 +12,7 @@ When an order is placed, either at checkout or through the admin UI, its State c
 
 ![Custom state field config](../images/state-transition-guards-2.png)
 
-But what if we wanted to add constraints to prevent administrative users from moving an Order from the Fulfillment state to Completed or Canceled under certain conditions? In the [Custom state fields documentation](../custom-state-fields), we created a custom State field for Order items, to track fulfillment on a per-item basis. We might want to prevent users from cancelling an order if any of its order items have already been "filled". And we might want to prevent users from transitioning an order to Completed if any of its items are still "un-filled". The State Machine module's state transition "Guards" provide the ability to incorporate this sort of business logic. State transition Guards limit the transitions available for a State field based on contextual information. Transitions can be restricted based on the current user's permissions, a parent entity field, etc.
+But what if we wanted to add constraints to prevent administrative users from moving an Order from the Fulfillment state to Completed or Canceled under certain conditions? In the [Custom state fields documentation](../state-fields), we created a custom State field for Order items, to track fulfillment on a per-item basis. We might want to prevent users from cancelling an order if any of its order items have already been "filled". And we might want to prevent users from transitioning an order to Completed if any of its items are still "un-filled". The State Machine module's state transition "Guards" provide the ability to incorporate this sort of business logic. State transition Guards limit the transitions available for a State field based on contextual information. Transitions can be restricted based on the current user's permissions, a parent entity field, etc.
 
 ![Order fulfillment workflow with guards](../images/state-transition-guards-3.png)
 
@@ -78,7 +78,7 @@ services:
       - { name: state_machine.guard, group: commerce_order }
 ```
 
-If we wanted to implement a Guard for the custom Order item "Fulfillment state" field we implemented in the [Custom state fields documentation](../custom-state-fields), the `group` value would change to match that custom workflow group:
+If we wanted to implement a Guard for the custom Order item "Fulfillment state" field we implemented in the [Custom state fields documentation](../state-fields), the `group` value would change to match that custom workflow group:
 
 ```yaml
   mymodule.fulfillment_order_item_guard: