trailing whitespace from blank lines gone

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

@@ -27,12 +27,12 @@ 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)
      - The index of the module instances on the path that encountered un-recoverable errors (for each trigger encountering an error condition)
-     
+
      The corresponding code can be found in [DataFormats/Common/interface/TriggerResults.h](https://github.com/cms-sw/cmssw/blob/CMSSW_5_3_X/DataFormats/Common/interface/TriggerResults.h "TriggerResults.h") and [DataFormats/Common/interface/HLTGlobalStatus.h](https://github.com/cms-sw/cmssw/blob/CMSSW_5_3_X/DataFormats/Common/interface/HLTGlobalStatus.h "HLTGlobalStatus.h")
 
   2. `TriggerEvent`: Summarises the "L3" trigger collections and "L3" filter decisions.
@@ -56,15 +56,15 @@ Original Source: [SWGuideHighLevelTrigger](https://twiki.cern.ch/twiki/bin/view/
 <br>
 
 #### <b>MiniAOD (2015 and beyond)</b>
-  
+
   MiniAOD contains:
 
   - trigger bits associated to all paths
   - all the trigger objects that have contributed to firing at least one filter within the trigger
   - all objects reconstructed
   - L1 global trigger summary
   - the prescale values of all triggers
- 
+
   <b>Trigger bits for each path</b> are stored as `edm::TriggerResults`, as standard in CMSSW.
 
   In order to access paths by trigger name, you can get an `edm::TriggerNames` instance from the Event, which translates indices in names. The mapping is the same in all events sharing the same trigger configuration, which is defined by the `parameterSetID()` method of the trigger results object.
@@ -85,14 +85,14 @@ Original Source: [SWGuideHighLevelTrigger](https://twiki.cern.ch/twiki/bin/view/
 #### <b>NanoAOD (2016 and beyond)</b>
 
   In NanoAOD, trigger bit information is available for all trigger paths in the input files. The bits that are not available in some events are filled with zeros. Trigger objects are stored in NanoAOD for some filters as defined [here](https://github.com/cms-sw/cmssw/blob/master/PhysicsTools/NanoAOD/python/triggerObjects_cff.py#L53). Trigger prescales are not stored in NanoAOD, but this information can be found using the `brilcalc` command line tool, as described in the last two sections of the [CMS luminosity calculation guide](/docs/cms-guide-luminosity-calculation).
- 
+
  Trigger information is stored in the following collections of branches:
- 
+
   - `L1_*`: Trigger bit for each L1 path.
   - `L1PreFiringWeight_*`: L1 pre-firing event correction weight. Prefiring of L1 triggers represents a problem in their combined effect with the CMS trigger rules. It causes inefficiency in recording potentially interesting events. See the [CMS Open Data Guide](https://cms-opendata-guide.web.cern.ch/analysis/selection/triggers/) for more details.
   - `HLT_*`: Trigger bit for each HLT path.
 
-   
+
 ### 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: