Update Documentation.md

AppExamples/script_icons/ScriptIcon/doc/Documentation.md

@@ -7,9 +7,8 @@
 
 This is a small example to show how an icon can be set to a script, whereas the icon itself resides in the App as a resource.
 
-```{note}
-This example is meant as addition to the information given in how-to: [Adding workspaces to packages - Icon guidelines](../../howtos/adding_workspaces_to_apps/adding_workspaces_to_apps.md#icon-guidelines).
-```
+> [!NOTE]
+> This example is meant as addition to the information given in how-to: [Adding workspaces to packages - Icon guidelines](https://zeissiqs.github.io/zeiss-inspect-addon-api/main/howtos/adding_workspaces_to_apps/adding_workspaces_to_apps.html#icon-guidelines).
 
 ## Highlights
 
@@ -19,10 +18,10 @@ However, using VS Code or another text editor, the corresponding `.metainfo` fil
 
 ![Icon file reference in script properties](script_icon_from_file.jpg)
 
-If you use this approach, and follow our [icon guidelines](../../howtos/adding_workspaces_to_apps/adding_workspaces_to_apps.md#icon-guidelines), the icons get inverted in dark themes automatically.
+If you use this approach, and follow our [icon guidelines](https://zeissiqs.github.io/zeiss-inspect-addon-api/main/howtos/adding_workspaces_to_apps/adding_workspaces_to_apps.html#icon-guidelines), the icons get inverted in dark themes automatically.
 
 ![Menu entry with icon, dark background](menu_icon_darkbg.jpg)
 
 ## Related
 
-* How-to: [Adding workspaces to packages](https://zeissiqs.github.io/zeiss-inspect-addon-api/2025/howtos/adding_workspaces_to_apps/adding_workspaces_to_apps.md)
+* How-to: [Adding workspaces to packages](https://zeissiqs.github.io/zeiss-inspect-addon-api/2025/howtos/adding_workspaces_to_apps/adding_workspaces_to_apps.md)