Docs: Run Output - Clarification and Additions

Clarification of the meanings of and the distinction between the
output-related terms iteration, job, workload and section for those
unfamiliar
- Add entries to the glossary and references to the glossary
- Added section on Configuration parameter hierarchy
- Added section on the number and names of directories generated for
jobs in the run output folder

doc/source/user_information/user_reference/agenda.rst

@@ -59,7 +59,7 @@ An example agenda can be seen here:
                 num_big_cores: 4
                 num_little_cores: 0
 
-    workloads:                  # List which workloads should be ran
+    workloads:                  # List which workloads should be run
     -   name: benchmarkpi
         augmentations:
             - ~trace-cmd        # Disable the trace-cmd instrument for this workload
@@ -160,15 +160,15 @@ Plugins
 workloads
 ^^^^^^^^^
 
-Here you can specify a list of workloads to be ran. If you wish to run a
+Here you can specify a list of workloads to be run. If you wish to run a
 workload with all default values then you can specify the workload name directly
 as an entry, otherwise a dict mapping should be provided. Any settings provided
 here will be the most specific and therefore override any other more generalised
 configuration for that particular workload spec. The valid entries are as
 follows:
 
-:workload_name: **(Mandatory)** The name of the workload to be ran
-:iterations: Specify how many iterations the workload should be ran
+:workload_name: **(Mandatory)** The name of the workload to be run
+:iterations: Specify how many iterations the workload should be run
 :label: Similar to IDs but do not have the uniqueness restriction.
     If specified, labels will be used by some output processors instead of (or in
     addition to) the workload name. For example, the csv output processor will put