Broken links fixed

hcourdent · hcourdent · commit 562742babc4c · 2023-05-02T11:05:42.000+02:00
diff --git a/docs/getting_started/6_flows_quickstart/index.md b/docs/getting_started/6_flows_quickstart/index.md
@@ -28,7 +28,7 @@ Also, you can give succintly a Name, a Summary and a Description to your flow. T
 
 Then, you will configure the **[Schedule](../../core_concepts/1_scheduling/index.md)**. Flows can be [triggered](../9_trigger_flows/index.md) by any schedules, their [webhooks](../../core_concepts/4_webhooks/index.md) or their UI but they only have only one primary schedule with which they share the same path. This menu is where you set the primary schedule with CRON. The default schedule is none.
 
-**[Shared Directory](../../flows/flow_settings#shared-directory)**:
+**[Shared Directory](../../flows/1_flow_editor.md#shared-directory)**:
 
 Flows on Windmill are by default based on a result basis. A step will take as inputs the results of previous steps. And this works fine for lightweight automation.
 
@@ -41,7 +41,7 @@ You can always go back to this menu by clicking on `Settings` on the top lef, or
 The proper flow editor is the side menu on the left. From there you can architecture your flow and take action at each step.
 ![Flow editor menu](./flow_editor_menu.png)
 
-There are four kinds of scripts: [Action](../../flows/flow_action), [Trigger](../../flows/10_flow_trigger.md), [Approval](../../flows/11_flow_approval.md) and [Error handler](../../flows/7_flow_error_handler.md). You can sequence them how you want.
+There are four kinds of scripts: [Action](../../flows/1_flow_editor.md#flow-actions), [Trigger](../../flows/10_flow_trigger.md), [Approval](../../flows/11_flow_approval.md) and [Error handler](../../flows/7_flow_error_handler.md). You can sequence them how you want.
 
 Each script can be called from Workspace or Hub, you can also decide to **write them inline**.
 
@@ -70,21 +70,21 @@ But the Flow editor is not just for sequence of steps, but also for more complex
 
 ### For loops
 
-**[For loops](../../flows//flow_loops)** are a special type of steps that allows you to iterate over a list of items, given by an iterator expression.
+**[For loops](../../flows/12_flow_loops.md)** are a special type of steps that allows you to iterate over a list of items, given by an iterator expression.
 
 ![Flows for loops](./for_loops.png)
 
 ### Branching
 
-**[Branches](../../flows/flow_branches)** allow you to build branching logic to create and manage complex workflows. There are two of them:
+**[Branches](../../flows/13_flow_branches.md)** allow you to build branching logic to create and manage complex workflows. There are two of them:
 - **branch one**: allows you to execute a branch if a condition is true
 - **branch all**: allows you to execute all the branches in parallel, as if each branch is a flow.
 
 
 
 ### Suspend/Approval Step
 
-At each step you can add **[approval scripts](../../flows/flow_approval)** to manage security and control over your flows.
+At each step you can add **[approval scripts](../../flows/11_flow_approval.md)** to manage security and control over your flows.
 
 Request approvals can be sent by email, Slack, anything. Then you can **automatically resume workflows with secret webhooks** after the approval steps.
 
@@ -124,7 +124,7 @@ We saw above that you can trigger flows using **[schedules](../../core_concepts/
 
 **[Webhooks](../../core_concepts/4_webhooks/index.md)**. Each Flow created in the app gets autogenerated webhooks. You can see them once you flow is saved.
 
-**[Execute flows from the CLI](../../advanced/cli/)** to trigger your flows from your terminal.
+**[Execute flows from the CLI](../../advanced/3_cli/index.md)** to trigger your flows from your terminal.
 
 You can even [trigger flows without leaving Slack](/blog/handler-slack-commands)!
 
