Bun ts extension and Deploy to prod refresh

docs/advanced/5_sharing_common_logic/index.mdx

@@ -69,19 +69,25 @@ scripts locally and on Windmill. See [Developing scripts locally](../4_local_dev
 
 ## Deno or Bun relative imports for sharing common logic
 
-Similarly to Python, it is possible to import directly from other TypeScript scripts. One can simply follow the path layout. For instance,
+Similarly to [Python](#python-relative-imports-for-sharing-common-logic), it is possible to import directly from other TypeScript scripts. One can simply follow the path layout. For instance,
 `import { foo } from "/f/<foldername>/script_name.ts"`. A more verbose example below:
 
 ```typescript
 import { main as foo, util } from '../my_script_path.ts';
 ```
 
+With [Bun](../../getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx), you don't need to specify the `.ts` file extension (it is only required for the [Deno](../../getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx#deno) runtime):
+
+```typescript
+import { main as foo, util } from '../my_script_path';
+```
+
 Relative imports syntax is much preferred as it will work on [local editors](../4_local_development/index.mdx) without further configuration.
 
 You may also use absolute imports:
 
 ```typescript
-import { main as foo, util } from '/f/common/my_script_path.ts';
+import { main as foo, util } from '/f/common/my_script_path';
 
 export async function main() {
 	await foo();
@@ -101,7 +107,7 @@ but to make it work with your local editor, you will need the following configur
 }
 ```
 
-Note that path in Windmill can have as many depth as needed, so you can have paths like this `f/folder/subfolder/my_script_path.ts` and relative imports will work at any level. Hence, it will work exactly the same as on local.
+Note that [paths](../../core_concepts/16_roles_and_permissions/index.mdx#path) in Windmill can have as many depth as needed, so you can have paths like this `f/folder/subfolder/my_script_path` and relative imports will work at any level. Hence, it will work exactly the same as on local.
 
 ### Bundle per Script built by CLI
 

docs/core_concepts/0_draft_and_deploy/index.mdx

@@ -12,7 +12,7 @@ Once deployed, scripts, flows and apps will be visible, editable and/or runnable
 
 :::tip Deploy to prod
 
-For all details on Deployments to Prods, see [Deploy to prod](../../advanced/12_deploy_to_prod/index.mdx).
+For all details on Deployments to Prod, see [Deploy to prod](../../advanced/12_deploy_to_prod/index.mdx).
 
 :::
 

docs/core_concepts/12_staging_prod/index.md

@@ -4,7 +4,7 @@ From a workspace in Windmill, you can deploy a script/flow/resource/variable and
 
 :::tip Deploy to prod
 
-For all details on Deployments to Prods, see [Deploy to prod](../../advanced/12_deploy_to_prod/index.mdx).
+For all details on Deployments to Prod, see [Deploy to prod](../../advanced/12_deploy_to_prod/index.mdx).
 
 :::
 
@@ -25,9 +25,9 @@ The [Draft and deploy](../0_draft_and_deploy/index.mdx) is another feature that
 
 ## How it works
 
-For users with admin rights on the source workspace, in the `Workspace` menu, go to the "Dev/Staging/Prod" tab and pick a workspace for "Workspace to link to".
+For users with admin rights on the source workspace, in the `Workspace` settings, go to the "Deployment UI" tab and pick a workspace for "Workspace to link to".
 
-![Link to a workspace](./workspace_to_link_to.png.webp 'Link to a workspace')
+![Link to a workspace](./workspace_to_link_to.png 'Link to a workspace')
 
 This workspace to link to can for example be: