docs: Standardize documentation headings (remove multiple # H1)

- Remove multiple single top-level (# H1) headings per file
 - Use (# H2 and ###### H6) sub-headings for consistency
 - Remove any trailing # in the headings
 - This ensures proper table of contents rendering in MkDocs.

 - Also removed RUN_NR_multiple_BWPs.md as it is moved to MAC usage

doc/handover-tutorial.md

@@ -12,7 +12,7 @@ the CU and the associated DUs.
 
 [[_TOC_]]
 
-# Considered setup for F1 handover
+## Considered setup for F1 handover
 
 We consider one CU and two DUs, connected over F1. The UE is initially
 connected over the radio interface ("Uu") to DU0. Via movement to a new
@@ -22,7 +22,7 @@ same.
 
 ![F1 Handover setup](./RRC/ho.png)
 
-# gNB neighbour definition
+## What is a gNB neighbor?
 
 Network continuity is a key aspect of 5G. In the 5G architecture, gNB neighbours
 play a central role in maintaining service continuity through mechanisms such
@@ -39,13 +39,13 @@ Neighbour types include:
 - **Inter-gNB neighbours** - cells belonging to different gNBs
 - **Inter-RAT neighbours** - cells belonging to another RAT (e.g., LTE)
 
-# Steps to run F1 handover with OAI UE
+## Steps to run F1 handover with OAI UE
 
 Measurement reporting and processing of RRC Reconfiguration for Mobility are
 not completed at the UE. Nevertheless, it is possible to make simple handover
 tests without any radio setup, on a single PC, with the OAI UE, in RFsimulator.
 
-## Build with telnet support
+### Build with telnet support
 
 Since the UE does not support any measurement reporting, it cannot trigger a
 handover on its own; it has to be triggered manually through telnet. Thus,
@@ -53,7 +53,7 @@ build both gNB and UE as well as activate the build of telnet to that purpose:
 
     ./build_oai --ninja --nrUE --gNB --build-lib telnetsrv
 
-## Run the setup
+### Run the setup
 
 We will use the TDD configuration files in the repository for the
 [CU](../targets/PROJECTS/GENERIC-NR-5GC/CONF/gnb-cu.sa.f1.conf) as well for
@@ -116,7 +116,7 @@ A number of remarks:
 1. In some cases, if the RFsim server is at the UE, the whole system can block;
    in this case, stop UE and all DUs and restart (the CU can keep running).
 
-## Additional information to the manual HO trigger
+### Additional information to the manual HO trigger
 
 You can trigger the handover manually by logging in through telnet:
 
@@ -139,7 +139,7 @@ and you have to manually type the CU UE ID. You can see a list of all UEs in
 the file `nrRRC_stats.log` that is printed periodically in the working
 directory of the CU.
 
-# Steps to run F1 handover with COTS UE
+## Steps to run F1 handover with COTS UE
 
 You can do handover across DUs with a COTS UE. Note that these DUs should be
 separated by at least multiple meters to ensure that the UE will receive
@@ -156,7 +156,7 @@ For UEs, we verified Quectel modules, iPhones and Samsung S23 Ultra. Note,
 though, that not all phones might work; for instance, we did not achieve
 handovers with a OnePlus Nord, yet.
 
-## Steps
+### Steps
 
 First, make sure that you can run both DUs with the CU independently.
 Use the same radio hardware for both radios to ensure that both cells can be
@@ -217,7 +217,7 @@ Our CI setup consists of:
 To run the setup using Docker:
 - We consider 2 synchronized servers. One for each DU.
 
-## Example neighbour configuration
+### Example neighbour configuration
 
 Below is an example neighbour configuration. It is based on this DU information
 gathered from `nrRRC_stats.log` at the CU:
@@ -339,13 +339,13 @@ below.
 
 ```
 
-# Handovers triggers and NTN
+## Handovers triggers and NTN
 
 Typically, in terrestrial networks, channel measurements as well as criteria
 such as load in base stations, is used to determine when and where to handover
 a UE.
 
-## NTN
+### NTN
 
 Doppler spreading and time selectivity of the channel are already a challenge
 for conventional terrestrial networks. However, in the context of
@@ -400,7 +400,7 @@ are as follows:
   which sends the preamble. However, UEs with GNSS support are required to
   perform this method.
 
-## Simple location/time-based trigger
+### Simple location/time-based trigger
 
 A location-based handover trigger, somewhat aligned with 3GPP Rel.17, taking
 advantage of deterministic satellite movement, can be implemented whereby it is
@@ -420,9 +420,9 @@ while true; do
 done
 ```
 
-# N2 Handover
+## N2 Handover
 
-## Run the setup
+### Run the setup
 
 An N2 handover involves the transfer of a UE from one gNB to another via the
 5G core network. Unlike F1 handover, where the CU handles the process internally
@@ -436,7 +436,7 @@ We assume:
 * Handover is triggered by either a decision based measurement event (e.g. A3)
 or telnet command.
 
-## Steps to run N2 handover with OAI UE
+### Steps to run N2 handover with OAI UE
 
 **Note for same-machine setup:** When running both gNBs on the same machine,
 you need to assign a unique IP address to the second gNB to avoid network
@@ -496,7 +496,7 @@ RRC ID of the UE.
 
 This will initiate the N2 handover on the source gNB.
 
-## Neighbour list and measurement configuration
+### Neighbour list and measurement configuration
 
 Make sure the configuration file contains a neighbour list and measurement
 configuration, e.g. [neighbour-config-rfsim.conf](../../ci-scripts/conf_files/neighbour-config.conf).