suse-coder
diff --git a/‎docs/apps/0_app_editor.md
Lines changed: 4 additions & 4 deletions b/‎docs/apps/0_app_editor.md
Lines changed: 4 additions & 4 deletions
diff --git a/‎docs/apps/4_app_component_library.md
Lines changed: 6 additions & 1 deletion b/‎docs/apps/4_app_component_library.md
Lines changed: 6 additions & 1 deletion
diff --git a/‎docs/apps/5_app-runnable.md
Lines changed: 1 addition & 1 deletion b/‎docs/apps/5_app-runnable.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/getting_started/6_flows_quickstart/branches.png
355 KB b/‎docs/getting_started/6_flows_quickstart/branches.png
355 KB
diff --git a/‎docs/getting_started/6_flows_quickstart/flow_approval_1.png
489 KB b/‎docs/getting_started/6_flows_quickstart/flow_approval_1.png
489 KB
diff --git a/‎docs/getting_started/6_flows_quickstart/flow_approval_2.png
75.2 KB b/‎docs/getting_started/6_flows_quickstart/flow_approval_2.png
75.2 KB
diff --git a/‎docs/getting_started/6_flows_quickstart/flow_approval_3.png
302 KB b/‎docs/getting_started/6_flows_quickstart/flow_approval_3.png
302 KB
diff --git a/‎docs/getting_started/6_flows_quickstart/flow_approval_4.png
323 KB b/‎docs/getting_started/6_flows_quickstart/flow_approval_4.png
323 KB
diff --git a/‎docs/getting_started/6_flows_quickstart/flow_editor_menu.png
504 KB b/‎docs/getting_started/6_flows_quickstart/flow_editor_menu.png
504 KB
diff --git a/‎docs/getting_started/6_flows_quickstart/flows_metadata.png
356 KB b/‎docs/getting_started/6_flows_quickstart/flows_metadata.png
356 KB
@@ -3,10 +3,10 @@
 Windmill's App editor allows you to build internal applications. Windmill's App editor has the following major components:
 
 - [Toolbar](./app_toolbar): configure app settings, toggle preview (desktop/mobile) and debug runs.
-- [Outputs](./app_outputs): View all components outputs and context
-- [Canvas](./app_canvas): Drag, drop and resize components on the canvas.
-- [Component Library](./app_component_library): Insert any component or modify the property or styling.
-- [Runnable editor](./app-runnable): Create, edit or manage the scripts or flows linked to components (Runnable), and background scripts.
+- [Outputs](./app_outputs): view all components outputs and context.
+- [Canvas](./app_canvas): drag, drop and resize components on the canvas.
+- [Component Library](./app_component_library): insert any component or modify the property or styling.
+- [Runnable editor](./app-runnable): create, edit or manage the scripts or flows linked to components (Runnable), and background scripts.
 
   ![App Editor](../assets/apps/0_app_editor/plain-app-editor.png)
 
 
@@ -8,14 +8,19 @@ Component can be configured in three ways:
 
 - **Inputs**: inputs can be connected to an output or computed using a runnable.
   - e.g. `Table` component has an input that can be connected to an output or computed using a runnable, which is an array of objects.
+  <br/>
+
+
 - **Configuration**: property such as the button label, the text input placeholder, etc.
   - e.g. `Table` component has a configuration property that allows you to configure the search bar: Client-side search, Server-side search, or no search.
 
 ## Component outputs
 
 - **Runnable**: some component can trigger a runnable when an event occurs, usually when a user interacts with the component. The result of the runnable is stored in the component output in the key `result`. It also stores the `loading` state of the component.
   - e.g. `Button` component can trigger a runnable when clicked.
-- **Own outputs**: Some component have outputs defined by the component.
+<br/>
+
+- **Own outputs**: some component have outputs defined by the component.
   - e.g. `Table` component has a selectedRow output
 
 ## Inserting components
 
@@ -2,7 +2,7 @@
 
 On the bottom of the app editor, you can find the runnable editor. It allows you to create, edit or manage the scripts or flows linked to components (Runnable), and background scripts. 
 
-You can also fork scripts from :
+You can also fork scripts from:
 - Inline scripts: scripts that are defined on the app editor, linked to a component.
 - Workspace/Hub: scripts linked to a component, but defined in the workspace or the Hub.
 - Background scripts: scripts that are not linked to a component, but run in the background.