TA: fixed format in markdown file

hpc-gridware · Jan 15, 2025 · 120454b · 120454b
1 parent 410c281
commit 120454b
Showing 1 changed file with 8 additions and 16 deletions.
diff --git a/doc/markdown/manual/development-guide/00_overview.md b/doc/markdown/manual/development-guide/00_overview.md
@@ -1,7 +1,6 @@
 # Introduction
 
-This guide is intended for developers who want to contribute to the ClusterScheduler project.
-It provides an overview of the project structure, the development process, and the tools used in the project.
+This guide is intended for developers who want to contribute to the ClusterScheduler project. It provides an overview of the project structure, the development process, and the tools used in the project.
 
 # Contributing to the ClusterScheduler Project
 
@@ -11,18 +10,11 @@ It provides an overview of the project structure, the development process, and t
 
 ## Tags
 
-Whenever we release a stable version we create a tag in the git repository.  
-Version numbers consist of three parts: major, minor, and patch, e.g. `9.0.0`.  
-The tag is named after the version number, e.g. `V900_TAG`.  
-Pre-releases might also be tagged, e.g. `V900alpha1_TAG`.
+Whenever we release a stable version we create a tag in the git repository. Version numbers consist of three parts: major, minor, and patch, e.g. `9.0.0`. The tag is named after the version number, e.g. `V900_TAG`. Pre-releases might also be tagged, e.g. `V900alpha1_TAG`.
 
 ## Branches
 
-The `master` branch is the main development branch.  
-It is used for the development of new features and bug fixes.  
-When we start working on features for a new major or minor release we will create a new branch
-for the maintenance of the current release, e.g. a `V90_BRANCH` for the maintenance of
-`9.0.x` versions when we start developmment on `9.1.0`.
+The `master` branch is the main development branch. It is used for the development of new features and bug fixes. When we start working on features for a new major or minor release we will create a new branch for the maintenance of the current release, e.g. a `V90_BRANCH` for the maintenance of `9.0.x` versions when we start developmment on `9.1.0`.
 
 ## Existing Tags and Branches of the ClusterScheduler Project
 
@@ -34,9 +26,9 @@ Tags and branches before `V9` will also not be described here.
 | Branch         | Tag         | Description                                                             |  
 |:---------------|:------------|:------------------------------------------------------------------------|
 | master         |             | main development branch                                                 |  
-|                | V900_TAG    | first OCS/GCS release                                                   |  
-|                | V901_TAG    | first 9.0 patch                                                         |
-|                | V902_TAG    | second 9.0 patch                                                        |
+|                | V900\_TAG   | first OCS/GCS release                                                   |  
+|                | V901\_TAG   | first 9.0 patch                                                         |
+|                | V902\_TAG   | second 9.0 patch                                                        |
 |                |             |                                                                         |
-| V900_BRANCH    |             | maintenance of 9.0.0                                                    |
-|                | V900p1_TAG  | patch to the 9.0.0 making it work on GCP (CS-663)                       |
+| V900\_BRANCH   |             | maintenance of 9.0.0                                                    |
+|                | V900p1\_TAG | patch to the 9.0.0 making it work on GCP (CS-663)                       |