From 9ddca0249fc42f771c9a9e239b2dd48ee09d3195 Mon Sep 17 00:00:00 2001
From: Simon Graband <sgraband@eclipsesource.com>
Date: Tue, 10 Dec 2024 16:05:50 +0100
Subject: [PATCH] Updating publishing guide and set markdown formatter (#14553)

- Set formatter for markdown files
- Format all markdown files
- Update publishing guide

Signed-off-by: Simon Graband <sgraband@eclipsesource.com>
---
 .theia/settings.json                          |  10 +-
 .vscode/extensions.json                       |   3 +-
 .vscode/settings.json                         |  10 +-
 CODE_OF_CONDUCT.md                            |   6 +-
 CONTRIBUTING.md                               |   4 +-
 NOTICE.md                                     | 128 ++++---
 README.md                                     |   1 +
 dev-packages/application-manager/README.md    |   3 +-
 dev-packages/application-package/README.md    |   3 +-
 dev-packages/cli/README.md                    |  15 +-
 dev-packages/localization-manager/README.md   |   4 +-
 dev-packages/native-webpack-plugin/README.md  |   3 +-
 dev-packages/ovsx-client/README.md            |   3 +-
 dev-packages/private-eslint-plugin/README.md  |  18 +-
 dev-packages/private-ext-scripts/README.md    |   4 +-
 dev-packages/request/README.md                |   3 +-
 doc/Developing.md                             | 236 +++++++------
 doc/Migration.md                              |   6 +-
 doc/Publishing.md                             | 327 ++++++++++++------
 doc/Testing.md                                |  23 +-
 doc/api-management.md                         |   7 +-
 doc/api-testing.md                            |   3 +
 doc/changelogs/CHANGELOG-2019.md              |  44 +--
 doc/changelogs/CHANGELOG-2020.md              |  34 +-
 doc/changelogs/CHANGELOG-2021.md              |   2 +-
 doc/changelogs/CHANGELOG-2022.md              |  12 +-
 doc/code-organization.md                      |   2 +-
 doc/coding-guidelines.md                      |  96 ++++-
 doc/pull-requests.md                          |  27 +-
 doc/runtime-policy.md                         |   6 +-
 doc/vscode-usage.md                           |   6 +-
 examples/api-provider-sample/README.md        |   6 +-
 examples/api-samples/README.md                |   4 +-
 examples/playwright/README.md                 |   2 +-
 package.json                                  |   1 +
 packages/ai-chat-ui/README.md                 |   3 +-
 packages/ai-chat/README.md                    |   3 +-
 packages/ai-code-completion/README.md         |   3 +-
 packages/ai-core/README.md                    |   3 +-
 packages/ai-history/README.md                 |   3 +-
 packages/ai-hugging-face/README.md            |   2 +-
 packages/ai-llamafile/README.md               |  14 +-
 packages/ai-openai/README.md                  |   3 +-
 packages/ai-terminal/README.md                |  10 +-
 packages/ai-workspace-agent/README.md         |   3 +-
 packages/bulk-edit/README.md                  |   3 +-
 packages/callhierarchy/README.md              |   3 +-
 packages/collaboration/README.md              |   3 +-
 packages/console/README.md                    |   3 +-
 packages/core/README.md                       |  82 ++---
 packages/core/README_TEMPLATE.md              |  10 +-
 packages/debug/README.md                      |  21 +-
 packages/dev-container/README.md              |   7 +-
 packages/editor-preview/README.md             |  16 +-
 packages/editor/README.md                     |   3 +-
 packages/electron/README.md                   |  11 +-
 packages/electron/README_TEMPLATE.md          |   5 +-
 packages/external-terminal/README.md          |   6 +-
 packages/file-search/README.md                |   3 +-
 packages/filesystem/README.md                 |   3 +-
 .../filesystem/src/common/download/README.md  |  12 +-
 packages/getting-started/README.md            |   4 +-
 packages/git/README.md                        |   4 +-
 packages/keymaps/README.md                    |   9 +-
 packages/markers/README.md                    |   4 +-
 packages/memory-inspector/README.md           |   4 +-
 packages/messages/README.md                   |   3 +-
 packages/metrics/README.md                    |   3 +-
 packages/mini-browser/README.md               |   3 +-
 packages/monaco/README.md                     |  33 +-
 packages/navigator/README.md                  |   3 +-
 packages/notebook/README.md                   |   3 +-
 packages/outline-view/README.md               |   3 +-
 packages/output/README.md                     |   3 +-
 packages/plugin-dev/README.md                 |   4 +-
 packages/plugin-ext-headless/README.md        |   3 +-
 packages/plugin-ext-vscode/README.md          |   4 +-
 packages/plugin-ext/README.md                 |   5 +-
 packages/plugin-metrics/README.md             |   7 +-
 packages/plugin/README.md                     |  26 +-
 packages/preferences/README.md                |  23 +-
 packages/preview/README.md                    |   3 +-
 packages/process/README.md                    |   3 +-
 packages/property-view/README.md              |   5 +-
 packages/remote/README.md                     |   2 +-
 packages/scm-extra/README.md                  |   4 +-
 packages/scm/README.md                        |   3 +-
 packages/search-in-workspace/README.md        |   4 +-
 packages/task/README.md                       |  13 +-
 packages/terminal/README.md                   |   3 +-
 packages/timeline/README.md                   |   3 +-
 packages/toolbar/README.md                    |   5 +-
 packages/typehierarchy/README.md              |   3 +-
 packages/userstorage/README.md                |   7 +-
 packages/variable-resolver/README.md          |   9 +-
 packages/vsx-registry/README.md               |   3 +-
 packages/workspace/README.md                  |   3 +-
 .../sample-namespace/plugin-gotd/README.md    |   4 +-
 scripts/performance/README.md                 |  46 +--
 99 files changed, 961 insertions(+), 613 deletions(-)

diff --git a/.theia/settings.json b/.theia/settings.json
index 23199246981cf..d6872327e715c 100644
--- a/.theia/settings.json
+++ b/.theia/settings.json
@@ -11,5 +11,13 @@
     "editor.tabSize": 2
   },
   "typescript.tsdk": "node_modules/typescript/lib",
-  "clang-format.language.typescript.enable": false
+  "clang-format.language.typescript.enable": false,
+  "[markdown]": {
+    "editor.defaultFormatter": "davidanson.vscode-markdownlint"
+  },
+  "markdownlint.config": {
+    "MD032": false, // don't require blank line around lists 
+    "MD033": false, // allow inline html
+    "MD041": false // don't require h1 in first line
+  },
 }
diff --git a/.vscode/extensions.json b/.vscode/extensions.json
index 517d760915049..4f803f4512200 100644
--- a/.vscode/extensions.json
+++ b/.vscode/extensions.json
@@ -3,7 +3,8 @@
   // Extension identifier format: ${publisher}.${name}. Example: vscode.csharp
   // List of extensions which should be recommended for users of this workspace.
   "recommendations": [
-    "dbaeumer.vscode-eslint"
+    "dbaeumer.vscode-eslint",
+    "DavidAnson.vscode-markdownlint"
   ],
   // List of extensions recommended by VS Code that should not be recommended for users of this workspace.
   "unwantedRecommendations": []
diff --git a/.vscode/settings.json b/.vscode/settings.json
index 8166ed2cb0656..a07b759be7e50 100644
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -51,6 +51,9 @@
     "editor.tabSize": 2,
     "editor.defaultFormatter": "vscode.json-language-features",
   },
+  "[markdown]": {
+    "editor.defaultFormatter": "DavidAnson.vscode-markdownlint"
+  },
   "typescript.tsdk": "node_modules/typescript/lib",
   "files.insertFinalNewline": true,
   "clang-format.language.typescript.enable": false,
@@ -63,5 +66,10 @@
     "editor.defaultFormatter": "vscode.typescript-language-features",
     "typescript.preferences.quoteStyle": "single",
     "editor.tabSize": 4,
-  }
+  },
+  "markdownlint.config": {
+    "MD032": false, // don't require blank line around lists 
+    "MD033": false, // allow inline html
+    "MD041": false // don't require h1 in first line
+  },
 }
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index f5254ea3e68ce..88ca1cbd71529 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -43,15 +43,15 @@ This Code of Conduct applies within all project spaces, and it also applies when
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at codeofconduct@eclipse.org. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at <codeofconduct@eclipse.org>. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
 Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
 
-For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
+For answers to common questions about this code of conduct, see <https://www.contributor-covenant.org/faq>
 
 <div id="theia-logo" align="left">
     <br />
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d60d3f404c49d..94567955134fb 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -55,7 +55,7 @@ We follow the coding guidelines described
 Before your contribution can be accepted by the project team contributors must
 electronically sign the Eclipse Contributor Agreement (ECA).
 
-* https://www.eclipse.org/legal/ECA.php
+* <https://www.eclipse.org/legal/ECA.php>
 
 Commits that are provided by non-committers must have a Signed-off-by field in
 the footer indicating that the author is aware of the terms by which the
@@ -64,7 +64,7 @@ additionally have an Eclipse Foundation account and must have a signed Eclipse
 Contributor Agreement (ECA) on file.
 
 For more information, please see the Eclipse Committer Handbook:
-https://www.eclipse.org/projects/handbook/#resources-commit
+<https://www.eclipse.org/projects/handbook/#resources-commit>
 
 ## Sign your work
 
diff --git a/NOTICE.md b/NOTICE.md
index a68be8b716cb6..8f780786a7156 100644
--- a/NOTICE.md
+++ b/NOTICE.md
@@ -2,7 +2,7 @@
 
 This content is produced and maintained by the Eclipse Theia project.
 
-* Project home: https://projects.eclipse.org/projects/ecd.theia
+* Project home: <https://projects.eclipse.org/projects/ecd.theia>
 
 ## Trademarks
 
@@ -18,12 +18,12 @@ source code repository logs.
 
 This program and the accompanying materials are made available under the terms
 of the Eclipse Public License v. 2.0 which is available at
-https://www.eclipse.org/legal/epl-2.0. This Source Code may also be made
+<https://www.eclipse.org/legal/epl-2.0>. This Source Code may also be made
 available under the following Secondary Licenses when the conditions for such
 availability set forth in the Eclipse Public License v. 2.0 are satisfied:
 (secondary) GPL-2.0 with Classpath-exception-2.0 which is available at GNU
 General Public License v2.0 w/Classpath exception',
-'https://www.gnu.org/software/classpath/license.html.
+'<https://www.gnu.org/software/classpath/license.html>.
 
 SPDX-License-Identifier: EPL-2.0 OR GPL-2.0-only WITH Classpath-exception-2.0
 
@@ -31,16 +31,16 @@ SPDX-License-Identifier: EPL-2.0 OR GPL-2.0-only WITH Classpath-exception-2.0
 
 The project maintains the following source code repositories:
 
-* https://github.com/eclipse-theia/theia
-* https://github.com/eclipse/theia-generator-plugin
-* https://github.com/eclipse/theia-yeoman-plugin
-* https://github.com/eclipse/theia-plugin-packager
-* https://github.com/eclipse-theia/theia-cpp-extensions
-* https://github.com/eclipse/theia-python-extension
-* https://github.com/eclipse/theia-java-extension
-* https://github.com/eclipse-theia/theia-example
-* https://github.com/eclipse-theia/cryptodetector
-* https://github.com/eclipse-theia/generator-theia-extension
+* <https://github.com/eclipse-theia/theia>
+* <https://github.com/eclipse/theia-generator-plugin>
+* <https://github.com/eclipse/theia-yeoman-plugin>
+* <https://github.com/eclipse/theia-plugin-packager>
+* <https://github.com/eclipse-theia/theia-cpp-extensions>
+* <https://github.com/eclipse/theia-python-extension>
+* <https://github.com/eclipse/theia-java-extension>
+* <https://github.com/eclipse-theia/theia-example>
+* <https://github.com/eclipse-theia/cryptodetector>
+* <https://github.com/eclipse-theia/generator-theia-extension>
 
 ## Third-party Content
 
@@ -49,8 +49,8 @@ This project leverages the following third party content.
 chalk (2.4.1)
 
 * License: MIT
-* Project: https://github.com/chalk/chalk
-* Source: https://github.com/chalk/chalk
+* Project: <https://github.com/chalk/chalk>
+* Source: <https://github.com/chalk/chalk>
 
 code copied from project cortex-debug (0.1.21)
 
@@ -63,8 +63,8 @@ Code copied from project Microsoft/vscode (1.31.0)
 Code copied from project Microsoft/vscode (1.32.3)
 
 * License: MIT
-* Project: https://code.visualstudio.com/
-* Source: https://github.com/Microsoft/vscode
+* Project: <https://code.visualstudio.com/>
+* Source: <https://github.com/Microsoft/vscode>
 
 Code copied from project Microsoft/vscode (1.32.3)
 
@@ -108,7 +108,6 @@ code copied from project vscode (1.34.0)
 
 code copied from project vscode (1.36.1)
 
-
 code copied from project vscode (1.36.1)
 
 * License: MIT
@@ -178,14 +177,14 @@ electron@2.0.14 (2.0.14)
    AND BSD-3-Clause AND ISC AND X11 AND Public-Domain AND (GPL-2.0 OR MIT) AND
    Unlicense AND IJG AND ICU AND UNICODE-TOU AND NTP AND (MIT OR BSD-3-Clause)
    AND Libpng AND MPL-2.0 AND LGPL-2.1+
-* Project: https://github.com/electron/electron
-* Source: https://github.com/electron/electron/releases/tag/v2.0.14
+* Project: <https://github.com/electron/electron>
+* Source: <https://github.com/electron/electron/releases/tag/v2.0.14>
 
 getmac (1.4.6)
 
 * License: MIT
-* Project: https://github.com/bevry/getmac
-* Source: https://github.com/bevry/getmac
+* Project: <https://github.com/bevry/getmac>
+* Source: <https://github.com/bevry/getmac>
 
 GH-3397: Implemented the HTTP-based authentication for Git in Electron. (n/a)
 
@@ -194,15 +193,15 @@ GH-3397: Implemented the HTTP-based authentication for Git in Electron. (n/a)
 glob promise (3.4.0)
 
 * License: ISC
-* Project: https://github.com/ahmadnassri/glob-promise
-* Source: https://github.com/ahmadnassri/glob-promise
+* Project: <https://github.com/ahmadnassri/glob-promise>
+* Source: <https://github.com/ahmadnassri/glob-promise>
 
 Icon configure-inverse.svg (n/a)
 
 * License: MIT
-* Project: https://github.com/Microsoft/vscode
+* Project: <https://github.com/Microsoft/vscode>
 * Source:
-   https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/contrib/tasks/common/media/configure-inverse.svg#L1
+   <https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/contrib/tasks/common/media/configure-inverse.svg#L1>
 
 Icons copied from microsoft/vscode-icons version:
 b73945c70f1117c4e65939dd3e10bdd623cb4ef3 (n/a)
@@ -216,9 +215,9 @@ inversify (5.0.1)
 jschardet (1.6.0)
 
 * License: (LGPL-2.1 OR LGPL-2.1+) AND (MIT OR GPL-2.0)
-* Project: https://www.npmjs.com/package/jschardet
+* Project: <https://www.npmjs.com/package/jschardet>
 * Source:
-   https://github.com/aadsm/jschardet/tree/28152dd8db5904dc2cf9aa12ef4f8783f713e79a
+   <https://github.com/aadsm/jschardet/tree/28152dd8db5904dc2cf9aa12ef4f8783f713e79a>
 
 jschardet (2.1.1)
 
@@ -243,20 +242,20 @@ long.js (3.2.0)
 micromatch (3.1.10)
 
 * License: MIT
-* Project: https://github.com/micromatch/micromatch
-* Source: https://github.com/micromatch/micromatch
+* Project: <https://github.com/micromatch/micromatch>
+* Source: <https://github.com/micromatch/micromatch>
 
 monaco-typescript (2.3.0)
 
 * License: MIT
-* Project: https://github.com/Microsoft/monaco-typescript
-* Source: https://github.com/Microsoft/monaco-typescript.git
+* Project: <https://github.com/Microsoft/monaco-typescript>
+* Source: <https://github.com/Microsoft/monaco-typescript.git>
 
 native-keymap (1.2.5)
 
 * License: BSD-3-Clause AND MIT
-* Project: https://github.com/Microsoft/node-native-keymap
-* Source: https://github.com/Microsoft/node-native-keymap
+* Project: <https://github.com/Microsoft/node-native-keymap>
+* Source: <https://github.com/Microsoft/node-native-keymap>
 
 node-oniguruma (n/a)
 
@@ -272,24 +271,23 @@ node.js dependencies for Theia (n/a)
 
 Preference code copied from vscode (n/a)
 
-
 ps-list (5.0.1)
 
 * License: MIT
-* Project: https://github.com/sindresorhus/ps-list
-* Source: https://github.com/sindresorhus/ps-list
+* Project: <https://github.com/sindresorhus/ps-list>
+* Source: <https://github.com/sindresorhus/ps-list>
 
 react-perfect-scrollbar:1.5.3 (1.5.3)
 
 * License: MIT
-* Project: https://github.com/goldenyz/react-perfect-scrollbar
-* Source: https://github.com/goldenyz/react-perfect-scrollbar
+* Project: <https://github.com/goldenyz/react-perfect-scrollbar>
+* Source: <https://github.com/goldenyz/react-perfect-scrollbar>
 
 read-pkg (4.0.1)
 
 * License: MIT
-* Project: https://github.com/sindresorhus/read-pkg
-* Source: https://github.com/sindresorhus/read-pkg
+* Project: <https://github.com/sindresorhus/read-pkg>
+* Source: <https://github.com/sindresorhus/read-pkg>
 
 regular expressions and helper function copied from microsoft/vscode (1.33.1)
 
@@ -298,8 +296,8 @@ regular expressions and helper function copied from microsoft/vscode (1.33.1)
 requestretry (3.1.0)
 
 * License: MIT
-* Project: https://github.com/FGRibreau/node-request-retry
-* Source: https://github.com/FGRibreau/node-request-retry
+* Project: <https://github.com/FGRibreau/node-request-retry>
+* Source: <https://github.com/FGRibreau/node-request-retry>
 
 rimraf (2.6.2)
 
@@ -326,8 +324,8 @@ theia-cpp-extension npm node (n/a)
 tslint (5.10.0)
 
 * License: Apache-2.0 AND MIT
-* Project: http://palantir.github.io/tslint/
-* Source: https://github.com/palantir/tslint
+* Project: <http://palantir.github.io/tslint/>
+* Source: <https://github.com/palantir/tslint>
 
 typefox/monaco-language-client (0.5.0)
 
@@ -336,8 +334,8 @@ typefox/monaco-language-client (0.5.0)
 typescript-formatter (7.2.2)
 
 * License: MIT
-* Project: https://github.com/vvakame/typescript-formatter
-* Source: https://github.com/vvakame/typescript-formatter
+* Project: <https://github.com/vvakame/typescript-formatter>
+* Source: <https://github.com/vvakame/typescript-formatter>
 
 VS Code (1.33.0)
 
@@ -345,7 +343,7 @@ VS Code (1.33.0)
 
 VS Code built-in extensions (1.30.1)
 
-* License: Apache-2.0 AND MIT AND Unicode-DFS-2016 AND CC-BY-4.0 AND W3C 
+* License: Apache-2.0 AND MIT AND Unicode-DFS-2016 AND CC-BY-4.0 AND W3C
 
 vscode (1.26.0)
 
@@ -382,14 +380,14 @@ vscode-java-debug (0.15.0)
 webdriverio (n/a)
 
 * License: MIT
-* Project: http://webdriver.io/
-* Source: https://github.com/webdriverio/webdriverio.git
+* Project: <http://webdriver.io/>
+* Source: <https://github.com/webdriverio/webdriverio.git>
 
 when (3.7.8)
 
 * License: MIT
-* Project: https://github.com/cujojs/when
-* Source: https://github.com/cujojs/when
+* Project: <https://github.com/cujojs/when>
+* Source: <https://github.com/cujojs/when>
 
 wjordan/browser-path SHA6719d19077b1454bff8b802f9be79cb1b69ebe7e (n/a)
 
@@ -406,8 +404,8 @@ xterm-addon-search (0.5.0)
 xterm.js (3.9.1)
 
 * License: MIT
-* Project: https://xtermjs.org/
-* Source: https://github.com/xtermjs/xterm.js
+* Project: <https://xtermjs.org/>
+* Source: <https://github.com/xtermjs/xterm.js>
 
 xterm.js (4.4)
 
@@ -416,32 +414,32 @@ xterm.js (4.4)
 yargs (12.0.1)
 
 * License: MIT
-* Project: http://yargs.js.org/
-* Source: https://github.com/yargs/yargs
+* Project: <http://yargs.js.org/>
+* Source: <https://github.com/yargs/yargs>
 
 yeoman environment (2.3.0)
 
 * License: BSD-2-Clause AND BSD-3-Clause
-* Project: https://github.com/yeoman/environment
-* Source: https://github.com/yeoman/environment
+* Project: <https://github.com/yeoman/environment>
+* Source: <https://github.com/yeoman/environment>
 
 yeoman generator (3.0.0)
 
 * License: BSD-2-Clause AND BSD-3-Clause
-* Project: http://yeoman.io
-* Source: https://github.com/yeoman/generator
+* Project: <http://yeoman.io>
+* Source: <https://github.com/yeoman/generator>
 
 yeoman-generator (2.0)
 
 * License: BSD-2-Clause
-* Project: http://yeoman.io/
-* Source: https://github.com/yeoman/generator
+* Project: <http://yeoman.io/>
+* Source: <https://github.com/yeoman/generator>
 
 yosay (2.0.2)
 
 * License: BSD-2-Clause
-* Project: https://github.com/yeoman/yosay
-* Source: https://github.com/yeoman/yosay
+* Project: <https://github.com/yeoman/yosay>
+* Source: <https://github.com/yeoman/yosay>
 
 ## Cryptography
 
@@ -470,4 +468,4 @@ licensing fees.
 We strongly recommend downstream consumers verify the type of FFmpeg support
 configured and modify as required.  More information on instructions to verify
 can be found here
-https://electronjs.org/docs/development/upgrading-chromium#verify-ffmpeg-support
+<https://electronjs.org/docs/development/upgrading-chromium#verify-ffmpeg-support>
diff --git a/README.md b/README.md
index 7787064ed858a..4daa9413cfb1e 100644
--- a/README.md
+++ b/README.md
@@ -41,6 +41,7 @@ Eclipse Theia is an extensible framework to develop full-fledged multi-language
 [Visit the Eclipse Theia website](http://www.theia-ide.org) for more information and [the Theia documentation](http://www.theia-ide.org/docs).
 
 ## Repositories
+
 This is the main repository for the Eclipse Theia project, containing the sources of the Theia Platform. Please open generic discussions, bug reports and feature requests about Theia on this repository. The Theia project also includes additional repositories, e.g. for the [artifacts building the Theia IDE](https://github.com/eclipse-theia/theia-blueprint) and the [Theia website](https://github.com/eclipse-theia/theia-website). Please also see the [overview of all Theia project repositories](https://github.com/eclipse-theia).
 
 ## Releases
diff --git a/dev-packages/application-manager/README.md b/dev-packages/application-manager/README.md
index 89d817501ff62..56e508ee70598 100644
--- a/dev-packages/application-manager/README.md
+++ b/dev-packages/application-manager/README.md
@@ -21,5 +21,6 @@
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/dev-packages/application-package/README.md b/dev-packages/application-package/README.md
index 01a8559541457..6290023cad7bd 100644
--- a/dev-packages/application-package/README.md
+++ b/dev-packages/application-package/README.md
@@ -21,5 +21,6 @@
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/dev-packages/cli/README.md b/dev-packages/cli/README.md
index 5412e8b766731..c2637add081cb 100644
--- a/dev-packages/cli/README.md
+++ b/dev-packages/cli/README.md
@@ -103,6 +103,7 @@ For example, an application can update the preference value for `files.enableTra
 ### Default Theme
 
 Default color and icon themes can be configured in `theia.frontend.config` section:
+
 ```json
 "theia": {
     "frontend": {
@@ -219,7 +220,7 @@ To run the backend server:
 
     theia start
 
-For the browser target a server is started on http://localhost:3000 by default.
+For the browser target a server is started on <http://localhost:3000> by default.
 For the electron target a server is started on `localhost` host with the dynamically allocated port by default.
 
 Arguments are passed directly to a server, use `--help` to learn which options are supported.
@@ -230,8 +231,7 @@ To debug the backend server:
 
     theia start --inspect
 
-Theia CLI accepts `--inspect` node flag: https://nodejs.org/en/docs/inspector/#command-line-options.
-
+Theia CLI accepts `--inspect` node flag: <https://nodejs.org/en/docs/inspector/#command-line-options>.
 
 ## Testing
 
@@ -324,8 +324,10 @@ The property `theiaPlugins` describes the list of plugins to download, for examp
     "rust-analyzer": "https://open-vsx.org/api/rust-lang/rust-analyzer/${targetPlatform}/0.4.1473/file/rust-lang.rust-analyzer-0.4.1473@${targetPlatform}.vsix"
 }
 ```
-As seen in the `rust-analyzer` entry we can use placeholders in the URLs. Supported placeholders are: 
-- The `${targetPlatform}` Placeholder, which resolves to a string like `win32-x64` describing the local system and architecture. This is useful for adding non-universal plugins. 
+
+As seen in the `rust-analyzer` entry we can use placeholders in the URLs. Supported placeholders are:
+
+- The `${targetPlatform}` Placeholder, which resolves to a string like `win32-x64` describing the local system and architecture. This is useful for adding non-universal plugins.
 
 Please note that in order to use `extensionPacks` properly you should use `namespace.name` as the `id` you give extensions so that when resolving the pack we do not re-download an existing plugin under a different name.
 
@@ -363,5 +365,6 @@ bundled-application.exe --no-cluster
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/dev-packages/localization-manager/README.md b/dev-packages/localization-manager/README.md
index b4cffc00468c2..d6d4f9fea1b2e 100644
--- a/dev-packages/localization-manager/README.md
+++ b/dev-packages/localization-manager/README.md
@@ -45,7 +45,6 @@ Additionally, Theia provides a simple way to translate the generated JSON files
 }
 ```
 
-
 Only JSON entries without corresponding translations are translated using DeepL. This ensures that manual changes to the translated files aren't overwritten and only new translation entries are actually sent to DeepL.
 
 Use `theia nls-localize --help` for more information on how to use the command and supply DeepL API keys.
@@ -63,5 +62,6 @@ For more information, see the [internationalization documentation](https://theia
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/dev-packages/native-webpack-plugin/README.md b/dev-packages/native-webpack-plugin/README.md
index 4226f155557d1..f377298ae0792 100644
--- a/dev-packages/native-webpack-plugin/README.md
+++ b/dev-packages/native-webpack-plugin/README.md
@@ -25,5 +25,6 @@ The `@theia/native-webpack-plugin` package contains a webpack plugin that is use
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/dev-packages/ovsx-client/README.md b/dev-packages/ovsx-client/README.md
index 055ae72421a97..a2a68b5407e1e 100644
--- a/dev-packages/ovsx-client/README.md
+++ b/dev-packages/ovsx-client/README.md
@@ -57,5 +57,6 @@ This class is an `OVSXClient` that can delegate requests to sub-clients based on
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/dev-packages/private-eslint-plugin/README.md b/dev-packages/private-eslint-plugin/README.md
index e8cd91259b622..51cb5c8158fd6 100644
--- a/dev-packages/private-eslint-plugin/README.md
+++ b/dev-packages/private-eslint-plugin/README.md
@@ -17,30 +17,32 @@ The plugin helps identify problems during development through static analysis in
 
 ## Rules
 
-### `annotation-check`:
+### `annotation-check`
 
 Inversify >=6.1 requires to annotate all constructor parameters of injectable classes as otherwise runtime errors are thrown.
 The rule checks that all constructor parameters of injectable classes are annotated with `@inject`, `@unmanaged` or `@multiInject`.
 
-### `localization-check`:
+### `localization-check`
 
 The rule prevents the following localization related issues:
+
 - incorrect usage of the `nls.localizeByDefault` function by using an incorrect default value.
 - unnecessary call to `nls.localize` which could be replaced by `nls.localizeByDefault`.
 
-### `no-src-import`:
+### `no-src-import`
 
 The rule prevents imports using `/src/` rather than `/lib/` as it causes build failures.
 The rule helps developers more easily identify the cause of build errors caused by the incorrect import.
 
-#### `runtime-import-check`:
+#### `runtime-import-check`
 
 The rule prevents imports from folders meant for incompatible runtimes.
 The check enforces the [code organization guidelines](https://github.com/eclipse-theia/theia/wiki/Code-Organization) of the framework and guards against invalid imports which may cause unforeseen issues downstream.
 
-#### `shared-dependencies`:
+#### `shared-dependencies`
 
 The rule prevents the following:
+
 - prevents the implicit use of a shared dependency from `@theia/core`.
 - prevents extensions from depending on a shared dependency without re-using it from `@theia/core`.
 
@@ -51,10 +53,10 @@ The rule prevents the following:
 
 ## License
 
--   [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
--   [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
+- [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
+- [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
 
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/dev-packages/private-ext-scripts/README.md b/dev-packages/private-ext-scripts/README.md
index 057b6a45db002..40ac1f5425108 100644
--- a/dev-packages/private-ext-scripts/README.md
+++ b/dev-packages/private-ext-scripts/README.md
@@ -12,7 +12,6 @@
 
 ## Description
 
-
 `theiaext` is a command line tool to run shared npm scripts in Theia packages.\
 For instance, if you want add a new `hello` script that prints `Hello World`:
 
@@ -66,5 +65,6 @@ For instance, if you want add a new `hello` script that prints `Hello World`:
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/dev-packages/request/README.md b/dev-packages/request/README.md
index bd9f1db2623c1..e6a05e0bf4156 100644
--- a/dev-packages/request/README.md
+++ b/dev-packages/request/README.md
@@ -25,5 +25,6 @@ The `@theia/request` package is used to send proxy-aware http requests to other
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/doc/Developing.md b/doc/Developing.md
index f8c111a41a656..5689721da4cbc 100644
--- a/doc/Developing.md
+++ b/doc/Developing.md
@@ -3,6 +3,7 @@ the world of Theia development. Are you in a hurry? See the
 [Quick Start](#quick-start).
 
 # How to build Theia and the example applications
+
 Theia is a framework to build IDEs, so you can't really "run" Theia itself.
 However, you can run the example applications included in its repository. One
 is a browser-based IDE and the other is the Electron-based equivalent.
@@ -11,52 +12,52 @@ The following instructions are for Linux and macOS.
 
 For Windows instructions [click here](#building-on-windows).
 
- - [**Prerequisites**](#prerequisites)
- - [**Quick Start**](#quick-start)
-    - [Run with SSL](#run-the-browser-example-with-ssl)
-    - [Run with Gitpod](#run-the-browser-example-with-gitpod)
- - [**Clone the repository**](#clone-the-repository)
- - [**The repository structure**](#the-repository-structure)
- - [**Build core, extensions and examples packages**](#build-core-extensions-and-examples-packages)
- - [**Build extension packages individually**](#build-extension-packages-individually)
- - [**Run the browser-based example application**](#run-the-browser-based-example-application)
- - [**Run the Electron-based example application**](#run-the-electron-based-example-application)
- - [**Rebuilding**](#rebuilding)
- - [**Watching**](#watching)
-     - [Watch the core and extension packages](#watch-the-core-and-extension-packages)
-     - [Watch the examples](#watch-the-examples)
-     - [Watch a specific package](#watch-a-specific-package)
-     - [Watch a specific package and its local upstream dependencies](#watch-a-specific-package-and-its-local-upstream-dependencies)
- - [**Debugging**](#debugging)
-     - [Debug the browser example's backend](#debug-the-browser-examples-backend)
-     - [Debug the browser example's frontend](#debug-the-browser-examples-frontend)
-     - [Debug the browser example's frontend and backend at the same time](#debug-the-browser-examples-frontend-and-backend-at-the-same-time)
-     - [Debug the Electron example's backend](#debug-the-electron-examples-backend)
-     - [Debug the Electron example's frontend](#debug-the-electron-examples-frontend)
-     - [Debug the Electron example's frontend and backend at the same time](#debug-the-electron-examples-frontend-and-backend-at-the-same-time)
-     - [Debug IPC servers](#debug-ipc-servers)
-     - [Debug the plugin host](#debug-the-plugin-host)
- - [**Profiling**](#profiling)
-     - [Profile the frontend process](#profile-the-frontend-process)
-     - [Profile the backend process](#profile-the-backend-process)
-     - [Profile IPC servers](#profile-ipc-servers)
-     - [Profile the plugin host](#profile-the-plugin-host)
- - [**Testing**](#testing)
- - [**Code coverage**](#code-coverage)
- - [**Building on Windows**](#building-on-windows)
- - [**Troubleshooting**](#troubleshooting)
-     - [Linux](#linux)
-     - [Windows](#windows)
-     - [macOS](#macos)
-     - [Root privileges errors](#root-privileges-errors)
+- [**Prerequisites**](#prerequisites)
+- [**Quick Start**](#quick-start)
+  - [Run with SSL](#run-the-browser-example-with-ssl)
+  - [Run with Gitpod](#run-the-browser-example-with-gitpod)
+- [**Clone the repository**](#clone-the-repository)
+- [**The repository structure**](#the-repository-structure)
+- [**Build core, extensions and examples packages**](#build-core-extensions-and-examples-packages)
+- [**Build extension packages individually**](#build-extension-packages-individually)
+- [**Run the browser-based example application**](#run-the-browser-based-example-application)
+- [**Run the Electron-based example application**](#run-the-electron-based-example-application)
+- [**Rebuilding**](#rebuilding)
+- [**Watching**](#watching)
+  - [Watch the core and extension packages](#watch-the-core-and-extension-packages)
+  - [Watch the examples](#watch-the-examples)
+  - [Watch a specific package](#watch-a-specific-package)
+  - [Watch a specific package and its local upstream dependencies](#watch-a-specific-package-and-its-local-upstream-dependencies)
+- [**Debugging**](#debugging)
+  - [Debug the browser example's backend](#debug-the-browser-examples-backend)
+  - [Debug the browser example's frontend](#debug-the-browser-examples-frontend)
+  - [Debug the browser example's frontend and backend at the same time](#debug-the-browser-examples-frontend-and-backend-at-the-same-time)
+  - [Debug the Electron example's backend](#debug-the-electron-examples-backend)
+  - [Debug the Electron example's frontend](#debug-the-electron-examples-frontend)
+  - [Debug the Electron example's frontend and backend at the same time](#debug-the-electron-examples-frontend-and-backend-at-the-same-time)
+  - [Debug IPC servers](#debug-ipc-servers)
+  - [Debug the plugin host](#debug-the-plugin-host)
+- [**Profiling**](#profiling)
+  - [Profile the frontend process](#profile-the-frontend-process)
+  - [Profile the backend process](#profile-the-backend-process)
+  - [Profile IPC servers](#profile-ipc-servers)
+  - [Profile the plugin host](#profile-the-plugin-host)
+- [**Testing**](#testing)
+- [**Code coverage**](#code-coverage)
+- [**Building on Windows**](#building-on-windows)
+- [**Troubleshooting**](#troubleshooting)
+  - [Linux](#linux)
+  - [Windows](#windows)
+  - [macOS](#macos)
+  - [Root privileges errors](#root-privileges-errors)
 
 ## Prerequisites
 
- - Node.js `>= 18.17.0` and `< 21`.
-   - If you are interested in Theia's VS Code Extension support then you should use a Node version at least compatible with the one included in the version of Electron used by [VS Code](https://github.com/microsoft/vscode).
- - [Yarn package manager](https://yarnpkg.com/en/docs/install)  `>= 1.7.0` **AND** `< 2.x.x`.
- - git (If you would like to use the Git-extension too, you will need to have git version 2.11.0 or higher.)
- - Python3 is required for the build due to [`node-gyp@8.4.1`](https://github.com/nodejs/node-gyp/tree/v8.4.1#installation)
+- Node.js `>= 18.17.0` and `< 21`.
+  - If you are interested in Theia's VS Code Extension support then you should use a Node version at least compatible with the one included in the version of Electron used by [VS Code](https://github.com/microsoft/vscode).
+- [Yarn package manager](https://yarnpkg.com/en/docs/install)  `>= 1.7.0` **AND** `< 2.x.x`.
+- git (If you would like to use the Git-extension too, you will need to have git version 2.11.0 or higher.)
+- Python3 is required for the build due to [`node-gyp@8.4.1`](https://github.com/nodejs/node-gyp/tree/v8.4.1#installation)
 
 Some additional tools and libraries are needed depending on your platform:
 
@@ -96,7 +97,7 @@ git clone https://github.com/eclipse-theia/theia \
     && yarn browser start
 ```
 
-Start your browser on http://localhost:3000.
+Start your browser on <http://localhost:3000>.
 
 To build and run the Electron example:
 
@@ -130,13 +131,14 @@ git clone https://github.com/eclipse-theia/theia \
     && yarn browser start --ssl --cert /path/to/cert.crt --certkey /path/to/certkey.key
 ```
 
-Start your browser on https://localhost:3000.
+Start your browser on <https://localhost:3000>.
 
 ### Run the browser example with Gitpod
 
 [Gitpod](https://www.gitpod.io/) is a Theia-based IDE for GitHub.
 You can start by prefixing any GitHub URL in the Theia repository with `gitpod.io/#`:
-- Open https://gitpod.io/#https://github.com/eclipse-theia/theia to start development with the master branch.
+
+- Open <https://gitpod.io/#https://github.com/eclipse-theia/theia> to start development with the master branch.
 - Gitpod will start a properly configured for Theia development workspace, clone and build the Theia repository.
 - After the build is finished, run from the terminal in Gitpod:
 
@@ -162,13 +164,13 @@ THEIA=$PWD/theia
 
 Theia repository has multiple folders:
 
- - `packages` folder contains runtime packages, as the core package and extensions to it
- - `dev-packages` folder contains devtime packages
-    - [@theia/cli](../dev-packages/cli/README.md) is a command line tool to manage Theia applications
-    - [@theia/ext-scripts](../dev-packages/private-ext-scripts/README.md) is a command line tool to share scripts between Theia runtime packages
- - `examples` folder contains example applications, both Electron-based and browser-based
- - `doc` folder provides documentation about how Theia works
- - `scripts` folder contains JavaScript scripts used by npm scripts when
+- `packages` folder contains runtime packages, as the core package and extensions to it
+- `dev-packages` folder contains devtime packages
+  - [@theia/cli](../dev-packages/cli/README.md) is a command line tool to manage Theia applications
+  - [@theia/ext-scripts](../dev-packages/private-ext-scripts/README.md) is a command line tool to share scripts between Theia runtime packages
+- `examples` folder contains example applications, both Electron-based and browser-based
+- `doc` folder provides documentation about how Theia works
+- `scripts` folder contains JavaScript scripts used by npm scripts when
 installing
 - the root folder lists dev dependencies and wires everything together with [Lerna](https://lerna.js.org/)
 
@@ -243,7 +245,7 @@ We can start the application from the [examples/browser](../examples/browser) di
 yarn start
 ```
 
-This command starts the backend application listening on port `3000`. The frontend application should be available on http://localhost:3000.
+This command starts the backend application listening on port `3000`. The frontend application should be available on <http://localhost:3000>.
 
 If you rebuild native Node.js packages for Electron then rollback these changes
 before starting the browser example by running from the root directory:
@@ -328,63 +330,65 @@ npx run watch @theia/navigator --include-filtered-dependencies --parallel
 
 ### Debug the browser example's backend
 
- - Open the debug view and run the `Launch Browser Backend` configuration.
+- Open the debug view and run the `Launch Browser Backend` configuration.
 
 ### Debug the browser example's frontend
 
- - Start the backend by using `yarn run start`.
- - In a browser: Open http://localhost:3000/ and use the dev tools for debugging.
- - Open the debug view and run the `Launch Browser Frontend` configuration.
+- Start the backend by using `yarn run start`.
+- In a browser: Open <http://localhost:3000/> and use the dev tools for debugging.
+- Open the debug view and run the `Launch Browser Frontend` configuration.
 
 ### Debug the browser example's frontend and backend at the same time
 
- - Open the debug view and run the `Launch Browser Backend` configuration.
- - Then run the `Launch Browser Frontend` configuration.
+- Open the debug view and run the `Launch Browser Backend` configuration.
+- Then run the `Launch Browser Frontend` configuration.
 
 ### Debug the Electron example's backend
 
- - Open the debug view and run the `Launch Electron Backend` configuration.
+- Open the debug view and run the `Launch Electron Backend` configuration.
 
 ### Debug the Electron example's frontend
 
- - Start the Electron backend
-   - Either open the debug view and run the `Launch Electron Backend` configuration
-   - Or use `yarn run start`.
- - Attach to the Electron Frontend
-   - Either open the debug view and run the `Attach to Electron Frontend` configuration
-   - Or in Electron: Help -> Toggle Electron Developer Tools.
+- Start the Electron backend
+  - Either open the debug view and run the `Launch Electron Backend` configuration
+  - Or use `yarn run start`.
+- Attach to the Electron Frontend
+  - Either open the debug view and run the `Attach to Electron Frontend` configuration
+  - Or in Electron: Help -> Toggle Electron Developer Tools.
 
 ### Debug the Electron example's frontend and backend at the same time
 
- - Open the debug view and run the `Launch Electron Backend & Frontend` configuration.
+- Open the debug view and run the `Launch Electron Backend & Frontend` configuration.
 
 ### Debug IPC servers
 
-  - Pass `--${server-name}-inspect` arg to the backend server.
-    - For example `--nsfw-watcher-inspect=0` to inspect nsfw watcher processes with dynamic port allocation.
-    - All variations of `--inspect` flag are supported: https://nodejs.org/en/docs/inspector/#command-line-options.
-  - Attach the debugger to the logged port.
+- Pass `--${server-name}-inspect` arg to the backend server.
+  - For example `--nsfw-watcher-inspect=0` to inspect nsfw watcher processes with dynamic port allocation.
+  - All variations of `--inspect` flag are supported: <https://nodejs.org/en/docs/inspector/#command-line-options>.
+- Attach the debugger to the logged port.
 
 In order to look up `server-name` run the backend server with `--log-level=debug` flag to enable logging of IPC servers instantiation.
 You should be able to see message of `[${server-name}: ${server-PID}]: IPC started` format, like `[nsfw-watcher: 37557] IPC started`.
 
 ### Debug the plugin host
 
-  - Pass `--hosted-plugin-inspect=9339` arg to the backend server from the command line.
-    - Instead, you can run `Launch Browser Backend` launch configuration which is already pre-configured.
-  - Open the debug view and run the `Attach to Plugin Host` launch configuration.
-    - It connects to the plugin host if at least one extension is detected, otherwise it timeouts after 60s.
-    - If you want to debug the activation then enable `stopOnEntry` flag.
-  - Open the browser page.
+- Pass `--hosted-plugin-inspect=9339` arg to the backend server from the command line.
+  - Instead, you can run `Launch Browser Backend` launch configuration which is already pre-configured.
+- Open the debug view and run the `Attach to Plugin Host` launch configuration.
+  - It connects to the plugin host if at least one extension is detected, otherwise it timeouts after 60s.
+  - If you want to debug the activation then enable `stopOnEntry` flag.
+- Open the browser page.
 
  ---
+
 ### Debugging Plugin Sources
 
 [click for base article](https://github.com/eclipse-theia/theia/issues/3251#issuecomment-468166533)
 
 The following launch configuration is meant to be used when the Theia project is opened as the main project in VS Code, the following launch configuration is added inside .vscode/launch.json.
+
 - The source repository of your plugin is expected under your `${workspaceFolder}/plugins` folder
-- You can start the frontend from URL: http://localhost:3030
+- You can start the frontend from URL: <http://localhost:3030>
 - It's suggested to update your frontend launch configuration URL to open your favorite target project in a second launch
 
 Launch configuration template that will start the backend process, and then attempt to connect on port 9339 to debug the plugin-host sub-process:
@@ -459,37 +463,37 @@ You can fix it by modifying your `tsconfig.json`:
 
 ## Profiling
 
- - Use Chrome devtools to profile both the frontend and backend (Node.js).
-   - For Node.js: open chrome://inspect, click the configure button and ensure target host and port are listed.
- - Learn how to get and understand CPU measurements: https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/
- - Learn how to get and understand Memory measurements: https://developers.google.com/web/tools/chrome-devtools/memory-problems/
- - Before taking the memory snapshot always collect garbage.
- - Make sure that Chrome extensions don't distort measurements by disabling them.
-   - For frontend: React extension is leaking components.
- - Make measurements before and after improvements to provide them as evidence on a pull request.
-   - Also document how to reproduce improved measurements in `How to test` section of a pull request description.
- - If objects don't have a proper class, i.e. plain JSON, then find one of them in the first snapshot
+- Use Chrome devtools to profile both the frontend and backend (Node.js).
+  - For Node.js: open chrome://inspect, click the configure button and ensure target host and port are listed.
+- Learn how to get and understand CPU measurements: <https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/>
+- Learn how to get and understand Memory measurements: <https://developers.google.com/web/tools/chrome-devtools/memory-problems/>
+- Before taking the memory snapshot always collect garbage.
+- Make sure that Chrome extensions don't distort measurements by disabling them.
+  - For frontend: React extension is leaking components.
+- Make measurements before and after improvements to provide them as evidence on a pull request.
+  - Also document how to reproduce improved measurements in `How to test` section of a pull request description.
+- If objects don't have a proper class, i.e. plain JSON, then find one of them in the first snapshot
  and check that it is garbage collected in the diff between snapshots.
 
 ### Profile the frontend process
 
-  - In Browser: open the devtools.
-  - In Electron: Help -> Toggle Electron Developer Tools.
+- In Browser: open the devtools.
+- In Electron: Help -> Toggle Electron Developer Tools.
 
 ### Profile the backend process
 
-  - Pass `--inspect` arg to the backend server: https://nodejs.org/en/docs/inspector/#command-line-options.
+- Pass `--inspect` arg to the backend server: <https://nodejs.org/en/docs/inspector/#command-line-options>.
 
 ### Profile IPC servers
 
-  - Pass `--${server-name}-inspect` arg to the backend server.
-    - For example `--nsfw-watcher-inspect=0` to inspect nsfw watcher processes with dynamic port allocation.
-    - All variations of `--inspect` flag are supported: https://nodejs.org/en/docs/inspector/#command-line-options.
+- Pass `--${server-name}-inspect` arg to the backend server.
+  - For example `--nsfw-watcher-inspect=0` to inspect nsfw watcher processes with dynamic port allocation.
+  - All variations of `--inspect` flag are supported: <https://nodejs.org/en/docs/inspector/#command-line-options>.
 
 ### Profile the plugin host
 
- - Pass `--hosted-plugin-inspect` arg to the backend server.
-   - All variations of `--inspect` flag are supported: https://nodejs.org/en/docs/inspector/#command-line-options.
+- Pass `--hosted-plugin-inspect` arg to the backend server.
+  - All variations of `--inspect` flag are supported: <https://nodejs.org/en/docs/inspector/#command-line-options>.
 
 ## Testing
 
@@ -506,15 +510,15 @@ etc.) by opening `packages/<package name>/coverage/index.html`.
 
 ## Building on Windows
 
- - Install [`scoop`](https://github.com/lukesampson/scoop#installation).
- - Install [`nvm`](https://github.com/coreybutler/nvm-windows) with scoop: `scoop install nvm`.
- - Install Node.js with `nvm`: `nvm install lts`, then use it: `nvm use lts`. You can list all available Node.js versions with `nvm list available` if you want to pick another version.
- - Install `yarn`: `scoop install yarn`.
- - If you need to install `windows-build-tools`, see [`Installing Windows Build Tools`](#installing-windows-build-tools).
- - If you run into problems with installing the required build tools, the `node-gyp` documentation offers a useful [guide](https://github.com/nodejs/node-gyp#on-windows) how to install the dependencies manually. The versions required for building Theia are:
-   - Python 3.6 to 3.11
-   - Visual Studio [build tools](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022) 17
- - If you have multiple versions of either python or Visual Studio installed, or if the tool is not found, you may adjust the version used as described 
+- Install [`scoop`](https://github.com/lukesampson/scoop#installation).
+- Install [`nvm`](https://github.com/coreybutler/nvm-windows) with scoop: `scoop install nvm`.
+- Install Node.js with `nvm`: `nvm install lts`, then use it: `nvm use lts`. You can list all available Node.js versions with `nvm list available` if you want to pick another version.
+- Install `yarn`: `scoop install yarn`.
+- If you need to install `windows-build-tools`, see [`Installing Windows Build Tools`](#installing-windows-build-tools).
+- If you run into problems with installing the required build tools, the `node-gyp` documentation offers a useful [guide](https://github.com/nodejs/node-gyp#on-windows) how to install the dependencies manually. The versions required for building Theia are:
+  - Python 3.6 to 3.11
+  - Visual Studio [build tools](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022) 17
+- If you have multiple versions of either python or Visual Studio installed, or if the tool is not found, you may adjust the version used as described
  [here](https://github.com/nodejs/node-gyp?tab=readme-ov-file#configuring-python-dependency)
 
 Clone, build and run Theia.
@@ -527,12 +531,13 @@ git clone https://github.com/eclipse-theia/theia.git \
     && yarn browser build \
     && yarn browser start
 ```
+
 If you do not have Git Bash installed on your system, [get one](https://gitforwindows.org/), or use `scoop`: `scoop install git`.
 
 ### Installing Windows Build Tools
 
- - Previously, [`windows-build-tools`](https://github.com/felixrieseberg/windows-build-tools) is required to build Native Nodes modules on Windows. The npm package is now [`deprecated`](https://www.npmjs.com/package/windows-build-tools) because NodeJS installer can now install all the required tools that it needs, including Windows Build Tools.
- - In case you need to install the tool manually, after installing `yarn`, run `PowerShell` as _Administrator_ and copy paste the following: `npm --add-python-to-path install --global --production windows-build-tools`.
+- Previously, [`windows-build-tools`](https://github.com/felixrieseberg/windows-build-tools) is required to build Native Nodes modules on Windows. The npm package is now [`deprecated`](https://www.npmjs.com/package/windows-build-tools) because NodeJS installer can now install all the required tools that it needs, including Windows Build Tools.
+- In case you need to install the tool manually, after installing `yarn`, run `PowerShell` as _Administrator_ and copy paste the following: `npm --add-python-to-path install --global --production windows-build-tools`.
 
 ## Troubleshooting
 
@@ -556,15 +561,15 @@ If you see `LINK : fatal error LNK1104: cannot open file 'C:\\Users\\path\\to\\n
 If you are facing with `EPERM: operation not permitted` or `permission denied`
 errors while building, testing or running the application then;
 
- - You don't have write access to the installation directory.
- - Try to run your command line (`PowerShell`, `GitBash`, `Cygwin` or whatever
+- You don't have write access to the installation directory.
+- Try to run your command line (`PowerShell`, `GitBash`, `Cygwin` or whatever
  you are using) as an administrator.
- - The permissions in the NPM cache might get corrupted. Please try to run
+- The permissions in the NPM cache might get corrupted. Please try to run
  `npm cache clean` to fix them.
- - If you experience issues such as `Error: EBUSY: resource busy or locked, rename`,
+- If you experience issues such as `Error: EBUSY: resource busy or locked, rename`,
  try to disable (or uninstall) your anti-malware software.
  See [here](https://github.com/npm/npm/issues/13461#issuecomment-282556281).
- - Still having issues on Windows? File a [bug]. We are working on Linux or OS X
+- Still having issues on Windows? File a [bug]. We are working on Linux or OS X
  operating systems. Hence, we are more than happy to receive any Windows-related
  feedbacks, [bug](https://github.com/eclipse-theia/theia/issues) reports.
 
@@ -583,10 +588,11 @@ If you already have Xcode installed, but you see the `xcode-select: error: tool
 The solution is the same if you have updated to `10.14` (Mojave) and you can see the `gyp: No Xcode or CLT version detected!` error. More details [here](https://github.com/nodejs/node-gyp#on-macos).
 
 ### Root privileges errors
+
 When trying to install with root privileges, you might encounter errors such as
 `cannot run in wd`.
 
 Several options are available to you:
 
- - Install without root privileges
- - Use the `--unsafe-perm` flag: `yarn --unsafe-perm`
+- Install without root privileges
+- Use the `--unsafe-perm` flag: `yarn --unsafe-perm`
diff --git a/doc/Migration.md b/doc/Migration.md
index 29e36e1ace3bb..b921f8d839611 100644
--- a/doc/Migration.md
+++ b/doc/Migration.md
@@ -67,6 +67,7 @@ With Inversify 6, the library has introduced a strict split between sync and asy
 Theia uses the sync dependency injection context, and therefore no async dependencies cannot be used as dependencies in Theia.
 
 This might require a few changes in your Theia extensions, if you've been using async dependencies before. These include:
+
 1. Injecting promises directly into services
 2. Classes with `@postConstruct` methods which return a `Promise` instance.
 
@@ -106,19 +107,22 @@ If you've been overriding some of these `init()` methods, it might make sense to
 
 #### Disabled node integration and added context isolation flag in Electron renderer
 
-This also means that `electron-remote` can no longer be used in components in `electron-frontend` or `electron-common`. In order to use electron-related functionality from the browser, you need to expose an API via a preload script (see https://www.electronjs.org/docs/latest/tutorial/context-isolation). To achieve this from a Theia extension, you need to follow these steps:
+This also means that `electron-remote` can no longer be used in components in `electron-frontend` or `electron-common`. In order to use electron-related functionality from the browser, you need to expose an API via a preload script (see <https://www.electronjs.org/docs/latest/tutorial/context-isolation>). To achieve this from a Theia extension, you need to follow these steps:
 
 1. Define the API interface and declare an API variable on the global `window` variable. See `packages/filesystem/electron-common/electron-api.ts` for an example
 2. Write a preload script module that implements the API on the renderer ("browser") side and exposes the API via `exposeInMainWorld`. You'll need to expose the API in an exported function called `preload()`. See `packages/filesystem/electron-browser/preload.ts` for an example.
 3. Declare a `theiaExtensions` entry pointing to the preload script like so:
+
 ```
 "theiaExtensions": [
     {
       "preload": "lib/electron-browser/preload",
 ```
+
 See `/packages/filesystem/package.json` for an example
 
 4. Implement the API on the electron-main side by contributing a `ElectronMainApplicationContribution`. See `packages/filesystem/electron-main/electron-api-main.ts` for an example. If you don't have a module contributing to the electron-main application, you may have to declare it in your package.json.
+
 ```
 "theiaExtensions": [
   {
diff --git a/doc/Publishing.md b/doc/Publishing.md
index 3a8d193012f8a..0463fadc8c723 100644
--- a/doc/Publishing.md
+++ b/doc/Publishing.md
@@ -1,152 +1,261 @@
-# Publishing
+# Publishing Guide for Eclipse Theia Releases
 
-The documentation describes the various steps and information regarding the release of Eclipse Theia for maintainers.
+This guide details the steps for maintainers to release Eclipse Theia, including pre-release preparations, the release process, post-release steps, and troubleshooting.
 
-## Release Procedure
+## Table of Contents
 
-- [**Pre-Release Steps**](#pre-release-steps)
-  - [Yarn Upgrade](#yarn-upgrade)
-  - [Announce Release](#announce-release)
-  - [Localization](#localization)
-  - [Changelog](#changelog)
-  - [Update Milestone](#update-milestone)
-- [**Release**](#publishing)
-  - [Community Releases](#community-releases)
-- [**Post-Release Steps**](#post-release-steps)
-  - [Eclipse Release](#eclipse-release)
-  - [Announce Release is Completed](#announce-release-is-completed)
-  - [Update Future Milestones](#update-future-milestones)
-  - [Publish GitHub Pages](#publish-github-pages)
-- [**Troubleshooting**](#troubleshooting)
-  - [**Failures During Publishing**](#failures-during-publishing)
+1. [Pre-Release Steps](#1-pre-release-steps)
+   - [1.1 Yarn Upgrade](#11-yarn-upgrade)
+   - [1.2 Announce Release](#12-announce-release)
+   - [1.3 Localization](#13-localization)
+   - [1.4 Prepare Release Branch](#14-prepare-release-branch)
+   - [1.5 Update Changelog](#15-update-changelog)
+2. [Release Process](#2-release-process)
+   - [2.1 Performing a Release](#21-performing-a-release)
+   - [2.2 Community Releases](#22-community-releases)
+3. [Post-Release Steps](#3-post-release-steps)
+   - [3.1 Eclipse Release](#31-eclipse-release)
+   - [3.2 Announce Release Completion](#32-announce-release-completion)
+   - [3.3 Update Future Milestones](#33-update-future-milestones)
+   - [3.4 Merge Website PRs](#34-merge-website-prs)
+   - [3.5 Publish GitHub Pages](#35-publish-github-pages)
+4. [Troubleshooting](#4-troubleshooting)
+   - [Failures During Publishing](#41-failures-during-publishing)
 
-## Pre-Release Steps
+## 1. Pre-Release Steps
 
-### Yarn Upgrade
+### 1.1 Yarn Upgrade
 
-In general, it is recommended to perform a `yarn upgrade` on the repository prior to a release to update the `yarn.lock`.
-The upgrade helps to:
+Perform a `yarn upgrade` on the repository prior to a release to update the `yarn.lock`. The upgrade helps to:
 
-- Better represents what adopters will pull during a release.
+- Better represent what adopters will pull during a release.
 - Validate dependencies with our declared version ranges.
 - Fix known security vulnerabilities from dependencies.
 
-In order to successfully perform a `yarn upgrade` one must:
+To perform the upgrade:
 
-- Perform a `yarn upgrade` at the root of the repository.
-- Fix any potential compilation errors, typing errors, and failing tests that may have been introduced.
+- Run `yarn upgrade` at the root of the repository.
+- Fix any compilation errors, typing errors, and failing tests.
+- Open a PR with the changes ([example](https://github.com/eclipse-theia/theia/pull/13423)).
 - Confirm licenses and wait for the "IP Check" to complete ([example](https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/9377)).
 
-### Announce Release
+### 1.2 Announce Release
 
-It is a good idea to give a heads-up to developers and the community some hours before a release.
-At the time of writing this is [GitHub Discussions](https://github.com/eclipse-theia/theia/discussions). Here is an [example](https://github.com/eclipse-theia/theia/discussions/13314).
+- Provide a heads-up to developers and the community a few hours before the release.
+- Use [GitHub Discussions](https://github.com/eclipse-theia/theia/discussions) for the announcement.
 
-### Localization
+  > Title: Eclipse Theia v{version}
+  >
+  > Hey everyone 👋,
+  >
+  > The Eclipse Theia v{version} release is happening today, starting around {time} CET.
+  > If you have any nearly-complete PRs that need to be included, let us know in this thread before we begin.
+  >
+  > We’ll post updates when the release starts and once it’s done.
+  > Please avoid merging any PRs during the release until we confirm it's over.
 
-The localization (`nls`) updates should be performed before a release ([example](https://github.com/eclipse-theia/theia/pull/12665)).
-To help we have an [automatic translation](https://github.com/eclipse-theia/theia/actions/workflows/translation.yml) workflow which can be triggered.
-Note that due to the required CI check (`lint`) we will need for force-push the branch that the bot creates to properly trigger CI.
+- Refer to [this example](https://github.com/eclipse-theia/theia/discussions/14547) for guidance.
+- Also send a mail to `theia-dev@eclipse.org` (don't forget to add the link to the discussion):
 
-### Changelog
+  > Hi,
+  >
+  > The Eclipse Theia v{version} release is scheduled for later today! You can follow the progress here: {add link here}
 
-The [changelog](https://github.com/eclipse-theia/theia/blob/master/CHANGELOG.md) should be updated and merged for the release.
-The updates should document the release as thoroughly as possible:
+### 1.3 Localization
 
-- Notable new features, improvements and bug fixes.
-- Potential breaking changes.
+- Perform `nls` updates before a release ([example](https://github.com/eclipse-theia/theia/pull/14373)).
+- Trigger the automatic translation workflow via GitHub Actions ([workflow link](https://github.com/eclipse-theia/theia/actions/workflows/translation.yml)).
+- Force-push the branch created by the bot to properly trigger CI.
+- Once the PR is approved, use `Squash and merge` to finalize it.
 
-The `changelog` should follow the same format as previous releases:
+### 1.4 Prepare Release Branch
 
-- Include the version, and date.
-- Add a link to the appropriate milestone.
-- Document all breaking changes in a separate section.
-- Entries should be formatted in the following way:
-  - Prefix by their most appropriate extension name (ex: `[core]`).
-  - Add a link to their corresponding pull-request.
-  - Should be in alphabetical order.
-  - Should be in the past tense (ex: 'Added support...').
+- Checkout `master` with the latest changes:
 
-### Update Milestone
+  ```bash
+  git pull
+  ```
 
-The given release [milestone](https://github.com/eclipse-theia/theia/milestones) should be updated to include all commits that composed the release.
-Generally, milestones are automatically added on merge but not necessarily for forks. It is therefore important to manually add such contributions to the milestone for the time being.
+- Confirm the latest changes are present:
 
-## Release
+  ```bash
+  git log
+  ```
 
-The release instructions are as follows:
+- Create a branch with the pattern `release/x.y.z` (e.g., `release/1.55.x`).
+
+### 1.5 Update Changelog
+
+Add entries for non-breaking changes since the last release. Breaking changes should be added by the PR, not during the release.
+
+Commit the changelog changes with the message: `docs: update changelog for {version}`.
+
+Format:
+
+- Version and date as an H2 header (e.g., `## 1.55.0 - 10/31/2024`).
+- Entries should:
+  - Be prefixed with their extension name (e.g., `[core]`).
+  - Start with a lowercase character and be in the past tense (e.g., 'added support...').
+  - Be in alphabetical order.
+  - Include a link to their corresponding pull request.
+  - Specify contribution if applicable (e.g., Contributed on behalf of x).
+  - Example: `[core] added support for Node 20.x [#1234](https://github.com/eclipse-theia/theia/pull/1234) - Contributed on behalf of x`.
+- Breaking changes should be in a separate section (header: `<a name="breaking_changes_1.55.0">[Breaking Changes:](#breaking_changes_1.55.0)</a>`).
+
+## 2. Release Process
+
+### 2.1 Performing a Release
+
+- Announce that the release is starting in the discussion (not needed for patch releases):
+
+  > The release will start now. We’ll post an update once it has completed.
+
+- Ensure the release branch is checked out (e.g., `release/1.55.x`).
+
+- Clean the working directory:
+
+  ```bash
+  git clean -xdf
+  ```
+
+- Build the changes:
+
+  ```bash
+  yarn
+  ```
+
+- Confirm the changes are built (ensure `@theia` extensions have their `lib/` folders).
+
+- Create a short-lived granular npm auth token ([instructions](https://docs.npmjs.com/creating-and-viewing-access-tokens#creating-granular-access-tokens-on-the-website)):
+  - Expiration: `7 days`.
+  - Under Packages and scopes:
+    - Permissions: `Read and write`.
+    - Select `Only select packages and scopes`
+    - Select packages and scopes: `@theia`.
+
+- Set the token:
+
+  ```bash
+   npm set "//registry.npmjs.org/:_authToken=${TOKEN}"
+  ```
+
+  _Note:_ Add a whitespace in front of this command to ensure it is not added to the shell's history (might not work for all shells).
+
+- Perform the release:
+
+  ```bash
+  yarn publish:latest
+  ```
+
+  Select the appropriate version.
+
+  _NOTE:_ For a patch release on an earlier version (e.g., 1.55.1 when 1.56.0 exists), use:
+
+  ```bash
+  yarn publish:patch
+  ```
+
+- Verify the packages are published on npm.
+
+- Remove the auth token:
+
+  ```bash
+  npm logout
+  ```
+
+- Update `packages/core/README.md` in a commit named `core: update re-exports for {version}` ([example](https://github.com/eclipse-theia/theia/commit/21fa2ec688e4a8bcf10203d6dc0f730af43a7f58)).
+
+- Add other changes in a commit named `v{version}`.
+
+- Push the branch.
+
+- Run the [_Package Native Dependencies_](https://github.com/eclipse-theia/theia/actions/workflows/native-dependencies.yml) GitHub Action on the new branch and download the artifacts.
+
+- Create a PR (not needed for patch releases):
+  - Name: `Theia {version}`.
+  - Wait for approval.
+  - Merge using `Rebase and Merge` (**DO NOT `Squash and Merge`**).
+
+- Tag the publishing commit after merging (for patch releases, tag directly on the release branch):
+
+  ```bash
+  git tag -a v{version} ${sha} -m "v{version}"
+  ```
+
+- Push the tag:
+
+  ```bash
+  git push origin v{version}
+  ```
 
-- Checkout `master` with the latest changes (`git pull` to pull the latest changes).
-- Confirm the latest changes are present (`git log`).
-- Build the changes (`yarn`).
-- Confirm the changes are built (individual `@theia` extensions should have their `lib/` folders present).
-- Perform the release using `yarn publish:latest` - choose an appropriate version.
-- Keep the `packages/core/README.md` updates in a separate commit ([example](https://github.com/eclipse-theia/theia/commit/21fa2ec688e4a8bcf10203d6dc0f730af43a7f58)).
-- Prepare a release - create a branch with the pattern `release/x.y.z` (ex: `release/1.40.x`).
-- Run the [*Package Native Dependencies*](https://github.com/eclipse-theia/theia/actions/workflows/native-dependencies.yml) GitHub Action on the new branch and download the resulting artifacts.
-- Once approved, merge using `Rebase and Merge` (**DO NOT `Squash and Merge`**).
-- Once the pull-request is merged, pull the changes locally and tag the publishing commit (ex: `git tag -a "${version} ${sha} -m "${version}"`).
-- Publish the tag to GitHub.
 - Create a GitHub release:
-  - Navigate to the releases [page](https://github.com/eclipse-theia/theia/releases).
-  - Select the _"Draft a new release"_ button.
-  - Input the appropriate release `tag` version (ex: `v1.2.0`).
-  - Input the appropriate release `name` (ex: `Eclipse Theia v1.2.0`).
-  - Use the `generate release notes` button to generate the list of contributors (including new ones), and format them similarly to other releases.
-  - Include a release `description` to include a reference to the `changelog` at the respective `sha` and release version.
-  - Include a reference to the migration guide in the release description.
-  - Add the artifacts of the *Package Native Dependencies* GitHub Action to the release assets.
-  - Select _"Publish Release"_ bottom at the bottom of the page.
-  - For additional information, please consult the official GitHub documentation regarding [creating releases](https://help.github.com/en/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release).
+  - Draft a release on the [releases page](https://github.com/eclipse-theia/theia/releases).
+  - Choose the appropriate `tag` and input a `name` (e.g., `v1.55.0`, `Eclipse Theia v1.55.0`).
+  - Use `generate release notes` for contributors and format like previous releases.
+  - Reference the `changelog` and breaking changes.
+  - Attach _Package Native Dependencies_ artifacts.
+  - Mark the release as `latest` (_Do not mark for a patch on an older version_).
+  - Select _"Publish Release"_.
+  - See [GitHub documentation](https://help.github.com/en/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release) for details.
+
+### 2.2 Community Releases
+
+Community releases are similar to regular releases but with fewer steps (e.g., no need to submit a pull request).
+
+- Prepare the community release branch from a specific release `tag`.
+- Cherry-pick any changes to apply on top of the `tag` (e.g., patches).
+- Perform the release as usual using a `dist-tag` of `community`.
+
+## 3. Post-Release Steps
+
+### 3.1 Eclipse Release
+
+- Login to [Eclipse Foundation Theia project page](https://projects.eclipse.org/projects/ecd.theia).
+- Select `Release` / `Create a new release` from the menu.
+  - `Release Date`: Enter the date.
+  - `Name`: Enter the version (e.g., `1.55.0`).
+- Go to Edit -> Project Plan
+  - Add the changelog link to `deliverables` (Link with text `Release Notes`).
+  - Add breaking changes link to `compatibility` (Link with text `Breaking Changes`).
+- Save changes and confirm by reviewing the project page.
+
+### 3.2 Announce Release Completion
+
+- Update the forum post to announce that the release is completed.
 
-### Community Releases
+  > The release has completed, thank you to everyone that participated and contributed!
 
-For the most part community releases are similar to regular releases but with fewer steps (ex: no need to submit a pull-request).
-In order to perform a community releases we want to:
+- Mark the message as the answer
 
-- Prepare the community release branch which branches off from a specific release `tag`.
-- Cherry-pick any changes we want to apply on top of the `tag` (ex: patches that fix regressions, security vulnerabilities).
-- Perform the release as usual (we want to use a `dist-tag` of `community`).
+- Submit to "Theia News" for a Twitter announcement. Use [this template](https://github.com/eclipse-theia/theia/wiki/Eclipse-Theia-Twitter-strategy#release-announcement-no-review) and submit it [here](https://forms.gle/ccS6qawpS54FQZht5).
 
-## Post-Release Steps
+### 3.3 Update Future Milestones
 
-### Eclipse Release
+- Close the current release [milestone](https://github.com/eclipse-theia/theia/milestones).
+- Create the next two milestones if they do not already exist. Releases are typically on the last Thursday of the month, with possible exceptions.
 
-- Login to [Eclipse Foundation Theia project page]( https://projects.eclipse.org/projects/ecd.theia)
-- On the right side menu, select `Release` / `Create a new release`
-  - `Release Date`: enter the date for the release.
-  - `Name`: enter the version of the release (ex: `1.40.0`).
-- Select `Create and edit`.
-- In the `projects` section:
-  - Add the changelog link to `deliverables`.
-  - Add the breaking changes link to `compatibility`.
-- Save the changes.
-- To confirm the release is successful:
-  - Open the [project page](https://projects.eclipse.org/projects/ecd.theia)
-    - Select the version you just created.
-    - Open the Review plan section, you should see the data provided before.
+### 3.4 Merge Website PRs
 
-### Announce Release is Completed
+- Merge all [website PRs marked with label `merge with next release`](https://github.com/eclipse-theia/theia-website/labels/merge%20with%20next%20release)
 
-- Update the forum release post to announce that the release has completed.
-- Submit to "Theia News", so that a Tweet will be created by the Twitter managers. Use [this template](https://github.com/eclipse-theia/theia/wiki/Eclipse-Theia-Twitter-strategy#release-announcement-no-review) for the message and post it [here](https://forms.gle/ccS6qawpS54FQZht5).
+### 3.5 Publish GitHub Pages
 
-### Update Future Milestones
+- Publish the `latest` documentation with the [GitHub Pages workflow](https://github.com/eclipse-theia/theia/actions/workflows/publish-gh-pages.yml) manually using the `manual_dispatch` job.
 
-- Close current release [milestone](https://github.com/eclipse-theia/theia/milestones).
-- Create the next two milestones in the case they do not already exist. Generally, the release is performed on the last Thursday of the month, but there may be exceptions (bug fix release, holidays, etc.).
+## 4. Troubleshooting
 
-### Publish GitHub Pages
+### 4.1 Failures During Publishing
 
-Following a release we should publish the `latest` documentation with our [GitHub Pages](https://github.com/eclipse-theia/theia/actions/workflows/publish-gh-pages.yml) workflow. The publishing should be performed manually using the `manual_dispatch` job.
+If `lerna` fails during publishing (e.g., socket errors), use the following commands to reset and retry:
 
-## Troubleshooting
+- Reset the repository:
 
-### Failures During Publishing
+  ```bash
+  git reset --hard
+  ```
 
-Sometimes `lerna` will fail during publishing (ex: socket errors). If such a case happens we should `git reset --hard` and retry publishing of only unpublished
-packages using a workaround command:
+- Retry publishing only the unpublished packages:
 
-```bash
-npx lerna publish from-package --no-git-reset --no-git-tag-version --no-push
-```
+  ```bash
+  npx lerna publish from-package --no-git-reset --no-git-tag-version --no-push
+  ```
diff --git a/doc/Testing.md b/doc/Testing.md
index 571ccd0502386..fce45144300fa 100644
--- a/doc/Testing.md
+++ b/doc/Testing.md
@@ -14,7 +14,6 @@ If you want to run all tests for a particular Theia extension, execute the follo
 
 `npx run test @theia/extension-name`
 
-
 Add the following npm script to the `package.json` of the desired Theia extension, if you would like to enable the watch mode for the tests.
 
 ```json
@@ -29,17 +28,17 @@ After editing the `package.json` you can run the tests in watch mode with:
 
 The test directory structure is as follows:
 
- - `src/node/foo.ts`: Code to be tested.
- - `src/node/foo.spec.ts`: Unit tests for foo.ts.
- - `src/node/test/test-helper.ts`: Any mocks, fixture or utility test code
+- `src/node/foo.ts`: Code to be tested.
+- `src/node/foo.spec.ts`: Unit tests for foo.ts.
+- `src/node/test/test-helper.ts`: Any mocks, fixture or utility test code
  goes here.
- - `src/node/foo.slow-spec.ts`: Any slow running tests such as integration
+- `src/node/foo.slow-spec.ts`: Any slow running tests such as integration
  tests should be labeled as such so that they can be excluded.
- - `src/browser/foo.ui-spec.ts`: UI tests.
- - `test-resources`: Any resources needed for the tests like configuration
+- `src/browser/foo.ui-spec.ts`: UI tests.
+- `test-resources`: Any resources needed for the tests like configuration
  files or scripts.
- - `test-resources/ui`: Resources for UI testing.
- - `test-resources/slow`: Resources for slow running tests.
+- `test-resources/ui`: Resources for UI testing.
+- `test-resources/slow`: Resources for slow running tests.
 
 ## Publishing
 
@@ -50,6 +49,6 @@ documentation purposes.
 
 ### Unpublished
 
- - `*ui-spec.ts`
- - `*slow-spec.ts`
- - `test-resources`
+- `*ui-spec.ts`
+- `*slow-spec.ts`
+- `test-resources`
diff --git a/doc/api-management.md b/doc/api-management.md
index 7b75536d82437..ca38d6730b15a 100644
--- a/doc/api-management.md
+++ b/doc/api-management.md
@@ -2,7 +2,6 @@
 
 > The guidance below is for the code of the Theia framework only. End products will get better development experience by using private visibility.
 
-
 - [**Stability**](#stability)
   - [**Experimental**](#experimental)
   - [**Stable**](#stable)
@@ -10,6 +9,7 @@
 - [**Deprecation**](#deprecation)
 
 Theia is a framework embracing openness, extensibility, and customizability as much as possible:
+
 - API defaults to public visibility for clients.
 - API defaults to protected for extenders.
 - Language constructions prohibiting runtime access to internals are never used.
@@ -17,7 +17,6 @@ Theia is a framework embracing openness, extensibility, and customizability as m
 Usually, the version management is built around API visibility.
 Particularly, when a public API is broken a new major release is required.
 
-
 Since all APIs are more or less public, following the conventional approach is not practicable for Theia.
 It will slow down API innovation, accumulate technical debt or require many major releases.
 
@@ -140,9 +139,9 @@ export interface DeprecatedStableInterface {
 }
 ```
 
-Deprecated [stable API](#stable) can be removed in one of the next *major* releases
+Deprecated [stable API](#stable) can be removed in one of the next _major_ releases
 
-Deprecated [experimental API](#experimental) can be removed in one of the next *minor* releases
+Deprecated [experimental API](#experimental) can be removed in one of the next _minor_ releases
 
 Breaking changes should be documented in [CHANGELOG](../CHANGELOG.md). Each breaking change should be justified to adopters
 and guide what should be done instead.
diff --git a/doc/api-testing.md b/doc/api-testing.md
index bd6c1be289bc7..1aacc3ed99d19 100644
--- a/doc/api-testing.md
+++ b/doc/api-testing.md
@@ -17,12 +17,14 @@ miss actual issues.
 
 Theia comes with own integration testing framework which is designed
 to overcome the shortcomings of the conventional approach:
+
 - tests are written against the application APIs
 ensuring that completeness and timing of APIs are tested;
 - tests are executed within the application process
 ensuring their speed and robustness.
 
 ## Testing principles
+
 - **Information Hiding**: API should provide the application object model
 hiding DOM/CSS implementation details behind.
 Test against the application API, not implementation details, like DOM/CSS.
@@ -98,6 +100,7 @@ describe('Editors', function () {
 ### Writing a test
 
 An example of the complete test suite can be found below. You can see how it follows design principles:
+
 - **Information Hiding**: the object model (EditorManager) is provided to access editors, no DOM/CSS are used.
 - **Completeness**: API provides a way to access existing editors and open new editors,
 there are also events notifying when a new editor get created or closed. More tests can be added to test it.
diff --git a/doc/changelogs/CHANGELOG-2019.md b/doc/changelogs/CHANGELOG-2019.md
index 8666c68d7f449..63aedf37589fe 100644
--- a/doc/changelogs/CHANGELOG-2019.md
+++ b/doc/changelogs/CHANGELOG-2019.md
@@ -109,10 +109,11 @@ Breaking changes:
 - [workspace] added path when creating a new folder [#6545](https://github.com/eclipse-theia/theia/pull/6545)
 
 Breaking changes:
+
 - [core] renamed preference `list.openMode` to `workbench.list.openMode` [#6481](https://github.com/eclipse-theia/theia/pull/6481)
 - [monaco] removed monaco prefix from commands [#5590](https://github.com/eclipse-theia/theia/pull/5590)
 - [plugin] re-implemented webviews to align with [VS Code browser implementation](https://blog.mattbierner.com/vscode-webview-web-learnings/) [#6465](https://github.com/eclipse-theia/theia/pull/6465)
-  - Security: `vscode.previewHTML` is removed, see https://code.visualstudio.com/updates/v1_33#_removing-the-vscodepreviewhtml-command
+  - Security: `vscode.previewHTML` is removed, see <https://code.visualstudio.com/updates/v1_33#_removing-the-vscodepreviewhtml-command>
   - Security: Before all webviews were deployed on [the same origin](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy)
   allowing them to break out and manipulate shared data as cookies, local storage or even start service workers
   for the main window as well as for each other. Now each webview will be deployed on own origin by default.
@@ -165,11 +166,11 @@ Breaking changes:
 - [monaco] fixed incorrect preference initialization [#6450](https://github.com/eclipse-theia/theia/pull/6450)
 - [monaco] rebinded keybinding for 'Go to Definition' [#6411](https://github.com/eclipse-theia/theia/pull/6411)
 - [plugin] improved tree views: [#6342](https://github.com/eclipse-theia/theia/pull/6342)
-    - added logic to not execute commands on selection change
-    - added better handling of `undefined` 'treeItem.label'
-    - added better styling support for item actions
-    - added better support for descriptions
-    - fixed styling issues
+  - added logic to not execute commands on selection change
+  - added better handling of `undefined` 'treeItem.label'
+  - added better styling support for item actions
+  - added better support for descriptions
+  - fixed styling issues
 - [plugin-ext] added `OutputChannelRegistry` interface and add it into the rpc [#6413](https://github.com/eclipse-theia/theia/pull/6413)
 - [plugin-ext] added configuration attribute to `DebugSession` [#6382](https://github.com/eclipse-theia/theia/pull/6382)
 - [plugin-ext] added logic to pass `pluginInfo` through the output channel append method [#6312](https://github.com/eclipse-theia/theia/pull/6312)
@@ -461,7 +462,6 @@ Breaking changes:
 - [plugin] fixed typo in 'HostedInstanceState' enum from RUNNNING to RUNNING in `plugin-dev` extension [#5608](https://github.com/theia-ide/theia/pull/5608)
 - [plugin] removed member `processOptions` from `AbstractHostedInstanceManager` as it is not initialized or used [#5608](https://github.com/theia-ide/theia/pull/5608)
 
-
 ## v0.8.0 - 27/06/2019
 
 - [core] added bépo keyboard layout
@@ -508,7 +508,7 @@ Breaking changes:
   - `URI.withoutScheme` is removed, in order to get a path use `URI.path`
 - [core] `SelectionCommandHandler.getMulitSelection()` is renamed into `SelectionCommandHandler.getMultiSelection()`
 - [debug] align commands with VS Code [#5102](https://github.com/theia-ide/theia/issues/5102)
-    - `debug.restart` renamed to `workbench.action.debug.restart`
+  - `debug.restart` renamed to `workbench.action.debug.restart`
 - [plugin] 'Hosted mode' extracted in `plugin-dev` extension
 - [preferences] removed constructor from the `FolderPreferenceProvider` class
 - [preferences] renamed overridenPreferenceName to overriddenPreferenceName
@@ -640,6 +640,7 @@ Breaking changes:
 - [dialog] updated `validate` and `accept` methods so they are now Promisified [#4764](https://github.com/theia-ide/theia/pull/4764)
 - [editor] turned off autoSave by default to align with VSCode [#4777](https://github.com/theia-ide/theia/pull/4777)
   - default settings can be overridden in application package.json:
+
   ```json
   {
     "private": true,
@@ -655,6 +656,7 @@ Breaking changes:
     }
   }
   ```
+
 - [electron] removed cluster mode and startup timeout setting
 - [electron] updated Electron to make runtime dependencies optional [#4873](https://github.com/theia-ide/theia/pull/4873)
 - [extension-manager] deprecated [#4876](https://github.com/theia-ide/theia/pull/4876)
@@ -671,7 +673,7 @@ Breaking changes:
 - [core] improved scrollbar styling
 - [core] updated tabbar toolbar to use VSCode icons
 - [core] updated the UI with numerous improvements including sidepanel icons, better alignment, tabbar and menu size
-- [cpp] added new `cpp.clangTidy `and `cpp.clangTidyChecks` preferences to lint cpp program when clangd v9+ is used
+- [cpp] added new `cpp.clangTidy`and `cpp.clangTidyChecks` preferences to lint cpp program when clangd v9+ is used
 - [cpp] fixed properly restarting clangd language server when changing cpp build configurations
 - [debug] added new debug preferences to control `view`, `console`, and `location` appearance
 - [editorconfig] added support to apply properties to monaco editor when opening/switching editors
@@ -686,8 +688,8 @@ Breaking changes:
 - [mini-browser] improved error handling of iframe errors
 - [navigator] added `Collapse All` toolbar item
 - [navigator] updated the navigator to handle multi-root workspaces better
-- [plugin-ext] added `workspace.onDidRenameFile ` Plug-in API
-- [plugin-ext] added `workspace.onWillRenameFile ` Plug-in API
+- [plugin-ext] added `workspace.onDidRenameFile` Plug-in API
+- [plugin-ext] added `workspace.onWillRenameFile` Plug-in API
 - [plugin-ext] added `workspace.registerFileSystemProvider` Plug-in API
 - [plugin-ext] added `workspace.saveAll` Plug-in API
 - [plugin-ext] added `workspace.updateWorkspaceFolders` Plug-in API
@@ -811,16 +813,16 @@ Breaking changes:
   - editor context menu group changes:
     - `2_cut_copy_paste` renamed to `9_cutcopypaste` group
 - [debug] align commands with VS Code [#4204](https://github.com/theia-ide/theia/issues/4204)
-    - `debug.breakpoint.toggle` renamed to `editor.debug.action.toggleBreakpoint`
-    - `debug.start` renamed to `workbench.action.debug.start`
-    - `debug.thread.continue` renamed to `workbench.action.debug.continue`
-    - `debug.start.noDebug` renamed to `workbench.action.debug.run`
-    - `debug.thread.pause` renamed to `workbench.action.debug.pause`
-    - `debug.thread.stepin` renamed to `workbench.action.debug.stepInto`
-    - `debug.thread.stepout` renamed to `workbench.action.debug.stepOut`
-    - `debug.thread.next` renamed to `workbench.action.debug.stepOver`
-    - `debug.stop` renamed to `workbench.action.debug.stop`
-    - `debug.editor.showHover` renamed to `editor.debug.action.showDebugHover`
+  - `debug.breakpoint.toggle` renamed to `editor.debug.action.toggleBreakpoint`
+  - `debug.start` renamed to `workbench.action.debug.start`
+  - `debug.thread.continue` renamed to `workbench.action.debug.continue`
+  - `debug.start.noDebug` renamed to `workbench.action.debug.run`
+  - `debug.thread.pause` renamed to `workbench.action.debug.pause`
+  - `debug.thread.stepin` renamed to `workbench.action.debug.stepInto`
+  - `debug.thread.stepout` renamed to `workbench.action.debug.stepOut`
+  - `debug.thread.next` renamed to `workbench.action.debug.stepOver`
+  - `debug.stop` renamed to `workbench.action.debug.stop`
+  - `debug.editor.showHover` renamed to `editor.debug.action.showDebugHover`
 - multi-root workspace support for preferences [#3247](https://github.com/theia-ide/theia/pull/3247)
   - `PreferenceProvider`
     - is changed from a regular class to an abstract class
diff --git a/doc/changelogs/CHANGELOG-2020.md b/doc/changelogs/CHANGELOG-2020.md
index cd577a3d7f2c1..6364da2710517 100644
--- a/doc/changelogs/CHANGELOG-2020.md
+++ b/doc/changelogs/CHANGELOG-2020.md
@@ -83,7 +83,6 @@
 - [electron] removed `attachWillPreventUnload` method from the Electron main application. The `confirmExit` logic is handled on the frontend [#8732](https://github.com/eclipse-theia/theia/pull/8732)
 - [file-search] deprecated dependency on `@theia/process` and replaced its usage by node's `child_process` API [#8721](https://github.com/eclipse-theia/theia/pull/8721)
 
-
 ## v1.7.0 - 29/10/2020
 
 <a name="release_milestone_1.7.0">[1.7.0 Release Milestone](https://github.com/eclipse-theia/theia/milestone/12?closed=1)</a>
@@ -109,7 +108,7 @@
 - [filesystem] refactored file watchers: [#8546](https://github.com/eclipse-theia/theia/pull/8546)
   - Added `FileSystemWatcherService` component that should be a singleton centralizing watch requests for all clients.
   - Added `FileSystemWatcherServiceDispatcher` to register yourself and listen to file change events.
-- [git] updated `commit details` and `diff view` rendering to respect `list` and `tree` modes [#8084] (https://github.com/eclipse-theia/theia/pull/8084)
+- [git] updated `commit details` and `diff view` rendering to respect `list` and `tree` modes [#8084] (<https://github.com/eclipse-theia/theia/pull/8084>)
 - [markers] updated and enhanced the 'problem-manager' tests [#8604](https://github.com/eclipse-theia/theia/pull/8604)
 - [mini-browser] updated deprecated `scrElement` usage to `target` [#8663](https://github.com/eclipse-theia/theia/pull/8663)
 - [monaco] fixed race condition on monaco editor initialization [#8563](https://github.com/eclipse-theia/theia/pull/8563)
@@ -150,7 +149,6 @@
 - [plugin-metrics] renamed `AnalyticsFromRequests.succesfulResponses` to `AnalyticsFromRequests.successfulResponses` [#8560](https://github.com/eclipse-theia/theia/pull/8560)
 - [plugin] `CodeEditorWidgetUti.getResourceUri` is no longer exportable [#8672](https://github.com/eclipse-theia/theia/pull/8672)
 
-
 ## v1.6.0 - 24/09/2020
 
 - [core] added ability to un-register keybindings for a given command [#8269](https://github.com/eclipse-theia/theia/pull/8269)
@@ -272,6 +270,7 @@
     }
   },
   ```
+
   - Consequently, `ThemeService` and `IconThemeService` don't allow to change the default color or icon theme anymore.
 <a name="1_5_0_drop_node_10_support"></a>
 - [[repo]](#1_5_0_drop_node_10_support) support for `Node 10` is dropped. [#8290](https://github.com/eclipse-theia/theia/pull/8290)
@@ -334,7 +333,7 @@
   - If you implement a custom user storage make sure to check old relative locations, otherwise it can cause user data loss.
 <a name="1_4_0_deprecate_languages"></a>
 - [[languages]](#1_4_0_deprecate_languages) `@theia/languages` extension is deprecated, use VS Code extensions to provide language smartness:
-  https://code.visualstudio.com/api/language-extensions/language-server-extension-guide [#8112](https://github.com/eclipse-theia/theia/pull/8112)
+  <https://code.visualstudio.com/api/language-extensions/language-server-extension-guide> [#8112](https://github.com/eclipse-theia/theia/pull/8112)
 
 ## v1.3.0 - 25/06/2020
 
@@ -682,6 +681,7 @@ Breaking changes:
 - [terminal] added a search widget to terminals [#5471](https://github.com/eclipse-theia/theia/pull/5471)
 - [core] from now on, downstream projects can refine where the configuration files (such as `settings.json`, `keymaps.json`, `recentworkspace.json`, etc.) will be stored by Theia. [#4488](https://github.com/eclipse-theia/theia/pull/4488)\
 The default location remains the same: `~/.theia`, however it can be customized by overriding the `#getConfigDirUri` method of the `EnvVariablesServer` API. The easiest way is to subclass the `EnvVariablesServerImpl` and rebind it in your backend module:
+
   ```ts
   // your-env-variables-server.ts:
 
@@ -715,30 +715,30 @@ Breaking changes:
 - The release includes the removal of language-specific Theia extensions and other Theia extensions that are or can be replaced by equivalent VS Code extensions.
   - Migration steps are available at the following wiki page [`Consuming Builtin and External VS Code Extensions`](https://github.com/eclipse-theia/theia/wiki/Consuming-Builtin-and-External-VS-Code-Extensions).
   - [debug-nodejs] removed the `@theia/debug-nodejs` extension [#6933](https://github.com/eclipse-theia/theia/pull/6933)
-      - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
+    - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
   - [editorconfig] removed the `@theia/editorconfig` extension [#6933](https://github.com/eclipse-theia/theia/pull/6933)
-      - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
+    - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
   - [java] removed the `@theia/java` extension [#6933](https://github.com/eclipse-theia/theia/pull/6933)
-      - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
-      - Please view the `theia-apps` [theia-java](https://github.com/theia-ide/theia-apps/tree/master/theia-java-docker) image for an example application which has been updated to
+    - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
+    - Please view the `theia-apps` [theia-java](https://github.com/theia-ide/theia-apps/tree/master/theia-java-docker) image for an example application which has been updated to
       use VS Code extensions instead of `@theia/java`.
   - [java-debug] removed the `@theia/java-debug` extension [#6933](https://github.com/eclipse-theia/theia/pull/6933)
-      - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
-      - Please view the `theia-apps` [theia-java](https://github.com/theia-ide/theia-apps/tree/master/theia-java-docker) image for an example application which has been updated to
+    - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
+    - Please view the `theia-apps` [theia-java](https://github.com/theia-ide/theia-apps/tree/master/theia-java-docker) image for an example application which has been updated to
       use VS Code extensions instead of `@theia/java-debug`.
   - [merge-conflicts] removed the `@theia/merge-conflicts` extension [#6933](https://github.com/eclipse-theia/theia/pull/6933)
-      - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
+    - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
   - [python] removed the `@theia/python` extension [#6933](https://github.com/eclipse-theia/theia/pull/6933)
-      - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
-      - Please view the `theia-apps` [theia-python](https://github.com/theia-ide/theia-apps/tree/master/theia-python-docker) image for an example application which has been updated to
+    - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
+    - Please view the `theia-apps` [theia-python](https://github.com/theia-ide/theia-apps/tree/master/theia-python-docker) image for an example application which has been updated to
       use VS Code extensions instead of `@theia/python`.
   - [textmate-grammars] removed the `@theia/textmate-grammars` extension [#6933](https://github.com/eclipse-theia/theia/pull/6933)
-      - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
+    - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
   - [tslint] removed the `@theia/tslint` extension [#6933](https://github.com/eclipse-theia/theia/pull/6933)
-      - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
+    - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
   - [typescript] removed the `@theia/typescript` extension [#6933](https://github.com/eclipse-theia/theia/pull/6933)
-      - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
-      - Please view the `theia-apps` [theia-typescript](https://github.com/theia-ide/theia-apps/tree/master/theia-docker) image for an example application which has been updated to
+    - The extension will no longer be maintained by the project and remains in the Git history for anyone who would like to reference it or maintain it.
+    - Please view the `theia-apps` [theia-typescript](https://github.com/theia-ide/theia-apps/tree/master/theia-docker) image for an example application which has been updated to
       use VS Code extensions instead of `@theia/typescript`.
 
 ## v0.15.0 - 30/01/2020
diff --git a/doc/changelogs/CHANGELOG-2021.md b/doc/changelogs/CHANGELOG-2021.md
index f0641b5edef6f..4c9ad1bdb25b7 100644
--- a/doc/changelogs/CHANGELOG-2021.md
+++ b/doc/changelogs/CHANGELOG-2021.md
@@ -638,8 +638,8 @@
 - [core] updated `SearchBox.input` field type from `HTMLInputElement` to `HTMLSpanElement` [#9005](https://github.com/eclipse-theia/theia/pull/9005)
 
 <a name="1.11.0_user-storage_scheme_updated"></a>
--   [[user-storage]](#1.11.0_user-storage_scheme_updated) `UserStorageUri` scheme was changed from 'user_storage' to 'user-storage' as '\_' is not a valid char in scheme (according to [RFC 3986](https://tools.ietf.org/html/rfc3986#page-17)) [#9049](https://github.com/eclipse-theia/theia/pull/9049)
 
+- [[user-storage]](#1.11.0_user-storage_scheme_updated) `UserStorageUri` scheme was changed from 'user_storage' to 'user-storage' as '\_' is not a valid char in scheme (according to [RFC 3986](https://tools.ietf.org/html/rfc3986#page-17)) [#9049](https://github.com/eclipse-theia/theia/pull/9049)
 
 ## v1.10.0 - 1/28/2021
 
diff --git a/doc/changelogs/CHANGELOG-2022.md b/doc/changelogs/CHANGELOG-2022.md
index 69c1869ed05a2..9e70a8ee666bb 100644
--- a/doc/changelogs/CHANGELOG-2022.md
+++ b/doc/changelogs/CHANGELOG-2022.md
@@ -105,9 +105,9 @@ generating the main code bundle (as before), the second serves to generate a *.c
 - [plugin-ext] `when` clauses removed from `codeToTheiaMappings` [#11741](https://github.com/eclipse-theia/theia/pull/#11741)
 - [terminal] the `AbstractCmdClickTerminalContribution` API has been removed in favor of the `TerminalLinkProvider` interface [#11552](https://github.com/eclipse-theia/theia/pull/11552) - Contributed on behalf of STMicroelectronics
 - [typehierarchy] - Adding Support of vscode TypeHierarchy API with the following breaking changes: [#11694](https://github.com/eclipse-theia/theia/pull/11694)
-  -  [plugin-ext/main] The file `callhierarchy-type-converters.ts` was renamed to `hierarchy-types-converters.ts`
-      - The method `toDefinition` was renamed to `toItemHierarchyDefinition` and the overloaded signatures were removed.
-      - The method `fromDefinition` was replaced for `fromItemHierarchyDefinition` to convert both `TypeHierarchyItem` and `CallHierarchyItem` to a common `HierarchyItem`.
+  - [plugin-ext/main] The file `callhierarchy-type-converters.ts` was renamed to `hierarchy-types-converters.ts`
+    - The method `toDefinition` was renamed to `toItemHierarchyDefinition` and the overloaded signatures were removed.
+    - The method `fromDefinition` was replaced for `fromItemHierarchyDefinition` to convert both `TypeHierarchyItem` and `CallHierarchyItem` to a common `HierarchyItem`.
   - [plugin-ext/plugin] - `type-converters.ts #fromCallHierarchyItem` was replaced by `fromHierarchyItem` to convert from `CallHierarchyItem` or `TypeHierarchyItem` to `HierarchyItem`.
 
 ## v1.30.0 - 9/29/2022
@@ -569,9 +569,9 @@ generating the main code bundle (as before), the second serves to generate a *.c
 - [debug] The interface method `DebugService#provideDynamicDebugConfigurations` changes the return type to `Record<string, DebugConfiguration[]>` [#10910](https://github.com/eclipse-theia/theia/pull/10910)
   This impacts the corresponding return type for `DebugConfigurationManager#provideDynamicDebugConfigurations`.
   The following functions under `plugin-api-rpc.ts#DebugExt` and in the `PluginDebugAdapterContribution` are deprecated
-    * $provideDebugConfigurations
-    * $resolveDebugConfigurations
-    * $resolveDebugConfigurationWithSubstitutedVariablesByHandle
+  - $provideDebugConfigurations
+  - $resolveDebugConfigurations
+  - $resolveDebugConfigurationWithSubstitutedVariablesByHandle
     The `PluginDebugAdapterContributionRegistrator` interface has been removed
 - [filesystem] The `generateUniqueResourceURI` method from the `FileSystemUtils` class has an updated signature. Additionally, the method now returns a generated Uri that uses spaces as separators. The naming scheme was also changed to match VSCode. [10767](https://github.com/eclipse-theia/theia/pull/10767)
 - [markers] `ProblemDecorator` reimplemented to reduce redundancy and align more closely with VSCode. `collectMarkers` now returns `Map<string, TreeDecoration.Data>`, `getOverlayIconColor` renamed to `getColor`, `getOverlayIcon` removed, `appendContainerMarkers` returns `void` [#10820](https://github.com/eclipse-theia/theia/pull/10820)
diff --git a/doc/code-organization.md b/doc/code-organization.md
index e091efc6a4eaa..10e8bc1c8edf1 100644
--- a/doc/code-organization.md
+++ b/doc/code-organization.md
@@ -12,4 +12,4 @@ The code is fully implemented in [TypeScript](https://github.com/microsoft/types
 - `electron-browser/*`: Source code that requires the [Electron renderer process](https://github.com/atom/electron/tree/master/docs#modules-for-the-renderer-process-web-page) APIs.
   - May use code from: `common`, `browser`.
 - `electron-main/*`: Source code that requires the [Electron main process](https://github.com/atom/electron/tree/master/docs#modules-for-the-main-process) APIs.
-  - May use code from: `electron-node`, `common`, `node`.
\ No newline at end of file
+  - May use code from: `electron-node`, `common`, `node`.
diff --git a/doc/coding-guidelines.md b/doc/coding-guidelines.md
index b3706d79e0aa7..f22e8b4f81f8a 100644
--- a/doc/coding-guidelines.md
+++ b/doc/coding-guidelines.md
@@ -1,13 +1,17 @@
 # Coding Guidelines
 
 ## Indentation
+
 Use 4 spaces per indentation level.
 
 ## Imports
+
 Use `organize imports` to sort imports, and make sure the imports work properly (e.g. imports from `/src/` rather than `/lib/` for *.ts files may break builds).
 
 ## Names
+
 <a name="pascalcase-type"></a>
+
 * [1.](#pascalcase-type) Use PascalCase for `type` names.
 <a name="pascalcase-enum"></a>
 * [2.](#pascalcase-enum) Use PascalCase for `enum` values.
@@ -18,6 +22,7 @@ Use `organize imports` to sort imports, and make sure the imports work properly
 <a name="whole-words-names"></a>
 * [5.](#whole-words-names) Use whole words in names when possible.
 <a name="lower-case-names"></a>
+
 ```ts
 // bad
 const termWdgId = 1;
@@ -25,16 +30,23 @@ const termWdgId = 1;
 // good
 const terminalWidgetId = 1;
 ```
+
 * [6.](#lower-case-names) Use lower-case, dash-separated file names (e.g. `document-provider.ts`).
 <a name="file-name"></a>
 * [7.](#file-name) Name files after the main type it exports.
+
 > Why? It should be easy to find a type by a file name.
 <a name="one-large-class-per-file"></a>
+
 * [7.1](#one-large-class-per-file) Avoid one file with many large classes; put each class in its own file.
+
 > Why? It should be easy to find a class by a file name.
 <a name="unique-names"></a>
+
 * [8.](#unique-names) Give unique names to types and files. Use specific names to achieve it.
+
 > Why? In order to avoid duplicate records in file and type search.
+
 ```ts
 // bad
 export interface TitleButton {}
@@ -42,7 +54,9 @@ export interface TitleButton {}
 // good
 export interface QuickInputTitleButton {}
 ```
+
 <a name="no_underscore_private"></a>
+
 * [9.](#no_underscore_private) Do not use "_" as a prefix for private properties. Exceptions:
 <a name="underscore_accessors"></a>
   * [9.1](#underscore_accessors) Exposing a property through get/set and using underscore for the internal field.
@@ -52,6 +66,7 @@ export interface QuickInputTitleButton {}
 * [10.](#event_names) Names of events follow the `on[Will|Did]VerbNoun?` pattern. The name signals if the event is going to happen (onWill) or already happened (onDid), what happened (verb), and the context (noun) unless obvious from the context.
 <a name="unique-context-keys"></a>
 * [11.](#unique-context-keys) Give unique names to keybinding contexts and keys to avoid collisions at runtime. Use specific names to achieve it.
+
 ```ts
 // bad
 export namespace TerminalSearchKeybindingContext {
@@ -71,7 +86,9 @@ const terminalFocusKey = this.contextKeyService.createKey<boolean>('terminalFocu
 ```
 
 ## Types
+
 <a name="no-expose-types"></a>
+
 * [1.](#no-expose-types) Do not export `types` or `functions` unless you need to share it across multiple components, [see as well](#di-function-export).
 <a name="no-global-types"></a>
 * [2.](#no-global-types) Do not introduce new `types` or `values` to the global namespace.
@@ -81,6 +98,7 @@ const terminalFocusKey = this.contextKeyService.createKey<boolean>('terminalFocu
 ## Interfaces/Symbols
 
 <a name="interfaces-no-i-prefix"></a>
+
 * [1.](#interfaces-no-i-prefix) Do not use `I` prefix for interfaces. Use `Impl` suffix for implementation of interfaces with the same name. See [624](https://github.com/theia-ide/theia/issues/624) for the discussion on this.
 <a name="classes-over-interfaces"></a>
 * [2.](#classes-over-interfaces) Use classes instead of interfaces + symbols when possible to avoid boilerplate.
@@ -108,25 +126,31 @@ bind(TaskDefinitionRegistry).toSelf().inSingletonScope();
 
 **Exceptions**
 <a name="remote-interfaces"></a>
+
 * [2.1](#remote-interfaces) Remote services should be declared as an interface + a symbol in order to be used in the frontend and backend.
 
 ## Comments
+
 * Use JSDoc style comments for `functions`, `interfaces`, `enums`, and `classes`
 
 ## Strings
+
 * Use 'single quotes' for all strings that aren't [template literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals)
 
 ## null and undefined
+
 Use `undefined`; do not use `null`.
 
 ## Internationalization/Localization
 
 <a name="nls-localize"></a>
+
 * [1.](#nls-localize) Always localize user-facing text with the `nls.localize(key, defaultValue, ...args)` function.
 
 > What is user-facing text? Any strings that are hard-coded (not calculated) that could be in any way visible to the user, be it labels for commands and menus, messages/notifications/dialogs, quick-input placeholders or preferences.
 
 <a name="nls-localize-args"></a>
+
 * [1.1.](#nls-localize-args) Parameters for messages should be passed as the `args` of the `localize` function. They are inserted at the location of the placeholders - in the form of `{\d+}` - in the localized text. E.g. `{0}` will be replaced with the first `arg`, `{1}` with the second, etc.
 
 ```ts
@@ -138,6 +162,7 @@ nls.localize('hello', 'Hello there {0}.', name);
 ```
 
 <a name="nls-localize-by-default"></a>
+
 * [1.2.](#nls-localize-by-default) The `nls.localizeByDefault` function automatically finds the translation key for VS Code's language packs just by using the default value as its argument and translates it into the currently used locale. If the `nls.localizeByDefault` function is not able to find a key for the supplied default value, a warning will be shown in the browser console. If there is no appropriate translation in VSCode, just use the `nls.localize` function with a new key using the syntax `theia/<package>/<id>`.
 
 ```ts
@@ -149,7 +174,9 @@ nls.localizeByDefault('Close');
 ```
 
 <a name="nls-utilities"></a>
+
 * [2.](#nls-utilities) Use utility functions where possible:
+
 ```ts
 // bad
 command: Command = { label: nls.localize(key, defaultValue), originalLabel: defaultValue };
@@ -159,6 +186,7 @@ command = Command.toLocalizedCommand({ id: key, label: defaultValue });
 ```
 
 ## Style
+
 * Use arrow functions `=>` over anonymous function expressions.
 * Only surround arrow function parameters when necessary. For example, `(x) => x + x` is wrong, but the following are correct:
 
@@ -177,11 +205,14 @@ for (var i = 0, n = str.length; i < 10; i++) { }
 if (x < 10) { }
 function f(x: number, y: string): void { }
 ```
- * Use a single declaration per variable statement <br />(i.e. use `var x = 1; var y = 2;` over `var x = 1, y = 2;`).
- * `else` goes on the line of the closing curly brace.
+
+* Use a single declaration per variable statement <br />(i.e. use `var x = 1; var y = 2;` over `var x = 1, y = 2;`).
+* `else` goes on the line of the closing curly brace.
 
 ## Dependency Injection
+
 <a name="property-injection"></a>
+
 * [1.](#property-injection) Use property injection over construction injection. Adding new dependencies via the construction injection is a breaking change.
 <a name="post-construct"></a>
 * [2.](#post-construct) Use a method decorated with `postConstruct` rather than the constructor to initialize an object, for example to register event listeners.
@@ -200,7 +231,9 @@ export class MyComponent {
 
 }
 ```
+
 <a name="singleton-scope"></a>
+
 * [3.](#singleton-scope) Make sure to add `inSingletonScope` for singleton instances, otherwise a new instance will be created on each injection request.
 
 ```ts
@@ -210,7 +243,9 @@ bind(CommandContribution).to(LoggerFrontendContribution);
 // good
 bind(CommandContribution).to(LoggerFrontendContribution).inSingletonScope();
 ```
+
 <a name="di-function-export"></a>
+
 * [4.](#di-function-export) Don't export functions, convert them into class methods. Functions cannot be overridden to change their behavior or work around a bug.
 
 ```ts
@@ -237,11 +272,14 @@ export class MyWebSocketProvider extends WebSocketProvider {
 
 **Exceptions**
 <a name="di-convenient-function-export"></a>
+
 * [4.1](#di-convenient-function-export) Convenient functions which are based on the stable API can be exported in the corresponding namespace.
 
 In this case clients:
-   - can customize behaviour via exchanging the API implementation
-   - have a choice to use convenient functions or an API directly
+
+* can customize behaviour via exchanging the API implementation
+* have a choice to use convenient functions or an API directly
+
 ```ts
 export namespace MonacoEditor {
     // convenient function to get a Monaco editor based on the editor manager API
@@ -251,10 +289,13 @@ export namespace MonacoEditor {
     ...
 }
 ```
+
 <a name="di-json-function-export"></a>
+
 * [4.2](#di-json-function-export) The special case of [4.1](#di-convenient-function-export) is functions on a JSON type.
 
 JSON types are not supposed to be *implementable*, but only *instantiable*. They cannot have functions to avoid serialization issues.
+
 ```ts
 export interface CompositeTreeNode extends TreeNode {
     children: ReadonlyArray<TreeNode>;
@@ -281,7 +322,9 @@ export interface MyCompositeTreeNode extends CompositeTreeNode {
     ...
 }
 ```
+
 <a name="di-auxiliary-function-export"></a>
+
 * [4.3](#di-auxiliary-function-export) Auxiliary functions which are called from the customizable context can be exported in the corresponding namespace.
 
 ```ts
@@ -300,36 +343,47 @@ export namespace DirtyDiffModel {
     }
 }
 ```
+
 <a name="no-multi-inject"></a>
+
 * [5.](#no-multi-inject) Don't use InversifyJS's `@multiInject`, use Theia's utility `ContributionProvider` to inject multiple instances.
-> Why?
-> - `ContributionProvider` is a documented way to introduce contribution points. See `Contribution-Points`: https://www.theia-ide.org/docs/services_and_contributions
-> - If nothing is bound to an identifier, multi-inject resolves to `undefined`, not an empty array. `ContributionProvider` provides an empty array.
-> - Multi-inject does not guarantee the same instances are injected if an extender does not use `inSingletonScope`. `ContributionProvider` caches instances to ensure uniqueness.
-> - `ContributionProvider` supports filtering. See `ContributionFilterRegistry`.
 
+> Why?
+>
+> * `ContributionProvider` is a documented way to introduce contribution points. See `Contribution-Points`: <https://www.theia-ide.org/docs/services_and_contributions>
+> * If nothing is bound to an identifier, multi-inject resolves to `undefined`, not an empty array. `ContributionProvider` provides an empty array.
+> * Multi-inject does not guarantee the same instances are injected if an extender does not use `inSingletonScope`. `ContributionProvider` caches instances to ensure uniqueness.
+> * `ContributionProvider` supports filtering. See `ContributionFilterRegistry`.
 
 ## CSS
+
 <a name="css-use-lower-case-with-dashes"></a>
+
 * [1.](#css-use-lower-case-with-dashes) Use the `lower-case-with-dashes` format.
 <a name="css-prefix-global-classes"></a>
 * [2.](#css-prefix-global-classes) Prefix classes with `theia` when used as global classes.
 <a name="no-styles-in-code"></a>
 * [3.](#no-styles-in-code) Do not define styles in code. Introduce proper CSS classes.
+
 > Why? It is not possible to play with such styles in the dev tools without recompiling the code. CSS classes can be edited in the dev tools.
 
 ## Theming
+
 <a name="theming-no-css-color-variables"></a>
+
 * [1.](#theming-no-css-color-variables) Do not introduce CSS color variables. Implement `ColorContribution` and use `ColorRegistry.register` to register new colors.
 <a name="theming-no-css-color-values"></a>
 * [2.](#theming-no-css-color-values) Do not introduce hard-coded color values in CSS. Instead, refer to [VS Code colors](https://code.visualstudio.com/api/references/theme-color) in CSS by prefixing them with `--theia` and replacing all dots with dashes. For example `widget.shadow` color can be referred to in CSS with `var(--theia-widget-shadow)`.
 <a name="theming-derive-colors-from-vscode"></a>
 * [3.](#theming-derive-colors-from-vscode) Always derive new colors from existing [VS Code colors](https://code.visualstudio.com/api/references/theme-color). New colors can be derived from an existing color by plain reference, e.g. `dark: 'widget.shadow'`, or transformation, e.g. `dark: Color.lighten('widget.shadow', 0.4)`.
+
 > Why? Otherwise, there is no guarantee that new colors will fit well into new VSCode color themes.
 <a name="theming-theia-colors"></a>
+
 * [4.](#theming-theia-colors) Apply different color values only in concrete Theia themes, see [Light (Theia)](https://github.com/eclipse-theia/theia/blob/master/packages/monaco/data/monaco-themes/vscode/light_theia.json), [Dark (Theia)](https://github.com/eclipse-theia/theia/blob/master/packages/monaco/data/monaco-themes/vscode/dark_theia.json) and [High Contrast (Theia)](https://github.com/eclipse-theia/theia/blob/master/packages/monaco/data/monaco-themes/vscode/hc_theia.json) themes.
 <a name="theming-variable-naming"></a>
 * [5.](#theming-variable-naming) Names of variable follow the `object.property` pattern.
+
 ```ts
 // bad
 'button.secondary.foreground'
@@ -341,9 +395,11 @@ export namespace DirtyDiffModel {
 ```
 
 ## React
+
 <a name="no-bind-fn-in-event-handlers"></a>
+
 * [1.](#no-bind-fn-in-event-handlers) Do not bind functions in event handlers.
-  - Extract a React component if you want to pass state to an event handler function.
+  * Extract a React component if you want to pass state to an event handler function.
 
 > Why? Because doing so creates a new instance of the event handler function on each render and breaks React element caching leading to re-rendering and bad performance.
 
@@ -394,22 +450,30 @@ class MyWidget extends ReactWidget {
 ```
 
 ## URI/Path
+
 <a name="uri-over-path"></a>
+
 * [1.](#uri-over-path) Pass URIs between frontend and backend, never paths. URIs should be sent as strings in JSON-RPC services, e.g. `RemoteFileSystemServer` accepts strings, not URIs.
+
 > Why? Frontend and backend can have different operating systems leading to incompatibilities between paths. URIs are normalized in order to be OS-agnostic.
 <a name="frontend-fs-path"></a>
+
 * [2.](#frontend-fs-path) Use `FileService.fsPath` to get a path on the frontend from a URI.
 <a name="backend-fs-path"></a>
 * [3.](#backend-fs-path) Use `FileUri.fsPath` to get a path on the backend from a URI. Never use it on the frontend.
 <a name="uri-scheme"></a>
 * [4.](#explicit-uri-scheme) Always define an explicit scheme for a URI.
+
 > Why? A URI without scheme will fall back to `file` scheme for now; in the future it will lead to a runtime error.
 <a name="frontend-path"></a>
+
 * [5.](#frontend-path) Use `Path` Theia API to manipulate paths on the frontend. Don't use Node.js APIs like `path` module. Also see [the code organization guideline](code-organization.md).
 <a name="backend-fs"></a>
 * [6.](#backend-fs) On the backend, use Node.js APIS to manipulate the file system, like `fs` and `fs-extra` modules.
+
 > Why? `FileService` is to expose file system capabilities to the frontend only. It's aligned with expectations and requirements on the frontend. Using it on the backend is not possible.
 <a name="use-long-name"></a>
+
 * [7.](#use-long-name) Use `LabelProvider.getLongName(uri)` to get a system-wide human-readable representation of a full path. Don't use `uri.toString()` or `uri.path.toString()`.
 <a name="use-short-name"></a>
 * [8.](#use-short-name) Use `LabelProvider.getName(uri)` to get a system-wide human-readable representation of a simple file name.
@@ -417,7 +481,9 @@ class MyWidget extends ReactWidget {
 * [9.](#use-icon) Use `LabelProvider.getIcon(uri)` to get a system-wide file icon.
 <a name="uri-no-string-manipulation"></a>
 * [10.](#uri-no-string-manipulations) Don't use `string` to manipulate URIs and paths. Use `URI` and `Path` capabilities instead, like `join`, `resolve` and `relative`.
+
 > Why? Because object representation can handle corner cases properly, like trailing separators.
+
 ```ts
 // bad
 uriString + '/' + pathString
@@ -433,8 +499,11 @@ new Path(absolutePathString).relative(pathString)
 ```
 
 ## Logging
+
 <a name="logging-use-console-log"></a>
+
 * [1.](#logging-use-console-log) Use `console` instead of `ILogger` for the root (top-level) logging.
+
 ```ts
 // bad
 @inject(ILogger)
@@ -445,12 +514,15 @@ this.logger.info(``);
 // good
 console.info(``)
 ```
+
 > Why? All calls to console are intercepted on the frontend and backend and then forwarded to an `ILogger` instance already. The log level can be configured from the CLI: `theia start --log-level=debug`.
 
 ## "To Do" Tags
+
 There are situations where we can't properly implement some functionality at the time we merge a PR. In those cases, it is sometimes good practice to leave an indication that something needs to be fixed later in the code. This can be done by putting a "tag" string in a comment. This allows us to find the places we need to fix again later. Currently, we use two "standard" tags in Theia:
- * `@stubbed`
+
+* `@stubbed`
    This tag is used in VS Code API implementations. Sometimes we need an implementation of an API in order for VS Code extensions to start up correctly, but we can't provide a proper  implementation of the underlying feature at this time. This might be because a certain feature has no corresponding UI in Theia or because we do not have the resources to provide a proper implementation.
 Using the `@stubbed` tag in a JSDoc comment will mark the element as "stubbed" on the [API status page](https://eclipse-theia.github.io/vscode-theia-comparator/status.html)
- * `@monaco-uplift`
+* `@monaco-uplift`
    Use this tag when some functionality can be added or needs to be fixed when we move to a newer version of the monaco editor. If you know which minimum version of Monaco we need, you can add that as a reminder.
diff --git a/doc/pull-requests.md b/doc/pull-requests.md
index 17d98da5062bc..4fb65ecc994f8 100644
--- a/doc/pull-requests.md
+++ b/doc/pull-requests.md
@@ -4,13 +4,13 @@ This document clarifies rules and expectations of contributing and reviewing pul
 It is structured as a list of rules which can be referenced on a PR to moderate and drive discussions.
 If a rule causes distress during discussions itself, it has to be reviewed on [the dev meeting](https://github.com/eclipse-theia/theia/wiki/Dev-Meetings) and updated.
 
- - [**Opening a Pull Request**](#opening-a-pull-request)
- - [**Requesting a Review**](#requesting-a-review)
- - [**Review Checklist**](#review-checklist)
- - [**Reviewing**](#reviewing)
- - [**Landing**](#landing)
- - [**Reverting**](#reverting)
- - [**Closing**](#closing)
+- [**Opening a Pull Request**](#opening-a-pull-request)
+- [**Requesting a Review**](#requesting-a-review)
+- [**Review Checklist**](#review-checklist)
+- [**Reviewing**](#reviewing)
+- [**Landing**](#landing)
+- [**Reverting**](#reverting)
+- [**Closing**](#closing)
 
 ## Opening a Pull Request
 
@@ -19,16 +19,19 @@ If a rule causes distress during discussions itself, it has to be reviewed on [t
 - [1.](#pr-template) Each PR description has to follow the [PR template](https://github.com/eclipse-theia/theia/blob/master/.github/PULL_REQUEST_TEMPLATE.md)
 
 <a name="design-review"></a>
+
 - [2.](#design-review) A PR can be opened early for the design review before going into the detailed implementation.
   - A request on the design review should be an explicit comment.
   - Such PR should be marked as a draft or with the WIP prefix.
 
 <a name="fixups"></a>
+
 - [3.](#fixups) Changes done _after_ the PR has been opened should be kept in separate commits until the review process is finished. This allows reviewers to re-review only the updated parts of the PR and to determine what needs to be tested again. The "fixup" commits must be squashed before merging in order to keep a clean history.
 
 ## Requesting a Review
 
 <a name="review-reqs"></a>
+
 - [1.](#review-reqs) A review can be requested when:
   - [The PR template](#pr-template) is filled in.
   - Changes are thoroughly tested by an author.
@@ -42,6 +45,7 @@ If a rule causes distress during discussions itself, it has to be reviewed on [t
 ## Review Checklist
 
 <a name="checklist-build-and-test"></a>
+
 - [1.](#checklist-build-and-test) The new code is built and tested according to the `How to test` section of a PR description.
 <a name="checklist-project-org"></a>
 - [2.](#checklist-project-org) The new code is aligned with the [project organization](code-organization.md) and [coding conventions](coding-guidelines.md).
@@ -56,7 +60,7 @@ If a rule causes distress during discussions itself, it has to be reviewed on [t
 <a name="checklist-copyright"></a>
 - [6.](#checklist-copyright) Each new file has proper copyright with the current year and the name of contributing entity (individual or company).
 <a name="checklist-sign-off"></a>
-- [7.](#checklist-sign-off) Commits are signed-off: https://github.com/eclipse-theia/theia/blob/master/CONTRIBUTING.md#sign-your-work.
+- [7.](#checklist-sign-off) Commits are signed-off: <https://github.com/eclipse-theia/theia/blob/master/CONTRIBUTING.md#sign-your-work>.
 <a name="checklist-meaningful-commits"></a>
 - [8.](#checklist-meaningful-commit) Each commit has meaningful title and a body that explains what it does. One can take inspiration from the `What it does` section from the PR.
 <a name="checklist-commit-history"></a>
@@ -66,6 +70,7 @@ If a rule causes distress during discussions itself, it has to be reviewed on [t
 ## Reviewing
 
 <a name="reviewing-template"></a>
+
 - [1.](#reviewing-template) Reviewers should check that a PR has a [proper description](#pr-template).
 <a name="reviewing-fn"></a>
 - [2.](#reviewing-fn) Reviewers should build and verify changes according to the `How to test` section of a PR description.
@@ -79,6 +84,7 @@ If a rule causes distress during discussions itself, it has to be reviewed on [t
 ### Requesting Changes
 
 <a name="changes-review-reqs"></a>
+
 - [1.](#changes-review-reqs) Changes should be requested if an author does not follow the [review requirements](#review-reqs).
 <a name="changes-no-nit"></a>
 - [2.](#changes-no-nit) Changes cannot be requested because of the personal preferences of a reviewer.
@@ -93,6 +99,7 @@ If a rule causes distress during discussions itself, it has to be reviewed on [t
 ### Approving
 
 <a name="justifying-approve"></a>
+
 - [1.](#justifying-approve) Each approval should have supporting comments following these guidelines.
 <a name="dismissing-approve"></a>
 - [2.](#dismissing-approve) An approval without a comment should be dismissed.
@@ -102,6 +109,7 @@ If a rule causes distress during discussions itself, it has to be reviewed on [t
 ### Collaborating
 
 <a name="collaboration-on-pr"></a>
+
 - [1.](#collaboration-on-pr) If a change request is important, but cannot be elaborated by a reviewer,
 then a reviewer should be encouraged to open an alternative PR or collaborate on a current PR.
 <a name="completing-pr"></a>
@@ -116,6 +124,7 @@ provided that the original author accepted the [ECA](https://github.com/eclipse-
 ## Landing
 
 <a name="landing-pr"></a>
+
 - [1.](#landing-pr) A PR can be landed when:
   - CI build has succeeded.
   - The author has accepted the [Eclipse Contributor Agreement](https://github.com/eclipse-theia/theia/blob/master/CONTRIBUTING.md#eclipse-contributor-agreement).
@@ -130,12 +139,14 @@ provided that the original author accepted the [ECA](https://github.com/eclipse-
 ## Reverting
 
 <a name="reverting-pr"></a>
+
 - [1.](#reverting-pr) If a PR causes regressions after landing
 then an author and maintainers have 2 days to resolve them after that a PR has to be reverted.
 
 ## Closing
 
 <a name="closing-pr"></a>
+
 - [1.](#closing-pr) A reviewer cannot close a PR without a reason.
 <a name="closing-pr-reasons"></a>
 - [2.](#closing-pr-reasons) A PR may be closed, for example, because of the following reasons:
diff --git a/doc/runtime-policy.md b/doc/runtime-policy.md
index 551b1513c4b04..cb27cfe422dd0 100644
--- a/doc/runtime-policy.md
+++ b/doc/runtime-policy.md
@@ -4,9 +4,9 @@
 
 We aim to support Node.js current _Active LTS_ version.
 
-See https://nodejs.org/en/about/releases/ to see the status of Node.js versions.
+See <https://nodejs.org/en/about/releases/> to see the status of Node.js versions.
 
-We recommend setting up your environment to run Theia using the Node.js _Active LTS_, but any supported version should work as well. File an issue otherwise: https://github.com/eclipse-theia/theia/issues/new/choose.
+We recommend setting up your environment to run Theia using the Node.js _Active LTS_, but any supported version should work as well. File an issue otherwise: <https://github.com/eclipse-theia/theia/issues/new/choose>.
 
 Note that the Node.js version you should use depends on your own project's dependencies: packages other than Theia might have their own requirements, so we try to support a reasonable range for adopters to be able to satisfy such constraints.
 
@@ -24,7 +24,7 @@ Note that the Node.js version you should use depends on your own project's depen
 
 We aim to use Electron's latest _Stable Release_.
 
-See https://www.electronjs.org/releases/stable to see the latest Electron stable releases.
+See <https://www.electronjs.org/releases/stable> to see the latest Electron stable releases.
 
 Note that clearing new Electron releases IP-wise is a lot of work and may cause us to lag behind a bit.
 
diff --git a/doc/vscode-usage.md b/doc/vscode-usage.md
index f86f3ad975743..adc8b64c2d087 100644
--- a/doc/vscode-usage.md
+++ b/doc/vscode-usage.md
@@ -1,6 +1,6 @@
 ## Using code from VS Code
 
-Since its inception, Theia has used the "Monaco" editor component from VS Code. With the recent move to using ECMAScript modules, consuming code from the VS Code project has become much easier and safer. But while reusing code saves us work, there is also a downside to it. Monaco has a relatively stable external API because Microsoft also releases it as a stand-alone editor component. But other parts of the code base may change more frequently and in unexpected ways. We always use the same version of all modules making up VS Code. So when we update VS Code, often to provide a new feature in Monaco to our adopters, we will have to deal with all the API changes at that same time. As an example: Theia used the quick-input component from VS Code directly to implement it's own quick-input component. Because the component was not encapsulated in any way, the updating Monaco to a new version became difficult and time-consuming. 
+Since its inception, Theia has used the "Monaco" editor component from VS Code. With the recent move to using ECMAScript modules, consuming code from the VS Code project has become much easier and safer. But while reusing code saves us work, there is also a downside to it. Monaco has a relatively stable external API because Microsoft also releases it as a stand-alone editor component. But other parts of the code base may change more frequently and in unexpected ways. We always use the same version of all modules making up VS Code. So when we update VS Code, often to provide a new feature in Monaco to our adopters, we will have to deal with all the API changes at that same time. As an example: Theia used the quick-input component from VS Code directly to implement it's own quick-input component. Because the component was not encapsulated in any way, the updating Monaco to a new version became difficult and time-consuming.
 
 So while we don't  prohibit the use of code from VS Code (other than the Monaco editor API), we have the following goals:
 
@@ -12,12 +12,10 @@ In order to achieve those goals, follow these simple rules:
 
 * Never export a type, function or variable from an internal VS Code API from a theia package
 
-* Don't use code from VS Code that you could not easily copy into the Theia codebase if the need arises. 
+* Don't use code from VS Code that you could not easily copy into the Theia codebase if the need arises.
 
 The first rule shields our adopters from having to change their code in response to updating Monaco. If they cannot see an object or type, they cannot rely on its existence or API. Note that this includes functions, supertype relationships or parameter and return types. If you need to export functionality, export an interface in Theia and import that interface using imported code from VS Code. This way, we can build adapters to shield against API changes. The rule also prevents spreading dependencies on VS Code in our code without our being aware of them.  While it's not technically possible to enforce non-export of stuff in our current build system, we should make sure we're not exporting tainted code through `index.ts` or similar mechanisms. At the very least, we should not require package users to rely on VS Code stuff.
 
 The second rule  ensures that we do not rely on VS Code stuff that is deeply coupled with other parts of VS Code that we don't want to import. It gives us the escape hatch of just copying the old version of the code and filing a CQ with the Eclipse foundation if updating to the version of stuff from VS Code is not what we want (because it doesn't fit our needs or takes to long).
 
 Tip: you can find locations where VS code is used by searching for import statements from `@theia/monaco-editor-core/esm/vs`.
-
-
diff --git a/examples/api-provider-sample/README.md b/examples/api-provider-sample/README.md
index dff79d5296502..09f4c8b3e1109 100644
--- a/examples/api-provider-sample/README.md
+++ b/examples/api-provider-sample/README.md
@@ -14,6 +14,7 @@
 
 The `@theia/api-provider-sample` extension is a programming example showing how to define and provide a custom API object for _plugins_ to use.
 The purpose of the extension is to:
+
 - provide developers with realistic coding examples of providing custom API objects
 - provide easy-to-use and test examples for features when reviewing pull requests
 
@@ -31,7 +32,7 @@ The source code is laid out in the `src/` tree as follows:
   The `GreetingExtImpl` and similar classes communicate with the actual API implementation (`GreetingMainImpl` etc.) classes in the main Theia process via RPC
 - `node/` — the API classes implementing `GreetingMain` and similar interfaces and the Inversify bindings that register the API provider.
   All code in this directory runs in the main Theia Node process
- - `common/` — the RPC API Ext/Main interface definitions corresponding to the backend of the `gotd` plugin API
+- `common/` — the RPC API Ext/Main interface definitions corresponding to the backend of the `gotd` plugin API
 
 ## Additional Information
 
@@ -44,5 +45,6 @@ The source code is laid out in the `src/` tree as follows:
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/examples/api-samples/README.md b/examples/api-samples/README.md
index 4ac5674d95695..fed4841ec5287 100644
--- a/examples/api-samples/README.md
+++ b/examples/api-samples/README.md
@@ -14,6 +14,7 @@
 
 The `@theia/api-samples` extension contains programming examples on how to use internal APIs.
 The purpose of the extension is to:
+
 - provide developers with real-world coding examples using internal APIs, dependency injection, etc.
 - provide easy-to-use and test examples for features when reviewing pull-requests.
 
@@ -36,5 +37,6 @@ for testing purposes only. It is currently hosted at
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/examples/playwright/README.md b/examples/playwright/README.md
index 43e636176ffa6..54ac730771a84 100644
--- a/examples/playwright/README.md
+++ b/examples/playwright/README.md
@@ -51,4 +51,4 @@ It is [extensible](./docs/EXTENSIBILITY.md) so you can add dedicated page object
 ## Trademark
 
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/package.json b/package.json
index 1fa803a3e513e..f79f3965091cb 100644
--- a/package.json
+++ b/package.json
@@ -81,6 +81,7 @@
     "postinstall": "theia-patch",
     "prepare": "yarn -s compile:references && lerna run prepare && yarn -s compile",
     "publish:latest": "lerna publish --exact --yes --no-push",
+    "publish:patch": "lerna publish --exact --yes --no-push --dist-tag patch",
     "publish:next": "lerna publish preminor --exact --canary --preid next --dist-tag next --no-git-reset --no-git-tag-version --no-push --yes && yarn -s publish:check",
     "publish:check": "node scripts/check-publish.js",
     "rebuild:clean": "rimraf .browser_modules",
diff --git a/packages/ai-chat-ui/README.md b/packages/ai-chat-ui/README.md
index 3638d69df5491..c0bb8e983dc43 100644
--- a/packages/ai-chat-ui/README.md
+++ b/packages/ai-chat-ui/README.md
@@ -28,5 +28,6 @@ It is based on `@theia/ai-chat`.
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/ai-chat/README.md b/packages/ai-chat/README.md
index 6f394ce95cc55..ef29db087aa17 100644
--- a/packages/ai-chat/README.md
+++ b/packages/ai-chat/README.md
@@ -26,5 +26,6 @@ It serves as the basis for `@theia/ai-chat-ui` to provide the Chat UI.
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/ai-code-completion/README.md b/packages/ai-code-completion/README.md
index 938ca2c78ffd9..5f0dcf962e50d 100644
--- a/packages/ai-code-completion/README.md
+++ b/packages/ai-code-completion/README.md
@@ -26,5 +26,6 @@ The user can separately enable code completion items as well as inline code comp
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/ai-core/README.md b/packages/ai-core/README.md
index 1cd399aaff0e1..4f7d97e42a0dc 100644
--- a/packages/ai-core/README.md
+++ b/packages/ai-core/README.md
@@ -26,5 +26,6 @@ It manages the integration of language models and provides core concepts like ag
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/ai-history/README.md b/packages/ai-history/README.md
index 40bc5e9f87495..151f30268b859 100644
--- a/packages/ai-history/README.md
+++ b/packages/ai-history/README.md
@@ -26,5 +26,6 @@ It also offers a view to inspect the history.
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/ai-hugging-face/README.md b/packages/ai-hugging-face/README.md
index b92925c32d26c..306c32e4f9db1 100644
--- a/packages/ai-hugging-face/README.md
+++ b/packages/ai-hugging-face/README.md
@@ -29,4 +29,4 @@ Alternatively, the Hugging Face API key can also be provided via the `HUGGINGFAC
 ## Trademark
 
 "Theia" is a trademark of the Eclipse Foundation  
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/ai-llamafile/README.md b/packages/ai-llamafile/README.md
index 17a4dc5464a8e..135242723a849 100644
--- a/packages/ai-llamafile/README.md
+++ b/packages/ai-llamafile/README.md
@@ -4,21 +4,21 @@ The AI Llamafile package provides an integration that allows users to manage and
 
 ## Features
 
--   Start and stop Llamafile language servers.
+- Start and stop Llamafile language servers.
 
 ## Commands
 
 ### Start Llamafile
 
--   **Command ID:** `llamafile.start`
--   **Label:** `Start Llamafile`
--   **Functionality:** Allows you to start a Llamafile language server by selecting from a list of configured Llamafiles.
+- **Command ID:** `llamafile.start`
+- **Label:** `Start Llamafile`
+- **Functionality:** Allows you to start a Llamafile language server by selecting from a list of configured Llamafiles.
 
 ### Stop Llamafile
 
--   **Command ID:** `llamafile.stop`
--   **Label:** `Stop Llamafile`
--   **Functionality:** Allows you to stop a running Llamafile language server by selecting from a list of currently running Llamafiles.
+- **Command ID:** `llamafile.stop`
+- **Label:** `Stop Llamafile`
+- **Functionality:** Allows you to stop a running Llamafile language server by selecting from a list of currently running Llamafiles.
 
 ## Usage
 
diff --git a/packages/ai-openai/README.md b/packages/ai-openai/README.md
index 1ec7facb4a1b0..ef06dddb04890 100644
--- a/packages/ai-openai/README.md
+++ b/packages/ai-openai/README.md
@@ -45,5 +45,6 @@ You can configure the end points via the `ai-features.openAiCustom.customOpenAiM
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/ai-terminal/README.md b/packages/ai-terminal/README.md
index 9d172389e7b14..09593e01a167c 100644
--- a/packages/ai-terminal/README.md
+++ b/packages/ai-terminal/README.md
@@ -17,15 +17,15 @@ The overlay can be used to ask a dedicated `TerminalAgent` for suggestions of te
 
 ## Additional Information
 
--   [Theia - GitHub](https://github.com/eclipse-theia/theia)
--   [Theia - Website](https://theia-ide.org/)
+- [Theia - GitHub](https://github.com/eclipse-theia/theia)
+- [Theia - Website](https://theia-ide.org/)
 
 ## License
 
--   [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
--   [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
+- [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
+- [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
 
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/ai-workspace-agent/README.md b/packages/ai-workspace-agent/README.md
index 947501725540d..9089f9da9fba5 100644
--- a/packages/ai-workspace-agent/README.md
+++ b/packages/ai-workspace-agent/README.md
@@ -26,5 +26,6 @@ The agent is able to inspect the current files of the workspace, including their
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/bulk-edit/README.md b/packages/bulk-edit/README.md
index e6af21c35a6f2..8930c10106c8d 100644
--- a/packages/bulk-edit/README.md
+++ b/packages/bulk-edit/README.md
@@ -26,5 +26,6 @@ The `@theia/bulk-edit` extension contributes a `Refactor Preview` widget to the
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/callhierarchy/README.md b/packages/callhierarchy/README.md
index 2ff3a1b9b2b93..4179159699fb1 100644
--- a/packages/callhierarchy/README.md
+++ b/packages/callhierarchy/README.md
@@ -26,5 +26,6 @@ The `@theia/callhierarchy` extension contributes a `call hierarchy` view which d
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/collaboration/README.md b/packages/collaboration/README.md
index f97352acc298f..4a32380fe6b79 100644
--- a/packages/collaboration/README.md
+++ b/packages/collaboration/README.md
@@ -29,5 +29,6 @@ Note that the project is still in a beta phase and can be subject to unexpected
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/console/README.md b/packages/console/README.md
index 6aa0c1b885169..38a43fa88b5bd 100644
--- a/packages/console/README.md
+++ b/packages/console/README.md
@@ -26,5 +26,6 @@ The `@theia/console` extension contributes a `console` widget which is used to e
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/core/README.md b/packages/core/README.md
index 2f598c6e398a9..b38e87379915d 100644
--- a/packages/core/README.md
+++ b/packages/core/README.md
@@ -14,6 +14,7 @@
 
 The `@theia/core` extension is the main extension for all Theia-based applications, and provides the main framework for all dependent extensions.
 The extension provides the base APIs for all Theia-based applications, including:
+
 - Application APIs
 - Shell APIs
 - Base Widgets
@@ -38,6 +39,7 @@ A Theia extension is a node package declaring `theiaExtensions` property in `pac
 ```
 
 Each extension can consist of the following modules:
+
 - `frontend` is used in the browser env and as well in the electron if `frontendElectron` is not provided
 - `frontendElectron` is used in the electron env
 - `backend` is used in the node env and as well in the electron env if `backendElectron` is not provided
@@ -69,44 +71,44 @@ export class SomeClass {
 ## Re-Exports
 
 - `@theia/core/electron-shared/...`
-    - `native-keymap` (from [`native-keymap@^2.2.1`](https://www.npmjs.com/package/native-keymap))
-    - `electron` (from [`electron@30.1.2`](https://www.npmjs.com/package/electron/v/30.1.2))
-    - `electron-store` (from [`electron-store@^8.0.0`](https://www.npmjs.com/package/electron-store))
-    - `fix-path` (from [`fix-path@^3.0.0`](https://www.npmjs.com/package/fix-path))
+  - `native-keymap` (from [`native-keymap@^2.2.1`](https://www.npmjs.com/package/native-keymap))
+  - `electron` (from [`electron@30.1.2`](https://www.npmjs.com/package/electron/v/30.1.2))
+  - `electron-store` (from [`electron-store@^8.0.0`](https://www.npmjs.com/package/electron-store))
+  - `fix-path` (from [`fix-path@^3.0.0`](https://www.npmjs.com/package/fix-path))
 - `@theia/core/shared/...`
-    - `@phosphor/algorithm` (from [`@phosphor/algorithm@1`](https://www.npmjs.com/package/@phosphor/algorithm))
-    - `@phosphor/commands` (from [`@phosphor/commands@1`](https://www.npmjs.com/package/@phosphor/commands))
-    - `@phosphor/coreutils` (from [`@phosphor/coreutils@1`](https://www.npmjs.com/package/@phosphor/coreutils))
-    - `@phosphor/domutils` (from [`@phosphor/domutils@1`](https://www.npmjs.com/package/@phosphor/domutils))
-    - `@phosphor/dragdrop` (from [`@phosphor/dragdrop@1`](https://www.npmjs.com/package/@phosphor/dragdrop))
-    - `@phosphor/messaging` (from [`@phosphor/messaging@1`](https://www.npmjs.com/package/@phosphor/messaging))
-    - `@phosphor/properties` (from [`@phosphor/properties@1`](https://www.npmjs.com/package/@phosphor/properties))
-    - `@phosphor/signaling` (from [`@phosphor/signaling@1`](https://www.npmjs.com/package/@phosphor/signaling))
-    - `@phosphor/virtualdom` (from [`@phosphor/virtualdom@1`](https://www.npmjs.com/package/@phosphor/virtualdom))
-    - `@phosphor/widgets` (from [`@phosphor/widgets@1`](https://www.npmjs.com/package/@phosphor/widgets))
-    - `@theia/application-package` (from [`@theia/application-package@1.56.0`](https://www.npmjs.com/package/@theia/application-package/v/1.56.0))
-    - `@theia/application-package/lib/api` (from [`@theia/application-package@1.56.0`](https://www.npmjs.com/package/@theia/application-package/v/1.56.0))
-    - `@theia/application-package/lib/environment` (from [`@theia/application-package@1.56.0`](https://www.npmjs.com/package/@theia/application-package/v/1.56.0))
-    - `@theia/request` (from [`@theia/request@1.56.0`](https://www.npmjs.com/package/@theia/request/v/1.56.0))
-    - `@theia/request/lib/proxy` (from [`@theia/request@1.56.0`](https://www.npmjs.com/package/@theia/request/v/1.56.0))
-    - `@theia/request/lib/node-request-service` (from [`@theia/request@1.56.0`](https://www.npmjs.com/package/@theia/request/v/1.56.0))
-    - `fs-extra` (from [`fs-extra@^4.0.2`](https://www.npmjs.com/package/fs-extra))
-    - `fuzzy` (from [`fuzzy@^0.1.3`](https://www.npmjs.com/package/fuzzy))
-    - `inversify` (from [`inversify@^6.1.3`](https://www.npmjs.com/package/inversify))
-    - `react-dom` (from [`react-dom@^18.2.0`](https://www.npmjs.com/package/react-dom))
-    - `react-dom/client` (from [`react-dom@^18.2.0`](https://www.npmjs.com/package/react-dom))
-    - `react-virtuoso` (from [`react-virtuoso@^2.17.0`](https://www.npmjs.com/package/react-virtuoso))
-    - `vscode-languageserver-protocol` (from [`vscode-languageserver-protocol@^3.17.2`](https://www.npmjs.com/package/vscode-languageserver-protocol))
-    - `vscode-uri` (from [`vscode-uri@^2.1.1`](https://www.npmjs.com/package/vscode-uri))
-    - `@parcel/watcher` (from [`@parcel/watcher@^2.5.0`](https://www.npmjs.com/package/@parcel/watcher))
-    - `dompurify` (from [`dompurify@^2.2.9`](https://www.npmjs.com/package/dompurify))
-    - `express` (from [`express@^4.21.0`](https://www.npmjs.com/package/express))
-    - `lodash.debounce` (from [`lodash.debounce@^4.0.8`](https://www.npmjs.com/package/lodash.debounce))
-    - `lodash.throttle` (from [`lodash.throttle@^4.1.1`](https://www.npmjs.com/package/lodash.throttle))
-    - `markdown-it` (from [`markdown-it@^12.3.2`](https://www.npmjs.com/package/markdown-it))
-    - `react` (from [`react@^18.2.0`](https://www.npmjs.com/package/react))
-    - `ws` (from [`ws@^8.17.1`](https://www.npmjs.com/package/ws))
-    - `yargs` (from [`yargs@^15.3.1`](https://www.npmjs.com/package/yargs))
+  - `@phosphor/algorithm` (from [`@phosphor/algorithm@1`](https://www.npmjs.com/package/@phosphor/algorithm))
+  - `@phosphor/commands` (from [`@phosphor/commands@1`](https://www.npmjs.com/package/@phosphor/commands))
+  - `@phosphor/coreutils` (from [`@phosphor/coreutils@1`](https://www.npmjs.com/package/@phosphor/coreutils))
+  - `@phosphor/domutils` (from [`@phosphor/domutils@1`](https://www.npmjs.com/package/@phosphor/domutils))
+  - `@phosphor/dragdrop` (from [`@phosphor/dragdrop@1`](https://www.npmjs.com/package/@phosphor/dragdrop))
+  - `@phosphor/messaging` (from [`@phosphor/messaging@1`](https://www.npmjs.com/package/@phosphor/messaging))
+  - `@phosphor/properties` (from [`@phosphor/properties@1`](https://www.npmjs.com/package/@phosphor/properties))
+  - `@phosphor/signaling` (from [`@phosphor/signaling@1`](https://www.npmjs.com/package/@phosphor/signaling))
+  - `@phosphor/virtualdom` (from [`@phosphor/virtualdom@1`](https://www.npmjs.com/package/@phosphor/virtualdom))
+  - `@phosphor/widgets` (from [`@phosphor/widgets@1`](https://www.npmjs.com/package/@phosphor/widgets))
+  - `@theia/application-package` (from [`@theia/application-package@1.56.0`](https://www.npmjs.com/package/@theia/application-package/v/1.56.0))
+  - `@theia/application-package/lib/api` (from [`@theia/application-package@1.56.0`](https://www.npmjs.com/package/@theia/application-package/v/1.56.0))
+  - `@theia/application-package/lib/environment` (from [`@theia/application-package@1.56.0`](https://www.npmjs.com/package/@theia/application-package/v/1.56.0))
+  - `@theia/request` (from [`@theia/request@1.56.0`](https://www.npmjs.com/package/@theia/request/v/1.56.0))
+  - `@theia/request/lib/proxy` (from [`@theia/request@1.56.0`](https://www.npmjs.com/package/@theia/request/v/1.56.0))
+  - `@theia/request/lib/node-request-service` (from [`@theia/request@1.56.0`](https://www.npmjs.com/package/@theia/request/v/1.56.0))
+  - `fs-extra` (from [`fs-extra@^4.0.2`](https://www.npmjs.com/package/fs-extra))
+  - `fuzzy` (from [`fuzzy@^0.1.3`](https://www.npmjs.com/package/fuzzy))
+  - `inversify` (from [`inversify@^6.1.3`](https://www.npmjs.com/package/inversify))
+  - `react-dom` (from [`react-dom@^18.2.0`](https://www.npmjs.com/package/react-dom))
+  - `react-dom/client` (from [`react-dom@^18.2.0`](https://www.npmjs.com/package/react-dom))
+  - `react-virtuoso` (from [`react-virtuoso@^2.17.0`](https://www.npmjs.com/package/react-virtuoso))
+  - `vscode-languageserver-protocol` (from [`vscode-languageserver-protocol@^3.17.2`](https://www.npmjs.com/package/vscode-languageserver-protocol))
+  - `vscode-uri` (from [`vscode-uri@^2.1.1`](https://www.npmjs.com/package/vscode-uri))
+  - `@parcel/watcher` (from [`@parcel/watcher@^2.5.0`](https://www.npmjs.com/package/@parcel/watcher))
+  - `dompurify` (from [`dompurify@^2.2.9`](https://www.npmjs.com/package/dompurify))
+  - `express` (from [`express@^4.21.0`](https://www.npmjs.com/package/express))
+  - `lodash.debounce` (from [`lodash.debounce@^4.0.8`](https://www.npmjs.com/package/lodash.debounce))
+  - `lodash.throttle` (from [`lodash.throttle@^4.1.1`](https://www.npmjs.com/package/lodash.throttle))
+  - `markdown-it` (from [`markdown-it@^12.3.2`](https://www.npmjs.com/package/markdown-it))
+  - `react` (from [`react@^18.2.0`](https://www.npmjs.com/package/react))
+  - `ws` (from [`ws@^8.17.1`](https://www.npmjs.com/package/ws))
+  - `yargs` (from [`yargs@^15.3.1`](https://www.npmjs.com/package/yargs))
 
 ## Logging Configuration
 
@@ -141,6 +143,7 @@ comes from, which can give an idea, without having to read the code:
 root INFO [parcel-watcher: 10734] Started watching: /Users/captain.future/git/theia/CONTRIBUTING.md
 ^^^^ ^^^^  ^^^^^^^^^^^^^^^^^^^^^
 ```
+
 Where `root` is the name of the logger and `INFO` is the log level. These are optionally followed by the name of a child process and the process ID.
 
 ## Environment Variables
@@ -155,7 +158,7 @@ Where `root` is the name of the logger and `INFO` is the log level. These are op
 - `FRONTEND_CONNECTION_TIMEOUT`
   - The duration in milliseconds during which the backend keeps the connection contexts for the frontend to reconnect.
   - This duration defaults to '0' if not set.
-  - If set to negative number, the backend will never close the connection.    
+  - If set to negative number, the backend will never close the connection.
 
 ## Additional Information
 
@@ -169,5 +172,6 @@ Where `root` is the name of the logger and `INFO` is the log level. These are op
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/core/README_TEMPLATE.md b/packages/core/README_TEMPLATE.md
index 76a0887aef570..da0265b1c9576 100644
--- a/packages/core/README_TEMPLATE.md
+++ b/packages/core/README_TEMPLATE.md
@@ -14,6 +14,7 @@
 
 The `@theia/core` extension is the main extension for all Theia-based applications, and provides the main framework for all dependent extensions.
 The extension provides the base APIs for all Theia-based applications, including:
+
 - Application APIs
 - Shell APIs
 - Base Widgets
@@ -38,6 +39,7 @@ A Theia extension is a node package declaring `theiaExtensions` property in `pac
 ```
 
 Each extension can consist of the following modules:
+
 - `frontend` is used in the browser env and as well in the electron if `frontendElectron` is not provided
 - `frontendElectron` is used in the electron env
 - `backend` is used in the node env and as well in the electron env if `backendElectron` is not provided
@@ -72,7 +74,7 @@ export class SomeClass {
 - `@theia/core/{{&directory}}/...`
     {{#packages}}
     {{#modules}}
-    - `{{&moduleName}}` (from [`{{&packageName}}@{{&versionRange}}`]({{&npmUrl}}))
+  - `{{&moduleName}}` (from [`{{&packageName}}@{{&versionRange}}`]({{&npmUrl}}))
     {{/modules}}
     {{/packages}}
 {{/reExportsDirectories}}
@@ -110,6 +112,7 @@ comes from, which can give an idea, without having to read the code:
 root INFO [parcel-watcher: 10734] Started watching: /Users/captain.future/git/theia/CONTRIBUTING.md
 ^^^^ ^^^^  ^^^^^^^^^^^^^^^^^^^^^
 ```
+
 Where `root` is the name of the logger and `INFO` is the log level. These are optionally followed by the name of a child process and the process ID.
 
 ## Environment Variables
@@ -124,7 +127,7 @@ Where `root` is the name of the logger and `INFO` is the log level. These are op
 - `FRONTEND_CONNECTION_TIMEOUT`
   - The duration in milliseconds during which the backend keeps the connection contexts for the frontend to reconnect.
   - This duration defaults to '0' if not set.
-  - If set to negative number, the backend will never close the connection.    
+  - If set to negative number, the backend will never close the connection.
 
 ## Additional Information
 
@@ -138,5 +141,6 @@ Where `root` is the name of the logger and `INFO` is the log level. These are op
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/debug/README.md b/packages/debug/README.md
index 6afe8b14f4fa8..4a46635e0fa6d 100644
--- a/packages/debug/README.md
+++ b/packages/debug/README.md
@@ -19,6 +19,7 @@ In most cases the default behavior of the `DebugSession` is enough. But it is po
 ### Debug Session life-cycle API
 
 `DebugSession` life-cycle is controlled and can be tracked as follows:
+
 * An `onDidPreCreateDebugSession` event indicates that a debug session is going to be created.
 * An `onDidCreateDebugSession` event indicates that a debug session has been created.
 * An `onDidDestroyDebugSession` event indicates that a debug session has terminated.
@@ -40,23 +41,25 @@ At the back-end we start a debug adapter using `DebugAdapterFactory` and then a
 
 ## Additional Information
 
-- [API documentation for `@theia/debug`](https://eclipse-theia.github.io/theia/docs/next/modules/debug.html)
-- [Theia - GitHub](https://github.com/eclipse-theia/theia)
-- [Theia - Website](https://theia-ide.org/)
-- [Debug Adapter Protocol](https://github.com/Microsoft/vscode-debugadapter-node/blob/master/protocol/src/debugProtocol.ts)
-- [VS Code debug API](https://code.visualstudio.com/docs/extensionAPI/api-debugging)
-- [Debug adapter example for VS Code](https://code.visualstudio.com/docs/extensions/example-debuggers)
+* [API documentation for `@theia/debug`](https://eclipse-theia.github.io/theia/docs/next/modules/debug.html)
+* [Theia - GitHub](https://github.com/eclipse-theia/theia)
+* [Theia - Website](https://theia-ide.org/)
+* [Debug Adapter Protocol](https://github.com/Microsoft/vscode-debugadapter-node/blob/master/protocol/src/debugProtocol.ts)
+* [VS Code debug API](https://code.visualstudio.com/docs/extensionAPI/api-debugging)
+* [Debug adapter example for VS Code](https://code.visualstudio.com/docs/extensions/example-debuggers)
 
 ## Debug adapter implementations for VS Code
+
 * [Node Debugger](https://github.com/microsoft/vscode-node-debug)
 * [Node Debugger 2](https://github.com/microsoft/vscode-node-debug2)
 * [Java Debugger](https://github.com/Microsoft/vscode-java-debug)
 
 ## License
 
-- [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
-- [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
+* [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
+* [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/dev-container/README.md b/packages/dev-container/README.md
index b9ce2d06af2e5..9f5e7f9d6011e 100644
--- a/packages/dev-container/README.md
+++ b/packages/dev-container/README.md
@@ -17,6 +17,7 @@ The `@theia/dev-container` extension provides functionality to create, start and
 
 The full devcontainer.json Schema can be found [here](https://containers.dev/implementors/json_reference/).
 Currently only a small number of configuration file properties are implemented. Those include the following:
+
 - name
 - Image
 - dockerfile/build.dockerfile
@@ -25,8 +26,7 @@ Currently only a small number of configuration file properties are implemented.
 - forwardPorts
 - mounts
 
-see `main-container-creation-contributions.ts` for how to implementations or how to implement additional ones. 
-
+see `main-container-creation-contributions.ts` for how to implementations or how to implement additional ones.
 
 ## Additional Information
 
@@ -39,5 +39,6 @@ see `main-container-creation-contributions.ts` for how to implementations or how
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/editor-preview/README.md b/packages/editor-preview/README.md
index b7460e3574b73..aa0ae67a4a2d2 100644
--- a/packages/editor-preview/README.md
+++ b/packages/editor-preview/README.md
@@ -13,27 +13,32 @@
 ## Description
 
 The `@theia/editor-preview` extension contributes the preview editor which  supports the same functionality as a regular editor widget with the exception:
+
 - if a preview editor has not "transitioned to a permanent editor" at the time an additional request to
 preview a file is received, instead of opening a new editor, it will display the contents of the
 newly requested file.
 
 Events that will transition the preview to a permanent editor are as follows:
-* Modifying file contents being previewed
-* Double clicking the preview tab
-* Performing a drag/drop operation of the editor preview tab resulting in the tab being moved.
-* Issuing a request to open the file being previewed (e.g. double clicking the file in the
+
+- Modifying file contents being previewed
+- Double clicking the preview tab
+- Performing a drag/drop operation of the editor preview tab resulting in the tab being moved.
+- Issuing a request to open the file being previewed (e.g. double clicking the file in the
 navigator)
 
 The preview editor is enabled by default when the extension is included in a Theia application, but
 may be disabled by modifying the preference:
+
 ```json
 editor.enablePreview
 ```
 
 In addition to this value, the preference:
+
 ```json
 list.openMode
 ```
+
 must be set to "singleClick" to enable opening files in preview mode.
 
 ## Additional Information
@@ -48,5 +53,6 @@ must be set to "singleClick" to enable opening files in preview mode.
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/editor/README.md b/packages/editor/README.md
index 12dfc6686039b..880a7e8722524 100644
--- a/packages/editor/README.md
+++ b/packages/editor/README.md
@@ -26,5 +26,6 @@ The `@theia/editor` extension contributed functionality such as the `editor` wid
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/electron/README.md b/packages/electron/README.md
index becdec4f58c66..da669f1164d76 100644
--- a/packages/electron/README.md
+++ b/packages/electron/README.md
@@ -17,10 +17,10 @@ The `@theia/electron` extension bundles all Electron-specific dependencies and c
 ## Re-Exports
 
 - `@theia/electron/shared/...`
-    - `native-keymap` (from [`native-keymap@^2.2.1`](https://www.npmjs.com/package/native-keymap))
-    - `electron` (from [`electron@30.1.2`](https://www.npmjs.com/package/electron/v/30.1.2))
-    - `electron-store` (from [`electron-store@^8.0.0`](https://www.npmjs.com/package/electron-store))
-    - `fix-path` (from [`fix-path@^3.0.0`](https://www.npmjs.com/package/fix-path))
+  - `native-keymap` (from [`native-keymap@^2.2.1`](https://www.npmjs.com/package/native-keymap))
+  - `electron` (from [`electron@30.1.2`](https://www.npmjs.com/package/electron/v/30.1.2))
+  - `electron-store` (from [`electron-store@^8.0.0`](https://www.npmjs.com/package/electron-store))
+  - `fix-path` (from [`fix-path@^3.0.0`](https://www.npmjs.com/package/fix-path))
 
 ## Additional Information
 
@@ -34,5 +34,6 @@ The `@theia/electron` extension bundles all Electron-specific dependencies and c
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/electron/README_TEMPLATE.md b/packages/electron/README_TEMPLATE.md
index 4007040b26874..c8d65acca8bd7 100644
--- a/packages/electron/README_TEMPLATE.md
+++ b/packages/electron/README_TEMPLATE.md
@@ -20,7 +20,7 @@ The `@theia/electron` extension bundles all Electron-specific dependencies and c
 - `@theia/electron/{{&directory}}/...`
     {{#packages}}
     {{#modules}}
-    - `{{&moduleName}}` (from [`{{&packageName}}@{{&versionRange}}`]({{&npmUrl}}))
+  - `{{&moduleName}}` (from [`{{&packageName}}@{{&versionRange}}`]({{&npmUrl}}))
     {{/modules}}
     {{/packages}}
 {{/reExportsDirectories}}
@@ -37,5 +37,6 @@ The `@theia/electron` extension bundles all Electron-specific dependencies and c
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/external-terminal/README.md b/packages/external-terminal/README.md
index bd6a4f7387057..7655070992f50 100644
--- a/packages/external-terminal/README.md
+++ b/packages/external-terminal/README.md
@@ -37,10 +37,10 @@ by identifying certain environment variables. The extension also contributes pre
 
 ## License
 
--   [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
--   [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
+- [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
+- [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
 
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/file-search/README.md b/packages/file-search/README.md
index 8b1ca84e2ea16..cfa5422ec00a1 100644
--- a/packages/file-search/README.md
+++ b/packages/file-search/README.md
@@ -26,5 +26,6 @@ The `@theia/file-search` extension adds the command and ability to quickly open
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/filesystem/README.md b/packages/filesystem/README.md
index 28dde5c42ccb3..f3cca4838c071 100644
--- a/packages/filesystem/README.md
+++ b/packages/filesystem/README.md
@@ -26,5 +26,6 @@ The `@theia/filesystem` extension provides functionality to interact with the fi
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/filesystem/src/common/download/README.md b/packages/filesystem/src/common/download/README.md
index 98cc1476df406..f34eb2d7a436c 100644
--- a/packages/filesystem/src/common/download/README.md
+++ b/packages/filesystem/src/common/download/README.md
@@ -3,6 +3,7 @@
 Provides the file download contribution to the `Files` navigator.
 
 Supports single and multi file downloads.
+
  1. A single file will be downloaded as is.
  2. Folders will be downloaded az tar archives.
  3. When downloading multiple files, the name of the closest common parent directory will be used for the archive.
@@ -10,10 +11,11 @@ Supports single and multi file downloads.
 
 ### REST API
 
- - To download a single file or folder use the following endpoint: `GET /files/?uri=/encoded/file/uri/to/the/resource`.
-   - Example: `curl -X GET http://localhost:3000/files/?uri=file:///Users/akos.kitta/git/theia/package.json`.
+- To download a single file or folder use the following endpoint: `GET /files/?uri=/encoded/file/uri/to/the/resource`.
+  - Example: `curl -X GET http://localhost:3000/files/?uri=file:///Users/akos.kitta/git/theia/package.json`.
+
+- To download multiple files (from the same folder) use the `PUT /files/` endpoint with the `application/json` content type header and the following body format:
 
- - To download multiple files (from the same folder) use the `PUT /files/` endpoint with the `application/json` content type header and the following body format:
     ```json
     {
         "uri": [
@@ -22,10 +24,12 @@ Supports single and multi file downloads.
         ]
     }
     ```
+
    ```
    curl -X PUT -H "Content-Type: application/json" -d '{ "uris": ["file:///Users/akos.kitta/git/theia/package.json", "file:///Users/akos.kitta/git/theia/README.md"] }' http://localhost:3000/files/
    ```
 
 ## License
+
 - [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
-- [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
\ No newline at end of file
+- [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
diff --git a/packages/getting-started/README.md b/packages/getting-started/README.md
index 0ec03d4d3b1b3..e503abd673215 100644
--- a/packages/getting-started/README.md
+++ b/packages/getting-started/README.md
@@ -16,6 +16,7 @@ The `@theia/getting-started` extension contributes a default `getting-started` w
 opening the application without any workspace present or if the widget is explicitly opened (through the menu or command).
 
 The `getting-started` widget provides useful commands and functionality for quickly getting up to speed with the application. For example:
+
 - `open commands`: commands which are used to open files, folders, and workspaces quickly.
 - `recent workspaces`: recently used workspaces are listed for easy and quick access.
 - `settings commands`: commands which are used to open the preferences and keyboard shortcuts widgets.
@@ -33,5 +34,6 @@ The `getting-started` widget provides useful commands and functionality for quic
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/git/README.md b/packages/git/README.md
index d8777bc008678..449d2128433c5 100644
--- a/packages/git/README.md
+++ b/packages/git/README.md
@@ -14,6 +14,7 @@
 
 The `@theia/git` extension contributes the ability to interact with Git from the user's system.
 The Git SCM provider contributes:
+
 - `blame`
 - `diff`
 - `dirty-diff`
@@ -32,5 +33,6 @@ The Git SCM provider contributes:
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/keymaps/README.md b/packages/keymaps/README.md
index 9c126ba2a3acd..6c1195dd0916e 100644
--- a/packages/keymaps/README.md
+++ b/packages/keymaps/README.md
@@ -25,6 +25,7 @@ Example of a valid `keymaps.json` file
     }
 ]
 ```
+
  where `command` is a unique command id and keybinding is a valid `keybinding`. There's also an optional `context` property that can be specified (which is also a unique string for a context id).
 
 ## Supported Keys
@@ -42,8 +43,9 @@ If unsure you can always look at the framework's [supported keys](https://eclips
 ## Key Sequences
 
 Key sequences like: `ctrl+x ctrl+a` or `ctrl+a b c` are supported.  With the following limitations:
- - If the key sequence exceeds 1 key chord it won't show in the electron menu.
- - If the key sequence exceeds 2 key chords it won't show in the command palette.
+
+- If the key sequence exceeds 1 key chord it won't show in the electron menu.
+- If the key sequence exceeds 2 key chords it won't show in the command palette.
 
 ## Additional Information
 
@@ -57,5 +59,6 @@ Key sequences like: `ctrl+x ctrl+a` or `ctrl+a b c` are supported.  With the fol
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/markers/README.md b/packages/markers/README.md
index b85dad791899e..7a91b0d41e3a2 100644
--- a/packages/markers/README.md
+++ b/packages/markers/README.md
@@ -14,6 +14,7 @@
 
 The `@theia/markers` adds support for file markers (diagnostic markers (`errors`, `warnings`, `infos`, `hint`)) for a given file.
 The extension contributes, the following:
+
 - `problems view`: a dedicated view to viewing diagnostic markers contributed by language-servers, linters, task problem matchers for the workspace
 - `marker decoration`: ability to decorate different components of the application based on markers (ex: file explorer)
 
@@ -29,5 +30,6 @@ The extension contributes, the following:
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/memory-inspector/README.md b/packages/memory-inspector/README.md
index e9f0478def703..7ddd99a33e6f6 100644
--- a/packages/memory-inspector/README.md
+++ b/packages/memory-inspector/README.md
@@ -54,7 +54,6 @@ method of that service allows you to change what kind of widget is instantiated
 [`MemoryProviderService`](./src/browser/memory-provider/memory-provider-service.ts), which delegates to implementations `MemoryProvider` interface
 that are bound as `MemoryProvider` contributions.
 
-
 ## Additional Information
 
 - [API documentation for `@theia/getting-started`](https://eclipse-theia.github.io/theia/docs/next/modules/getting_started.html)
@@ -67,5 +66,6 @@ that are bound as `MemoryProvider` contributions.
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/messages/README.md b/packages/messages/README.md
index 16f4a839cb625..25667e5912d88 100644
--- a/packages/messages/README.md
+++ b/packages/messages/README.md
@@ -26,5 +26,6 @@ The `@theia/messages` extension provides the ability to display user notificatio
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/metrics/README.md b/packages/metrics/README.md
index 7f324192bccb0..2f606e2371506 100644
--- a/packages/metrics/README.md
+++ b/packages/metrics/README.md
@@ -26,5 +26,6 @@ The `@theia/metrics` extension provides metrics using the [Prometheus](https://p
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/mini-browser/README.md b/packages/mini-browser/README.md
index faa2bd6eff656..500009f3f2a07 100644
--- a/packages/mini-browser/README.md
+++ b/packages/mini-browser/README.md
@@ -41,5 +41,6 @@ The `@theia/mini-browser` extension provides a browser widget with the correspon
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/monaco/README.md b/packages/monaco/README.md
index d9d4f76042e78..8a1865f02a6a7 100644
--- a/packages/monaco/README.md
+++ b/packages/monaco/README.md
@@ -14,6 +14,7 @@
 
 The `@theia/monaco` extension contributes the integration of the [monaco-editor](https://microsoft.github.io/monaco-editor/index.html).\
 This includes:
+
 - full-feature code editor
 - diff-editor
 - code snippets
@@ -28,22 +29,28 @@ process, the steps for undertaking a Monaco uplift are outlined here.
 ### Setting up the VSCode side
 
 1. Clone the VSCode repo and make sure you have the following remotes:
- - https://github.com/microsoft/vscode.git - the official VSCode repo.
- - https://github.com/theia-ide/vscode.git - Theia's fork.
+
+- <https://github.com/microsoft/vscode.git> - the official VSCode repo.
+- <https://github.com/theia-ide/vscode.git> - Theia's fork.
+
 2. Find the latest release tag in the official VSCode repo, and the most recent uplift branch in the Theia fork.
+
  > At the time of this writing the latest release tag is `1.67.2`, and the uplift branch is `monaco-uplift-2022-6`
+
 3. Check out the release tag, cherry pick the tip of the uplift branch, and resolve any conflicts.
+
  > As you resolve conflicts and make changes to the VSCode repo, make sure you end up with a single commit on the uplift branch to make it easier for the next person to rebase.
+
 4. Try to build. At the moment, this means running `yarn` and `yarn run gulp editor-distro`.
 5. Fix any build errors that arise.
 6. Change the version in `build/monaco/package.json`
 
 #### Current State
 
- - build/gulpfile.editor.js: various changes to modify the treeshaking and output destinations.
- - build/lib/standalone.js/ts: changes to output sourcemaps etc. One small change to fix a build error due to having a directory named `model` and a file named `model.ts` in the same folder.
- - src/vs/base/browser/dompurify/dompurify.js changes for CommonJS rather than ESM
- - src/vs/base/common/marked/marked.js changes for CommonJS rather than ESM
+- build/gulpfile.editor.js: various changes to modify the treeshaking and output destinations.
+- build/lib/standalone.js/ts: changes to output sourcemaps etc. One small change to fix a build error due to having a directory named `model` and a file named `model.ts` in the same folder.
+- src/vs/base/browser/dompurify/dompurify.js changes for CommonJS rather than ESM
+- src/vs/base/common/marked/marked.js changes for CommonJS rather than ESM
 
 ### Setting up the Theia side
 
@@ -51,15 +58,21 @@ For initial testing, it's easier to point dependencies to your local VSCode.
 
 1. Having built `monaco-editor-core` using the steps [above](#setting-up-the-vscode-side).
 2. Find all references to `@theia/monaco-editor-core` in `package.json`s and replace their version with `"link:<path to your local build of monaco-editor-core>"`.
-> Using `link:` means that if you subsequently make changes on the VSCode side, you only need to rebuild VSCode and then rebuild Theia to see the effects. 
+
+> Using `link:` means that if you subsequently make changes on the VSCode side, you only need to rebuild VSCode and then rebuild Theia to see the effects.
+
 3. Delete your `node_modules` and `yarn` and build Theia.
 4. Fix any build errors.
 5. Uncomment the `bindMonacoPreferenceExtractor` function in `examples/api-samples/src/browser/monaco-editor-preferences/monaco-editor-preference-extractor.ts` and run the commands there. Fix the `EditorGeneratedPreferenceSchema` as necessary, and add or remove validations from the `MonacoFrontendApplicationContribution` as appropriate.
 6. Look for comments that indicate forced types or other code smells that would prevent a build error from being thrown where it should be thrown and check that the assertion still applies.
+
 > If you add these, mark them with @monaco-uplift - that'll make them easier to find in the future. Better: if you can remove them, do! Typically, the cause is mixing imports from
 private API and public API. Often public API fails to satisfy private declarations.
+
 7. Test the application thoroughly - make sure everything's still working.
+
 > It may also be necessary to update our various `vscode` dependencies to match the current state of VSCode. It may not be necessary to upgrade all (or any) of these to successfully adopt a new Monaco version, but if something is misbehaving inexplicably, checking dependencies is a reasonable place to start. Check on:
+>
 > - `vscode-debugprotocol`
 > - `vscode-languageserver-protocol`
 > - `vscode-oniguruma`
@@ -74,7 +87,6 @@ Once you believe that everything is in working order, you'll need to publish the
 [here](https://github.com/theia-ide/vscode/wiki/Publish-%60@theia-monaco-editor-core%60). Once the package is published, point your `package.json`s at the testing version and make
 sure everything still works, then make a PR.
 
-
 ## Additional Information
 
 - [API documentation for `@theia/monaco`](https://eclipse-theia.github.io/theia/docs/next/modules/monaco.html)
@@ -87,14 +99,15 @@ sure everything still works, then make a PR.
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
-"Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
 
+"Theia" is a trademark of the Eclipse Foundation
+<https://www.eclipse.org/theia>
 
 # Theia - Monaco Extension
 
 See [here](https://www.theia-ide.org/doc/index.html) for a detailed documentation.
 
 ## License
+
 - [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
diff --git a/packages/navigator/README.md b/packages/navigator/README.md
index 702406183e946..9f54a30b6c2ac 100644
--- a/packages/navigator/README.md
+++ b/packages/navigator/README.md
@@ -27,5 +27,6 @@ The `file explorer` can be used to easily view, open, and manage the files that
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/notebook/README.md b/packages/notebook/README.md
index 7dd65bc96ec64..090da13262d61 100644
--- a/packages/notebook/README.md
+++ b/packages/notebook/README.md
@@ -26,5 +26,6 @@ The `@theia/notebook` extension contributes functionality for integrated noteboo
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/outline-view/README.md b/packages/outline-view/README.md
index efcec91db5afb..0276a031d28df 100644
--- a/packages/outline-view/README.md
+++ b/packages/outline-view/README.md
@@ -26,5 +26,6 @@ The `@theia/outline-view` extension contributes the code outline tree based on a
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/output/README.md b/packages/output/README.md
index 29f029db710f2..c0e58d467c9be 100644
--- a/packages/output/README.md
+++ b/packages/output/README.md
@@ -29,5 +29,6 @@ and help identify internal operations which a user can act upon if problems occu
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/plugin-dev/README.md b/packages/plugin-dev/README.md
index d00ecc13e103f..611ae6504ca50 100644
--- a/packages/plugin-dev/README.md
+++ b/packages/plugin-dev/README.md
@@ -14,7 +14,6 @@
 
 The `@theia/plugin-dev` extension contributes functionality for the `plugin host`.
 
-
 ## Additional Information
 
 - [API documentation for `@theia/plugin-dev`](https://eclipse-theia.github.io/theia/docs/next/modules/plugin_dev.html)
@@ -27,5 +26,6 @@ The `@theia/plugin-dev` extension contributes functionality for the `plugin host
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/plugin-ext-headless/README.md b/packages/plugin-ext-headless/README.md
index f77c932c07d09..9cd5d4a0acfb1 100644
--- a/packages/plugin-ext-headless/README.md
+++ b/packages/plugin-ext-headless/README.md
@@ -28,5 +28,6 @@ The implementation is derived from the [`@theia/plugin-ext` extension][plugin-ex
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/plugin-ext-vscode/README.md b/packages/plugin-ext-vscode/README.md
index fb3777ddebb90..74fd76bd719f5 100644
--- a/packages/plugin-ext-vscode/README.md
+++ b/packages/plugin-ext-vscode/README.md
@@ -15,7 +15,6 @@
 The `@theia/plugin-ext-vscode` extension contributes functionality to be able to successfully run VS Code extensions in the application.
 The extension is mandatory for any application which requires VS Code extension support.
 
-
 ## Additional Information
 
 - [API documentation for `@theia/plugin-ext-vscode`](https://eclipse-theia.github.io/theia/docs/next/modules/plugin_ext_vscode.html)
@@ -28,5 +27,6 @@ The extension is mandatory for any application which requires VS Code extension
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/plugin-ext/README.md b/packages/plugin-ext/README.md
index 5baa7c2e58283..13d4f63de0577 100644
--- a/packages/plugin-ext/README.md
+++ b/packages/plugin-ext/README.md
@@ -16,7 +16,7 @@ The `@theia/plugin-ext` extension contributes functionality for the `plugin` API
 
 ## Implementation
 
-The implementation is inspired from: https://blog.mattbierner.com/vscode-webview-web-learnings/.
+The implementation is inspired from: <https://blog.mattbierner.com/vscode-webview-web-learnings/>.
 
 ## Environment Variables
 
@@ -50,5 +50,6 @@ The property is used to control whether or not extension-packs and extension-dep
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/plugin-metrics/README.md b/packages/plugin-metrics/README.md
index edc4413bfb896..4128dd2d012cf 100644
--- a/packages/plugin-metrics/README.md
+++ b/packages/plugin-metrics/README.md
@@ -16,13 +16,13 @@ The `@theia/plugin-metrics` extension contributes metrics for plugins in the [Pr
 
 ### What Metrics it Detects
 
-1. Detects errors in languages that are registered directly with monaco (E.g. if an error happens here: https://github.com/microsoft/vscode-extension-samples/blob/master/completions-sample/src/extension.ts#L11 it will be reported).
+1. Detects errors in languages that are registered directly with monaco (E.g. if an error happens here: <https://github.com/microsoft/vscode-extension-samples/blob/master/completions-sample/src/extension.ts#L11> it will be reported).
 
 2. Detects errors that are logged directly to the output channel for a specific vscode extension that uses a language server. These errors can only be reported via their id that is registered with the vscode-languageclient library. E.g. "YAML Support", "XML Support", etc
 
 ### Limitations & Drawbacks
 
-Due to the limitations of the vscode-languageclient library (see https://github.com/microsoft/vscode-languageserver-node/issues/517) we are unable to process errors that come from the language server directly, instead we need to use the output channel. The output channel is great because it allows us to work around limitations of the vscode-languageclient library and still get metrics but it still has some drawbacks:
+Due to the limitations of the vscode-languageclient library (see <https://github.com/microsoft/vscode-languageserver-node/issues/517>) we are unable to process errors that come from the language server directly, instead we need to use the output channel. The output channel is great because it allows us to work around limitations of the vscode-languageclient library and still get metrics but it still has some drawbacks:
 
 1. Every time a language server request is resolved it counts as a success. This is because the vscode-languageclient always sends back a resolved promise even when the promise is actually rejected. The only time you can get an error is by extracting data from the output channel using a regex and connecting it back to the successes that were counted earlier. This has a few consequences:
     1. If the errors logged are not matched by the regex we have no way to know where the error occurred and thus we can't link the error back to a language server method. That means that the metric we created will always show that its working 100% correctly, even though it's not.
@@ -59,5 +59,6 @@ Then, when you load up the /metrics endpoint you will see the new language metri
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/plugin/README.md b/packages/plugin/README.md
index 9fd146b9fe47d..6c7b314696d8e 100644
--- a/packages/plugin/README.md
+++ b/packages/plugin/README.md
@@ -192,6 +192,7 @@ Simple example that show a status bar message with statusBarItem:
         item.text = 'test status bar item';
         item.show();
 ```
+
 #### Output channel API
 
  It is possible to show a container for readonly textual information:
@@ -241,9 +242,10 @@ const terminal = theia.window.createTerminal("Bash terminal", "/bin/bash", ["-l"
 ```
 
 Where are:
- - first argument - terminal's name.
- - second argument - path to the executable shell.
- - third argument - arguments to configure executable shell.
+
+- first argument - terminal's name.
+- second argument - path to the executable shell.
+- third argument - arguments to configure executable shell.
 
 You can create terminal with specific options:
 
@@ -258,10 +260,11 @@ const options: theia.TerminalOptions {
 ```
 
 Where are:
- - "shellPath" - path to the executable shell, for example "/bin/bash", "bash", "sh" or so on.
- - "shellArgs" - shell command arguments, for example without login: "-l". If you defined shell command "/bin/bash" and set up shell arguments "-l" than will be created terminal process with command "/bin/bash -l". And client side will connect to stdin/stdout of this process to interaction with user.
- - "cwd" - current working directory;
- - "env"- environment variables for terminal process, for example TERM - identifier terminal window capabilities.
+
+- "shellPath" - path to the executable shell, for example "/bin/bash", "bash", "sh" or so on.
+- "shellArgs" - shell command arguments, for example without login: "-l". If you defined shell command "/bin/bash" and set up shell arguments "-l" than will be created terminal process with command "/bin/bash -l". And client side will connect to stdin/stdout of this process to interaction with user.
+- "cwd" - current working directory;
+- "env"- environment variables for terminal process, for example TERM - identifier terminal window capabilities.
 
 Function to create new terminal with defined theia.TerminalOptions described above:
 
@@ -288,6 +291,7 @@ terminal.sendText("Hello, Theia!", false);
 ```
 
 Where are:
+
 - first argument - text content.
 - second argument - in case true, terminal will apply new line after the text, otherwise will send only the text.
 
@@ -323,6 +327,7 @@ terminal.processId.then(id => {
 Preference API allows one to read or update User's and Workspace's preferences.
 
 To get preferences:
+
 ```typescript
 // editor preferences
 const preferences = theia.workspace.getConfiguration('editor');
@@ -332,6 +337,7 @@ const fontSize = preferences.get('tabSize');
 ```
 
 To change preference:
+
 ```typescript
 preferences.onDidChangeConfiguration(e => {
     if (e.affectsConfiguration('editor.tabSize')) {
@@ -353,6 +359,7 @@ const diagnostics = theia.languages.getDiagnostics(uriToResource)
 ```
 
 To get all diagnostics use:
+
 ```typescript
 const diagnostics =  theia.languages.getDiagnostics()
 ```
@@ -424,6 +431,7 @@ diagnosticsCollection.forEach((uri, diagnostics) => {
 #### Signature help
 
 To provide signature help form plugin it is required to register provider. For registration 3 items are needed:
+
 - Documents selector to describe for which files it should be applied
 - Handler which will do the work
 - Trigger characters after typing of which the handler should be invoked. Often symbols `(` and `,` are used.
@@ -474,6 +482,7 @@ Example of signature information:
 ```
 
 Note, that:
+
 - `activeSignature` and `activeParameter` are zero based.
 - label is usually full method signature.
 - for documentation fields markdown partially supported (Tags aren't supported).
@@ -762,5 +771,6 @@ function provideRanges(document: theia.TextDocument): theia.ProviderResult<theia
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/preferences/README.md b/packages/preferences/README.md
index 7dd24f962944f..690fe10d36618 100644
--- a/packages/preferences/README.md
+++ b/packages/preferences/README.md
@@ -13,12 +13,14 @@
 ## Description
 
 The `@theia/preferences` extension implements the preferences API defined in `@theia/core`, including the four preference providers:
+
 - `Default` Preference, which serves as default values of preferences,
 - `User` Preference for the user home directory, which has precedence over the default values,
 - `Workspace` Preference for the workspace, which has precedence over User Preference, and
 - `Folder` Preference for the root folder, which has precedence over the Workspace Preference
 
 To set:
+
 - `User` Preferences: Create or edit a `settings.json` under the `.theia` folder located either in the user home.
 - `Workspace` Preference: If one folder is opened as the workspace, create or edit a `settings.json` under the root of the workspace. If a multi-root workspace is opened, create or edit the "settings" property in the workspace file.
 - `Folder` Preferences: Create or edit a `settings.json` under any of the root folders.
@@ -28,10 +30,10 @@ Example of a `settings.json` below:
 ```typescript
 {
     // Enable/Disable the line numbers in the monaco editor
-	"editor.lineNumbers": "off",
+ "editor.lineNumbers": "off",
     // Tab width in the editor
-	"editor.tabSize": 4,
-	"files.watcherExclude": "path/to/file"
+ "editor.tabSize": 4,
+ "files.watcherExclude": "path/to/file"
 }
 ```
 
@@ -42,16 +44,16 @@ Example of a workspace file below:
    "folders": [
       {
          "path": "file:///home/username/helloworld"
-	  },
-	  {
+   },
+   {
          "path": "file:///home/username/dev/byeworld"
       }
    ],
    "settings": {
       // Enable/Disable the line numbers in the monaco editor
-	  "editor.lineNumbers": "off",
+   "editor.lineNumbers": "off",
       // Tab width in the editor
-	  "editor.tabSize": 4,
+   "editor.tabSize": 4,
    }
 }
 ```
@@ -68,14 +70,13 @@ Example of a workspace file below:
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
-"Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
 
+"Theia" is a trademark of the Eclipse Foundation
+<https://www.eclipse.org/theia>
 
 # Theia - Preferences Extension
 
-
-
 ## License
+
 - [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
diff --git a/packages/preview/README.md b/packages/preview/README.md
index c0012f0e3bed4..8bbbd768b020f 100644
--- a/packages/preview/README.md
+++ b/packages/preview/README.md
@@ -41,5 +41,6 @@ bind(PreviewHandler).toService(MyPreviewHandler);
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/process/README.md b/packages/process/README.md
index 11740f87cf320..ee76ea08d2bf5 100644
--- a/packages/process/README.md
+++ b/packages/process/README.md
@@ -26,5 +26,6 @@ The `@theia/process` extension allows the management of processes started with o
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/property-view/README.md b/packages/property-view/README.md
index 46c9c72431c48..fa440c4871d80 100644
--- a/packages/property-view/README.md
+++ b/packages/property-view/README.md
@@ -17,6 +17,7 @@ The `@theia/property-view` extension contributes a generic, global property view
 The property view widget can be opened/toggled either via menu _View->Properties_ or via shortcut <kbd>Shift+Alt+P</kbd>. It is located in the bottom dock area by default.
 
 The following two default content widgets are implemented in this extension:
+
 - EmptyPropertyViewWidget: If no other widget can be provided, a simple message (_No properties available_) is shown.
 - ResourcePropertyViewWidget: Can handle `FileSelection`s and `Navigatable` selections (which provide their resource URI) and displays the general `FileStat` information (e.g. location, name, last modified) in a TreeWidget.
 
@@ -36,9 +37,11 @@ To contribute a specific property view, it is necessary to implement a `Property
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
 
 ## License
+
 - [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
diff --git a/packages/remote/README.md b/packages/remote/README.md
index 48b85b41fd9dd..d75aae8321a6f 100644
--- a/packages/remote/README.md
+++ b/packages/remote/README.md
@@ -58,4 +58,4 @@ Although these backend services live on a different remote system, the frontend
 ## Trademark
 
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/scm-extra/README.md b/packages/scm-extra/README.md
index e48617980eae0..624220eb47658 100644
--- a/packages/scm-extra/README.md
+++ b/packages/scm-extra/README.md
@@ -14,6 +14,7 @@
 
 The `@theia/scm-extra` extension contributes additional functionality compared to the base `@theia/scm` extension.
 This includes:
+
 - `SCM History`: a dedicated view to visualize a repository's commit history.
 
 ## Additional Information
@@ -28,5 +29,6 @@ This includes:
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/scm/README.md b/packages/scm/README.md
index 55816ebebfe02..24026c33e1992 100644
--- a/packages/scm/README.md
+++ b/packages/scm/README.md
@@ -27,5 +27,6 @@ The `@theia/scm` extension adds support for handling multiple source control man
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/search-in-workspace/README.md b/packages/search-in-workspace/README.md
index 4e333d5a4e58b..0358e0c3eb3d8 100644
--- a/packages/search-in-workspace/README.md
+++ b/packages/search-in-workspace/README.md
@@ -17,6 +17,7 @@ The `@theia/search-in-workspace` extension provides the ability to perform searc
 ## Search Widget
 
 The `@theia/search-in-workspace` extension contributes the `Search` widget which is capable of performing different types of searches include the possibility to:
+
 - Perform standard searches
 - Perform searches using regular expressions
 - Perform searches within an `include` list (search for specific types of files (ex: `*.ts`))
@@ -36,5 +37,6 @@ The `@theia/search-in-workspace` extension contributes the `Search` widget which
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/task/README.md b/packages/task/README.md
index 8933041a43dc2..b4568649189b6 100644
--- a/packages/task/README.md
+++ b/packages/task/README.md
@@ -17,6 +17,7 @@ The `@theia/task` extension extension permits executing scripts or binaries in t
 Tasks launch configurations can be defined independently for each workspace, under `.theia/tasks.json`. When present, they are automatically picked-up when a client opens a workspace, and watches for changes. A task can be executed by triggering the "Run Task" command (shortcut F1). A list of known tasks will then be available, one of which can be selected to trigger execution.
 
 Each task configuration looks like this:
+
 ``` json
 {
     "label": "Test task - list workspace files recursively",
@@ -48,6 +49,7 @@ Each task configuration looks like this:
 *args*: a list of strings, each one being one argument to pass to the command.
 
 *options*: the command options used when the command is executed. This is the place to provide the
+
 - *cwd*: the current working directory, in which the task's command will execute. This is the equivalent of doing a "cd" to that directory, on the command-line, before running the command. This can contain the variable *${workspaceFolder}*, which will be replaced at execution time by the path of the current workspace. If left undefined, will by default be set to workspace root.
 - *env*: the environment of the executed program or shell. If omitted the parent process' environment is used.
 - *shell*: configuration of the shell when task type is `shell`, where users can specify the shell to use with *shell*, and the arguments to be passed to the shell executable to run in command mode with *args*.
@@ -61,6 +63,7 @@ By default, *command* and *args* above are used on all platforms. However it's n
 *linux*: if *linux* is defined, its command, command arguments, and options (i.e., *linux.command*, *linux.args*, and *linux.options*) will take precedence over the *command*, *args*, and *options*, when the task is executed on a Linux backend.
 
 Here is a sample tasks.json that can be used to test tasks. Just add this content under the theia source directory, in directory `.theia`:
+
 ``` json
 {
     // Some sample Theia tasks
@@ -145,7 +148,9 @@ Here is a sample tasks.json that can be used to test tasks. Just add this conten
 ```
 
 ## Variables substitution
+
 The variables are supported in the following properties, using `${variableName}` syntax:
+
 - `command`
 - `args`
 - `options.cwd`
@@ -162,15 +167,20 @@ The variables are supported in the following properties, using `${variableName}`
 See [here](https://www.theia-ide.org/doc/index.html) for a detailed documentation.
 
 ## Contribution points
+
 The extension provides contribution points:
+
 - `browser/TaskContribution` - allows an extension to provide its own Task format and/or to provide the Tasks programmatically to the system
+
 ```typescript
 export interface TaskContribution {
     registerResolvers?(resolvers: TaskResolverRegistry): void;
     registerProviders?(providers: TaskProviderRegistry): void;
 }
 ```
+
 - `node/TaskRunnerContribution` - allows an extension to provide its own way of running/killing a Task
+
 ```typescript
 export interface TaskRunnerContribution {
     registerRunner(runners: TaskRunnerRegistry): void;
@@ -189,5 +199,6 @@ export interface TaskRunnerContribution {
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/terminal/README.md b/packages/terminal/README.md
index f8d15ba31d568..3d647c5617c56 100644
--- a/packages/terminal/README.md
+++ b/packages/terminal/README.md
@@ -26,5 +26,6 @@ The `@theia/terminal` extension contributes the ability to spawn integrated term
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/timeline/README.md b/packages/timeline/README.md
index 0f277b97fcace..fa15a80b64ca8 100644
--- a/packages/timeline/README.md
+++ b/packages/timeline/README.md
@@ -26,5 +26,6 @@ The `@theia/timeline` extension adds Timeline view for visualizing time-series e
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/toolbar/README.md b/packages/toolbar/README.md
index 02a015a830f06..d8f2dd2240f8c 100644
--- a/packages/toolbar/README.md
+++ b/packages/toolbar/README.md
@@ -12,7 +12,7 @@
 
 ## Description
 
-The `@theia/toolbar` extension contributes a global toolbar to the application shell. The toolbar supplements the `Command Palette` and allows users to easily add, remove, and rearrange toolbar items to their liking. The toolbar is hidden by default and ships with a default layout which can be overridden by downstream applications. Extenders can also contribute custom widgets to the toolbar through a contribution point. 
+The `@theia/toolbar` extension contributes a global toolbar to the application shell. The toolbar supplements the `Command Palette` and allows users to easily add, remove, and rearrange toolbar items to their liking. The toolbar is hidden by default and ships with a default layout which can be overridden by downstream applications. Extenders can also contribute custom widgets to the toolbar through a contribution point.
 
 ## Additional Information
 
@@ -28,5 +28,6 @@ An example toolbar custom widget and layout override can be found in [here](http
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/typehierarchy/README.md b/packages/typehierarchy/README.md
index f9dfbbadbb0f5..77aad182cf80a 100644
--- a/packages/typehierarchy/README.md
+++ b/packages/typehierarchy/README.md
@@ -26,5 +26,6 @@ The `@theia/typehierarchy` extension includes support for `super` and `subtype`
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/userstorage/README.md b/packages/userstorage/README.md
index 29647b030288c..807c6453705d5 100644
--- a/packages/userstorage/README.md
+++ b/packages/userstorage/README.md
@@ -26,14 +26,13 @@ The `@theia/userstorage` extension provides an API for accessing user storage fi
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
-"Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
 
+"Theia" is a trademark of the Eclipse Foundation
+<https://www.eclipse.org/theia>
 
 # Theia - User Storage Extension
 
-
-
 ## License
+
 - [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
diff --git a/packages/variable-resolver/README.md b/packages/variable-resolver/README.md
index cd022d3c86e13..2247c4573b07e 100644
--- a/packages/variable-resolver/README.md
+++ b/packages/variable-resolver/README.md
@@ -15,8 +15,10 @@
 The `@theia/variable-resolved` extension provides variable substitution mechanism inside of strings using `${variableName}` syntax.
 
 ### Variable Contribution Point
+
 Extension provides a hook that allows any extensions to contribute its own variables.
 Here's the example of contributing two variables:
+
 - `${file}` - returns the name of the file opened in the current editor
 - `${lineNumber}` - returns the current line number in the current file
 
@@ -68,6 +70,7 @@ Note that a Variable is resolved to `MaybePromise<string | undefined>` which mea
 ### Using the Variable Resolver Service
 
 There's the example of how one can use Variable Resolver Service in its own plugin:
+
 ```typescript
 @injectable()
 export class MyService {
@@ -85,6 +88,7 @@ export class MyService {
 ```
 
 If `package.json` file is currently opened and cursor is on line 5 then the following output will be logged to the console:
+
 ```
 cursor is in file package.json on line 5
 ```
@@ -101,14 +105,15 @@ cursor is in file package.json on line 5
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
-"Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
 
+"Theia" is a trademark of the Eclipse Foundation
+<https://www.eclipse.org/theia>
 
 # Theia - Variable Resolver Extension
 
 The extension
 
 ## License
+
 - [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
diff --git a/packages/vsx-registry/README.md b/packages/vsx-registry/README.md
index 4789962d545ee..e4b3f0f258f1d 100644
--- a/packages/vsx-registry/README.md
+++ b/packages/vsx-registry/README.md
@@ -41,5 +41,6 @@ and its `OVSXRouterConfig` configuration.
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/packages/workspace/README.md b/packages/workspace/README.md
index 45816f10208c4..b14319af9a2ea 100644
--- a/packages/workspace/README.md
+++ b/packages/workspace/README.md
@@ -26,5 +26,6 @@ The `@theia/workspace` extension provides functionality and services to handle w
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/sample-plugins/sample-namespace/plugin-gotd/README.md b/sample-plugins/sample-namespace/plugin-gotd/README.md
index f16aeb4a4ca6a..8a2d022a4dd00 100644
--- a/sample-plugins/sample-namespace/plugin-gotd/README.md
+++ b/sample-plugins/sample-namespace/plugin-gotd/README.md
@@ -20,6 +20,7 @@ An example demonstrating three Theia concepts:
 
 Thus this plug-in demonstrates the capability of a VS Code-compatible plugin to provide two distinct backend entry-points for the two different backend contexts.
 As declared in the `package.json` manifest:
+
 - in the headless plugin host, the entry-point script is `headless.js` via the Theia-specific the `"theiaPlugin"` object
 - in the backend plugin host for a frontend connection, the entry-point script is `backend.js` via the VS Code standard `"main"` property
 
@@ -40,5 +41,6 @@ The sample uses the custom `gotd` API to log a greeting upon activation.
 - [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)
 
 ## Trademark
+
 "Theia" is a trademark of the Eclipse Foundation
-https://www.eclipse.org/theia
+<https://www.eclipse.org/theia>
diff --git a/scripts/performance/README.md b/scripts/performance/README.md
index 7fa4a5ae134e7..2e0b7a83eb256 100644
--- a/scripts/performance/README.md
+++ b/scripts/performance/README.md
@@ -21,11 +21,11 @@ The script can be executed using `node browser-performance.js` in this directory
 
 The script accepts the following optional parameters:
 
--   `--name`: Specify a name for the current measurement (default: `Browser Frontend Startup`)
--   `--url`: Point Theia to a url for example for specifying a specific workspace (default: `http://localhost:3000/#/<pathToMeasurementScript>/workspace`)
--   `--folder`: Folder name for the generated tracing files in the `profiles` folder (default: `browser`)
--   `--runs`: Number of runs for the measurement (default: `10`)
--   `--headless`: Boolean, if the tests should be run in headless mode (default: `true`)
+- `--name`: Specify a name for the current measurement (default: `Browser Frontend Startup`)
+- `--url`: Point Theia to a url for example for specifying a specific workspace (default: `http://localhost:3000/#/<pathToMeasurementScript>/workspace`)
+- `--folder`: Folder name for the generated tracing files in the `profiles` folder (default: `browser`)
+- `--runs`: Number of runs for the measurement (default: `10`)
+- `--headless`: Boolean, if the tests should be run in headless mode (default: `true`)
 
 _**Note**: When multiple runs are specified the script will calculate the mean and the standard deviation of all values._
 
@@ -40,8 +40,8 @@ Execute `yarn run performance:startup:electron` in the root directory to execute
 To run the script the Theia Electron example needs to be built. In the root directory:
 
 ```console
-$ yarn
-$ yarn electron build
+yarn
+yarn electron build
 ```
 
 ### Executing the script
@@ -50,11 +50,11 @@ The script can be executed using `node electron-performance.js` in this director
 
 The script accepts the following optional parameters:
 
--   `--name`: Specify a name for the current measurement (default: `Electron Frontend Startup`)
--   `--folder`: Folder name for the generated tracing files in the `profiles` folder (default: `electron`)
--   `--workspace`: Absolute path to a Theia workspace to open (default: an empty workspace folder)
--   `--runs`: Number of runs for the measurement (default: `10`)
--   `--debug`: Whether to log debug information to the console. Currently, this is only the standard error of the Electron app, which ordinarily is suppressed because the child process is detached
+- `--name`: Specify a name for the current measurement (default: `Electron Frontend Startup`)
+- `--folder`: Folder name for the generated tracing files in the `profiles` folder (default: `electron`)
+- `--workspace`: Absolute path to a Theia workspace to open (default: an empty workspace folder)
+- `--runs`: Number of runs for the measurement (default: `10`)
+- `--debug`: Whether to log debug information to the console. Currently, this is only the standard error of the Electron app, which ordinarily is suppressed because the child process is detached
 
 _**Note**: When multiple runs are specified the script will calculate the mean and the standard deviation of all values, except for any runs that failed to capture a measurement due to an exception._
 
@@ -81,22 +81,22 @@ The script can be executed by running `node extension-impact.js` in this directo
 
 The following parameters are available:
 
--   `--app`: The example app in which to measure performance, either `browser` or `electron` (default: `browser`)
--   `--runs`: Specify the number of measurements for each extension (default: `10`)
--   `--base-time`: Provide an existing measurement (mean) for the base Theia application. If none is provided it will be measured.
--   `--extensions`: Provide a list of extensions (need to be locally installed) that shall be tested (default: all extensions in packages folder)
+- `--app`: The example app in which to measure performance, either `browser` or `electron` (default: `browser`)
+- `--runs`: Specify the number of measurements for each extension (default: `10`)
+- `--base-time`: Provide an existing measurement (mean) for the base Theia application. If none is provided it will be measured.
+- `--extensions`: Provide a list of extensions (need to be locally installed) that shall be tested (default: all extensions in packages folder)
 
     _**Note**: Each entry should:_
 
-    -   _have the format {name}:{version}_
-    -   _not contain whitespaces_
-    -   _and be separated by whitespaces_
+  - _have the format {name}:{version}_
+  - _not contain whitespaces_
+  - _and be separated by whitespaces_
 
     _For example: `--extensions @theia/git:1.19.0 @theia/keymaps:1.19.0`_
 
--   `--yarn`: Flag to trigger a full yarn at script startup (e.g. to build changes to extensions)
--   `--url`: Specify a URL that Theia should be launched with (can be used to specify the workspace to be opened). _Applies only to the `browser` app_ (default: `http://localhost:3000/#/<GIT_ROOT>/scripts/performance/workspace`)
--   `--workspace`: Specify a workspace on which to launch Theia. _Applies only to the `electron` app_ (default: `/<GIT_ROOT>/scripts/performance/workspace`)
--   `--file`: Relative path to the output file (default: `./script.csv`)
+- `--yarn`: Flag to trigger a full yarn at script startup (e.g. to build changes to extensions)
+- `--url`: Specify a URL that Theia should be launched with (can be used to specify the workspace to be opened). _Applies only to the `browser` app_ (default: `http://localhost:3000/#/<GIT_ROOT>/scripts/performance/workspace`)
+- `--workspace`: Specify a workspace on which to launch Theia. _Applies only to the `electron` app_ (default: `/<GIT_ROOT>/scripts/performance/workspace`)
+- `--file`: Relative path to the output file (default: `./script.csv`)
 
 _**Note**: If no extensions are provided all extensions from the `packages` folder will be measured._