fix(report): unify .rst section marks

Unify characters marking section levels,
(at least for methodology Vratko contributed to):

Level 0: ==== Do not use, or use for index.rst only.
 (Because git conflicts also create ====.)
Level 1: ^^^^
Level 2: ~~~~
Level 3: ````
Level 4: ____
Level 5: ---- Do not use.
 (Because other documents use this as level 0,
 and it also appears in tables.)

Change-Id: I10813f718b2ee34d1e34c58e62e88353000340e9
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
(cherry picked from commit 6809aeefd0f2b951cd4861f676ee2dff0df47ff2)

5 files changed, 22 insertions, 22 deletions

diff --git a/docs/report/introduction/methodology_data_plane_throughput/index.rst b/docs/report/introduction/methodology_data_plane_throughput/index.rst
index 487d300b5b..e2e373c56f 100644
--- a/docs/report/introduction/methodology_data_plane_throughput/index.rst
+++ b/docs/report/introduction/methodology_data_plane_throughput/index.rst
@@ -1,5 +1,5 @@
 Data Plane Throughput
-=====================
+---------------------
 
 .. toctree::
 
diff --git a/docs/report/introduction/methodology_data_plane_throughput/methodology_data_plane_throughput.rst b/docs/report/introduction/methodology_data_plane_throughput/methodology_data_plane_throughput.rst
index a26b40088b..24e76ef391 100644
--- a/docs/report/introduction/methodology_data_plane_throughput/methodology_data_plane_throughput.rst
+++ b/docs/report/introduction/methodology_data_plane_throughput/methodology_data_plane_throughput.rst
@@ -1,7 +1,7 @@
 .. _data_plane_throughput:
 
 Data Plane Throughput Tests
----------------------------
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Network data plane throughput is measured using multiple test methods in
 order to obtain representative and repeatable results across the large
@@ -21,10 +21,10 @@ Description of each test method is followed by generic test properties
 shared by all methods.
 
 MLRsearch Tests
-^^^^^^^^^^^^^^^
+~~~~~~~~~~~~~~~
 
 Description
-~~~~~~~~~~~
+```````````
 
 Multiple Loss Ratio search (MLRsearch) tests discover multiple packet
 throughput rates in a single search, reducing the overall test execution
@@ -35,7 +35,7 @@ and Partial Drop Rate (PDR, with PLR<0.5%). MLRsearch is compliant with
 :rfc:`2544`.
 
 Usage
-~~~~~
+`````
 
 MLRsearch tests are run to discover NDR and PDR rates for each VPP and
 DPDK release covered by CSIT report. Results for small frame sizes
@@ -50,17 +50,17 @@ all frame sizes and for all tests are presented in detailed results
 tables.
 
 Details
-~~~~~~~
+```````
 
 See :ref:`mlrsearch_algorithm` section for more detail. MLRsearch is
 being standardized in IETF in `draft-ietf-bmwg-mlrsearch
 <https://datatracker.ietf.org/doc/html/draft-ietf-bmwg-mlrsearch-01>`_.
 
 MRR Tests
-^^^^^^^^^
+~~~~~~~~~
 
 Description
-~~~~~~~~~~~
+```````````
 
 Maximum Receive Rate (MRR) tests are complementary to MLRsearch tests,
 as they provide a maximum “raw” throughput benchmark for development and
@@ -72,7 +72,7 @@ a set trial duration, regardless of packet loss. Maximum load for
 specified Ethernet frame size is set to the bi-directional link rate.
 
 Usage
-~~~~~
+`````
 
 MRR tests are much faster than MLRsearch as they rely on a single trial
 or a small set of trials with very short duration. It is this property
@@ -86,7 +86,7 @@ comparisons between releases and test environments. Small frame sizes
 only (64b/78B, IMIX).
 
 Details
-~~~~~~~
+```````
 
 See :ref:`mrr_throughput` section for more detail about MRR tests
 configuration.
@@ -98,10 +98,10 @@ and `VPP per patch tests
 <https://s3-docs.fd.io/csit/master/trending/methodology/perpatch_performance_tests.html>`_.
 
 PLRsearch Tests
-^^^^^^^^^^^^^^^
+~~~~~~~~~~~~~~~
 
 Description
-~~~~~~~~~~~
+```````````
 
 Probabilistic Loss Ratio search (PLRsearch) tests discovers a packet
 throughput rate associated with configured Packet Loss Ratio (PLR)
@@ -110,7 +110,7 @@ testing. PLRsearch assumes that system under test is probabilistic in
 nature, and not deterministic.
 
 Usage
-~~~~~
+`````
 
 PLRsearch are run to discover a sustained throughput for PLR=10^-7
 (close to NDR) for VPP release covered by CSIT report. Results for small
@@ -121,14 +121,14 @@ Each soak test lasts 30 minutes and is executed at least twice. Results are
 compared against NDR and PDR rates discovered with MLRsearch.
 
 Details
-~~~~~~~
+```````
 
 See :ref:`plrsearch` methodology section for more detail. PLRsearch is
 being standardized in IETF in `draft-vpolak-bmwg-plrsearch
 <https://tools.ietf.org/html/draft-vpolak-bmwg-plrsearch>`_.
 
 Generic Test Properties
-^^^^^^^^^^^^^^^^^^^^^^^
+~~~~~~~~~~~~~~~~~~~~~~~
 
 All data plane throughput test methodologies share following generic
 properties:
diff --git a/docs/report/introduction/methodology_data_plane_throughput/methodology_mlrsearch_tests.rst b/docs/report/introduction/methodology_data_plane_throughput/methodology_mlrsearch_tests.rst
index 6789dc073b..f834ca3e1b 100644
--- a/docs/report/introduction/methodology_data_plane_throughput/methodology_mlrsearch_tests.rst
+++ b/docs/report/introduction/methodology_data_plane_throughput/methodology_mlrsearch_tests.rst
@@ -1,7 +1,7 @@
 .. _mlrsearch_algorithm:
 
 MLRsearch Tests
----------------
+^^^^^^^^^^^^^^^
 
 Overview
 ~~~~~~~~
diff --git a/docs/report/introduction/methodology_data_plane_throughput/methodology_mrr_throughput.rst b/docs/report/introduction/methodology_data_plane_throughput/methodology_mrr_throughput.rst
index 4e8000b161..f2a6cd57cd 100644
--- a/docs/report/introduction/methodology_data_plane_throughput/methodology_mrr_throughput.rst
+++ b/docs/report/introduction/methodology_data_plane_throughput/methodology_mrr_throughput.rst
@@ -1,7 +1,7 @@
 .. _mrr_throughput:
 
 MRR Throughput
---------------
+^^^^^^^^^^^^^^
 
 Maximum Receive Rate (MRR) tests are complementary to MLRsearch tests,
 as they provide a maximum "raw" throughput benchmark for development and
diff --git a/docs/report/introduction/methodology_data_plane_throughput/methodology_plrsearch.rst b/docs/report/introduction/methodology_data_plane_throughput/methodology_plrsearch.rst
index d60e9203ff..a128674384 100644
--- a/docs/report/introduction/methodology_data_plane_throughput/methodology_plrsearch.rst
+++ b/docs/report/introduction/methodology_data_plane_throughput/methodology_plrsearch.rst
@@ -1,7 +1,7 @@
 .. _plrsearch:
 
 PLRsearch
----------
+^^^^^^^^^
 
 Motivation for PLRsearch
 ~~~~~~~~~~~~~~~~~~~~~~~~
@@ -25,7 +25,7 @@ draft `draft-vpolak-bmwg-plrsearch-02`_ that is in the process
 of being standardized in the IETF Benchmarking Methodology Working Group (BMWG).
 
 Terms
------
+`````
 
 The rest of this page assumes the reader is familiar with the following terms
 defined in the IETF draft:
@@ -319,7 +319,7 @@ low quality estimate at first sight, but a more detailed look
 reveals the quality is good (considering the measurement results).
 
 L2 patch
---------
+________
 
 Both fitting functions give similar estimates, the graph shows
 "stochasticity" of measurements (estimates increase and decrease
@@ -356,7 +356,7 @@ the performance stays constant.
         :align: center
 
 Vhost
------
+_____
 
 This test case shows what looks like a quite broad estimation interval,
 compared to other test cases with similarly looking zero loss frequencies.
@@ -390,7 +390,7 @@ agrees that the interval should be wider than that.
         :align: center
 
 Summary
--------
+_______
 
 The two graphs show the behavior of PLRsearch algorithm applied to soaking test
 when some of PLRsearch assumptions do not hold: