Correct nummering

Author: Jonasvdbo

docs/2. User manual and workshops/2.1. preparation/1-setup-archi.md

@@ -1,4 +1,4 @@
-# 5.1.1. Setting up and configuring Archi and the plug-in
+# 2.1.1. Setting up and configuring Archi and the plug-in
 
 ## Installing Archi
 

docs/2. User manual and workshops/2.1. preparation/2-prepare-github.md

@@ -1,4 +1,4 @@
-# 5.1.2. Preparing your GitHub account to configure Archi integration
+# 2.1.2. Preparing your GitHub account to configure Archi integration
 
 1. Log onto your GitHub Account at [GitHub.com](https://github.com) or create a GitHub account at [GitHub.com](https://github.com)
 2. Please share your GitHub account name by emailing it to [email protected], so that we can add you to the NBility-Model GitHub organization.

docs/2. User manual and workshops/2.1. preparation/3-import-model-to-archi.md

@@ -1,4 +1,4 @@
-# 5.1.3. Import the model from GitHub into Archi
+# 2.1.3. Import the model from GitHub into Archi
 
 Once you have configured Archi and coArchi, and generated your Github Personal Access Token (PAT) you will be able to import the Nbility model into archi.
 

docs/2. User manual and workshops/2.2. archi-beginner/1-navigate-ui.md

@@ -2,7 +2,7 @@
 title: "Navigate the UI"
 ---
 
-# 5.2.1. Navigating the user interface
+# 2.2.1. Navigating the user interface
 
 1. In Archi, select [**Toggle Collaboration Workspace**] and [**Toggle Branches View**] from the **Collaboration** menu.  The Workspace and Branch windows will be docked within Archi.  Archi/coArchi supports repository branches.
 

docs/2. User manual and workshops/2.2. archi-beginner/2-refresh-model.md

@@ -2,7 +2,7 @@
 title: "Refresh model"
 ---
 
-# 5.2.2. Refreshing the model
+# 2.2.2. Refreshing the model
 
 **IMPORTANT: To ensure that the local repository remains synchronized with the upstream repository and to prevent overwriting any changes made since the last pull from the server, it is crucial to refresh the model from GitHub before applying any modifications.** Regular refreshs of the model not only maintain alignment with the upstream repository but also mitigate the risk of merge conflicts.
 

docs/2. User manual and workshops/2.2. archi-beginner/3-add-new-branch.md

@@ -2,7 +2,7 @@
 title: "Add new branch"
 ---
 
-# 5.2.3. Adding a new branch
+# 2.2.3. Adding a new branch
 
 To protect the integrity of the main branch and avoid overwriting updates from someone else, it is recommended to create a branch for each new piece of work.  Branches could be named by feature_[**topic name**] or fix_[**topic name**].  Branches can be created either through the coArchi plugin or via Github.com.
 

docs/2. User manual and workshops/2.2. archi-beginner/4-switch-branch.md

@@ -2,7 +2,7 @@
 title: "Switch branch"
 ---
 
-# 5.2.4. Switching branches
+# 2.2.4. Switching branches
 
 1. In archi, select [**Toggle Branches View**] from the **Collaboration** menu.
 2. In archi, right click on the branch you like to switch to and click on [**Switch branch**].

docs/2. User manual and workshops/2.2. archi-beginner/5-commit-and-publish-change.md

@@ -2,7 +2,7 @@
 title: "Commit and publish changes"
 ---
 
-# 5.2.5. Committing and publishing changes
+# 2.2.5. Committing and publishing changes
 
 1. To commit your latest changes, select [**Commit changes**] from the **Collaboration** menu. 
 

docs/2. User manual and workshops/2.2. archi-beginner/6-merge-change.md

@@ -2,7 +2,7 @@
 title: "Merge change"
 ---
 
-# 5.2.6. Creating a pull request review and merging topic branch
+# 2.2.6. Creating a pull request review and merging topic branch
 
 On regular intervals all committed and published branches need to be merged into the main branch which will trickle down into all subsequent branches.
 

docs/2. User manual and workshops/2.2. archi-beginner/7-export-xml.md

@@ -2,7 +2,7 @@
 title: "Export to XML"
 ---
 
-# 5.2.7. Exporting a model to an Open Exchange XML file
+# 2.2.7. Exporting a model to an Open Exchange XML file
 
 1. Open Archi on your local machine and select the architecture repository which you would like to export. For the purpose of this example, we choose Nbility-business-capabilities-EN. See image below.