fix AOD, MiniAOD bullet lists

cernopendata/modules/fixtures/data/docs/cms-guide-trigger-system/cms-guide-trigger-system.md

@@ -1,4 +1,4 @@
-An event is the result of a single reading of the detector electronics capturing signals generated by particles from several bunch crossings. The online Trigger and Data Acquisition System (TriDAS) is tasked with selecting and storing the most interesting events (around 100 events per second) from the millions of detected events. An event has to pass two independent sets of tests, or Trigger Levels, in order to qualify. These tests range from quick and simple (Level 1, called L1) to more complex and time-consuming (Levels 2 and 3, called the "high-level trigger", or HLT). Ultimately, the HLT system produces RAW data events containing:
+An event is the result of a single reading of the detector electronics capturing signals generated by particles from several bunch crossings. The online Trigger and Data Acquisition System (TriDAS) is tasked with selecting and storing the most interesting events (around 1000 events per second) from the millions of detected events. An event has to pass two independent sets of tests, or Trigger Levels, in order to qualify. These tests range from quick and simple (Level 1, called L1) to more complex and time-consuming (Levels 2 and 3, called the "high-level trigger", or HLT). Ultimately, the HLT system produces RAW data events containing:
 
 - the detector data,
 - the L1 trigger result
@@ -27,6 +27,7 @@ Original Source: [SWGuideHighLevelTrigger](https://twiki.cern.ch/twiki/bin/view/
   1. `TriggerResults`: Contains all the usual decision bits. It is subclassed from `HLTGlobalStatus` object.
 
      The `TriggerResults` product is available for events written to output. It provides access to both configuration information and trigger decisions, i.e., all the usual "trigger bits", including:
+
      - Final decision of individual path and of full trigger table
      - Which triggers were run (some triggers may not run due to lack of a corresponding L1 seed or HLT running in truncated mode)
      - The index of the intermediate or final module instances on the path that rejected the event (for each trigger rejecting the event)
@@ -60,6 +61,7 @@ configuration can only change between runs.
 #### <b>MiniAOD (2015 and beyond)</b>
 
   MiniAOD contains:
+
   - trigger bits accosciated to all paths
   - all the trigger objects that have contributed to firing at least one filter within the trigger
   - all objects reconstructed
@@ -76,7 +78,7 @@ configuration can only change between runs.
 
   For tips and examples on accessing the trigger information, check the [MiniAOD Analysis Documentation](https://twiki.cern.ch/twiki/bin/view/CMSPublic/WorkBookMiniAOD2015), which contains both example CMSSW code and example python code.
 
-  Find examples for accessing trigger information using POET (physics object extractor tool) in
+  Find examples for accessing trigger information using POET (physics object extractor tool) in:
 
   - [Physics object extractor tool for the CMS 2015 data](/record/12502).
   - [CMS Open Data Workshops](https://cms-opendata-guide.web.cern.ch/cmsOpenData/workshops/), particularly from 2022 and 2023.
@@ -96,7 +98,7 @@ configuration can only change between runs.
 
 ### HLT Trigger Path definitions
 
-For each dataset, the possible HLT trigger paths are listed in the dataset record. Each HLT path is composed of different algorithms defined in the data-taking configuration files, which are given in
+For each dataset, the possible HLT trigger paths are listed in the dataset record. Each HLT path is composed of different algorithms defined in the data-taking configuration files, which are given in:
 
 - [High-Level Trigger information for 2010 CMS open data](/record/1699)
 - [High-Level Trigger information for 2011 CMS open data](/record/1700)