Update 02-rucio_usage.md

Formatting updates and fixes.

Author: sjdkay

_episodes/02-rucio_usage.md

@@ -44,7 +44,7 @@ To use Rucio further, we will need to briefly look at how Rucio organises data.
 
 Typically, we want to analyse data contained within specific files. Files can be grouped together into datasets which can themselves, be grouped into containers. All three refer to "data". As such, the term "data identifier` or **DID** is used in Rucio. A DID is just the name of a single file, dataset or container.
 
-In Rucio, all DIDs follow a naming scheme which is composed of two strings - a **scope** and a **name**, formatted as -
+In Rucio, all DIDs follow a naming scheme which is composed of two strings - a **scope** and a **name**, formatted as:
 
 ``scope:name``
 
@@ -69,16 +69,16 @@ The `name` here - `/RECO/26.02.0/epic_craterlake/EXCLUSIVE/DEMP/DEMPgen-1.2.4/10
 - `EXCLSUIVE`
   - The DID is for a dataset of exclusive physics events
 - `DEMP`
- - This is the specific exclusive process simulated in the dataset, **D**eeply **E**xclusive **M**eson **P**roduction, DEMP
+  - This is the specific exclusive process simulated in the dataset, **D**eeply **E**xclusive **M**eson **P**roduction, DEMP
 - `DEMPgen-1.2.4`
   - The simulation in this dataset is based upon input generated by the `DEMPgen-1.2.4` event generator
 - `10x130`
- - The files in this dataset were simulated with 10 GeV electrons on 130 GeV ions (in this case protons, if the ion species is not specified, it is likely to be an ep simulation)
- - The AAxBBB format, where AA is the electron energy and BBB is the ion energy, is typical for quoting beam energies in EIC files. This may be written as AAonBBB too.
+  - The files in this dataset were simulated with 10 GeV electrons on 130 GeV ions (in this case protons, if the ion species is not specified, it is likely to be an ep simulation)
+  - The AAxBBB format, where AA is the electron energy and BBB is the ion energy, is typical for quoting beam energies in EIC files. This may be written as AAonBBB too.
 - `q2_10_20`
   - The files in this dataset are from a simulation input containing events in the 10 to 20 GeV2 Q2 range
 - `pi+`
- - Pi+ are generated in this output - this is specific to this DEMP reaction and signifies that it is Deeply Exclusive Pion Production
+  - Pi+ are generated in this output - this is specific to this DEMP reaction and signifies that it is Deeply Exclusive Pion Production
 
 > ## `Warning - Not a filepath!`
 > The `name` of our DID here looks a lot like a filepath, however it is a flat object and does **not** have any hierarchy as we will see in the next section.
@@ -90,27 +90,27 @@ Other names may not necessarily contain all of the same information, but as a ba
 
 Now that we know what a DID looks like, how can we find the DID corresponding to the file or dataset that we're interested in?
 
-Well, we can list DIDs using -
+Well, we can list DIDs using:
 
 ```bash
 rucio did list scope:name
 ```
 
-To begin though, let's try -
+To begin though, let's try:
 
 ```bash
 rucio did list --help
 ```
 
-As we can see, we can apply filters to our list request if we want. We can also apply wildcards, but we need to be a bit careful due to the warning above. Whilst our DIDs *look* like a unix file path, they are not. The structure is flat. We can quickly see this if we try -
+As we can see, we can apply filters to our list request if we want. We can also apply wildcards, but we need to be a bit careful due to the warning above. Whilst our DIDs *look* like a unix file path, they are not. The structure is flat. We can quickly see this if we try:
 
 ```bash
 rucio did list epic:/RECO/\*
 ```
 
 We get an enormous number of DIDs returned! This is every reconstruction related DID available to access right now.
 
-Working backwards from the full DID we had earlier, we could combine in the software release, detector configuration, process and generator to narrow down the list of DIDs
+Working backwards from the full DID we had earlier, we could combine in the software release, detector configuration, process and generator to narrow down the list of DIDs:
 
 ```bash
 rucio did list epic:/RECO/26.02.0/epic_craterlake/EXCLUSIVE/DEMP/DEMPgen-1.2.4/\*