fix: windmill typos

changelog/2024-08-14-continue-on-disapproval/index.md

@@ -9,8 +9,8 @@ features:
     'New toggle to continue flow execution after disapproval.',
     'Would allow to put a branchone right after to handle both cases separately.',
     'New toggle to continue flow execution after disapproval.',
-    'If any disapproval/timeout event is received, the resume payload will be similar to every error result in Winmdill, an object containing an `error` field which you can use to distinguish between approvals and disapproval/timeouts.',
+    'If any disapproval/timeout event is received, the resume payload will be similar to every error result in Windmill, an object containing an `error` field which you can use to distinguish between approvals and disapproval/timeouts.',
   ]
 docs: /docs/flows/flow_approval#continue-on-disapprovaltimeout
 video: /videos/continue_on_disapproval.mp4
----
+---

docs/advanced/11_git_sync/index.mdx

@@ -4,7 +4,7 @@ import TabItem from '@theme/TabItem';
 
 # Git sync
 
-Git sync lets Windmill workspaces be tracked by git. Each time an item is deployed, Widnmill will create and push a commit to the specified repository. It is also possible, and recommended, to setup CI/CD actions that will deploy items on windmill when a new commit is detected, enabling bi-directional synchronization.
+Git sync lets Windmill workspaces be tracked by git. Each time an item is deployed, Windmill will create and push a commit to the specified repository. It is also possible, and recommended, to setup CI/CD actions that will deploy items on windmill when a new commit is detected, enabling bi-directional synchronization.
 
 :::tip Version control
 

docs/flows/11_flow_approval.mdx

@@ -81,7 +81,7 @@ Set a custom timeout after which the flow will be automatically canceled if no a
 
 ### Continue on disapproval/timeout
 
-If set, instead of failing the flow and bubbling up the error, continue to the next step which would allow to put a [branchone](./13_flow_branches.md) right after to handle both cases separately. If any disapproval/timeout event is received, the resume payload will be similar to every error result in Winmdill, an object containing an `error` field which you can use to distinguish between approvals and disapproval/timeouts.
+If set, instead of failing the flow and bubbling up the error, continue to the next step which would allow to put a [branchone](./13_flow_branches.md) right after to handle both cases separately. If any disapproval/timeout event is received, the resume payload will be similar to every error result in Windmill, an object containing an `error` field which you can use to distinguish between approvals and disapproval/timeouts.
 
 ![Continue on disapproval/timeout](../assets/flows/continue_on_disapproval.png 'Continue on disapproval/timeout')
 
@@ -729,4 +729,4 @@ You could use the [Mailchimp Mandrill integration](../integrations/mailchimp_man
 
 <br />
 
-This flow can be found and forked on [Windmill Hub](https://hub.windmill.dev/flows/49/).
+This flow can be found and forked on [Windmill Hub](https://hub.windmill.dev/flows/49/).