docs(editor): update the Online Editor articles

astro.config.mjs

@@ -229,7 +229,11 @@ const config = defineConfig({
           'warning',
           'groups',
           'reply',
-          'payments'
+          'payments',
+          'undo'
+        ],
+        garden: [
+          'puzzle-piece-fill-12'
         ],
       }
     })

package.json

@@ -27,6 +27,7 @@
     "@expressive-code/plugin-collapsible-sections": "^0.41.7",
     "@fontsource-variable/noto-sans": "^5.2.10",
     "@fontsource-variable/plus-jakarta-sans": "^5.2.8",
+    "@iconify-json/garden": "^1.2.4",
     "@iconify-json/heroicons": "^1.2.3",
     "@iconify-json/material-symbols": "^1.2.58",
     "@iconify-json/mdi": "^1.2.3",

src/content/docs/crowdin/online-editor/screens-translation.mdx

@@ -31,8 +31,8 @@ Here's a step-by-step guide on how to translate using screens:
   3. On the language page, you will see a list of the project's screenshots instead of usual source files. Click on the needed screenshot to open it in the Editor.
   4. You'll see the full screenshot in the preview panel with text elements on the screenshot highlighted with colored tags.
   5. Click on any highlighted tag on the image. The tag will turn yellow, and the Editor will automatically load the corresponding source string.
-  5. Enter your translation in the text area and click **Save**.
-  6. You can continue clicking other tags on the screenshot to translate them in order. <Image src={screenshotPreview} alt="Editor view with a screenshot preview" />
+  6. Enter your translation in the text area and click <Icon name="mdi:content-save" class="inline-icon" /> **Save translation**.
+  7. You can continue clicking other tags on the screenshot to translate them in order. <Image src={screenshotPreview} alt="Editor view with a screenshot preview" />
 </Steps>
 
 ### Screenshot Preview Options

src/content/docs/enterprise/online-editor/screens-translation.mdx

@@ -31,8 +31,8 @@ Here's a step-by-step guide on how to translate using screens:
   3. On the language page, you will see a list of the project's screenshots instead of usual source files. Click on the needed screenshot to open it in the Editor.
   4. You'll see the full screenshot in the preview panel with text elements on the screenshot highlighted with colored tags.
   5. Click on any highlighted tag on the image. The tag will turn yellow, and the Editor will automatically load the corresponding source string.
-  5. Enter your translation in the text area and click **Save**.
-  6. You can continue clicking other tags on the screenshot to translate them in order. <Image src={screenshotPreview} alt="Editor view with a screenshot preview" />
+  6. Enter your translation in the text area and click <Icon name="mdi:content-save" class="inline-icon" /> **Save translation**.
+  7. You can continue clicking other tags on the screenshot to translate them in order. <Image src={screenshotPreview} alt="Editor view with a screenshot preview" />
 </Steps>
 
 ### Screenshot Preview Options

src/content/docs/enterprise/organization-management/workflows/overview.mdx

@@ -63,9 +63,8 @@ The Switch Source Language step allows you to change the source language of your
   When you download XLIFF files via the language page, Crowdin Enterprise uses the original project source language by default. To ensure your XLIFF contains the newly switched source language instead, follow these steps:
   <Steps>
     1. Open the necessary file in the Editor.
-    2. From the [Workflow menu in the Editor](/enterprise/online-editor/#quick-access-to-menu-sections), select the step that follows the Switch Source Language step.
-    3. Click on the Main menu <Icon name="mdi:menu" class="inline-icon"/> in the upper-left corner.
-    4. In the **File** menu, select **Export Filtered in XLIFF**.
+    2. Go to **Workflow** in the main menu and select the step that follows the Switch Source Language step.
+    3. Go to **File** in the main menu and select **Export Filtered in XLIFF**.
   </Steps>
 
   Because workflows can have complex structures with multiple parallel streams, the system can’t automatically determine which source language to include when downloading from other areas (such as the language page). So, by downloading from the Editor and selecting the step immediately after the Switch Source Language step, you can precisely determine which step of the workflow to export from—ensuring your offline translation file contains the switched source language.