subtitle formating

Contributing-to-the-Cockatrice-Tokens-File.md

@@ -57,15 +57,15 @@ Here are some examples:
 
 As you can see, the `reverse-related` tag is made up of several parts. The name in the middle, in between the tag start and end, specifies the card that makes the token. The words within the `<reverse-related>` tag start are called attributes and they change how the relations function.
 
-#### `count`
+#### The `count` Attribute
 
 The `count` attribute specifies how many tokens the card should make when the player tells it to make tokens. `count=1` is assumed and does not needed to be stated, as in the first example, and `count="5"` will make exactly five tokens. `count="x"` will prompt the player to enter a number of tokens (defaulting to 1) and something like `count="x=3"` will also prompt the player, but will default to 3 instead of 1. This is useful when a card makes a variable number of tokens but is guaranteed to make at least a certain number.
 
-#### `attach`
+#### The `attach` Attribute
 
 Some tokens need to be attached to the card that made them. Including the `attach` attribute and setting it to "attach" (as in example 4 above) allows this to happen automatically on token creation. This is mainly useful for equipment. Setting the `attach` attribute to "transform" allows the card to transform into the token instead of creating it (e.g. Incubator Token).
 
-#### `exclude`
+#### The `exclude` Attribute
 
 One other attribute that can be included in `reverse-related` tags in `exclude`. Rather than relating directly to a rule of MTG, the `exclude` attribute relates to the technical implementation of creating tokens in Cockatrice. When making tokens from a card, there are two kinds of options available to the player. One is to make every token that the card can make (`Create All Tokens`) and the other is to make each individual kind of token (e.g. `Create 3/3 Beast Token`). When a card makes multiple kinds of tokens or different numbers of tokens at different times, we can use `exclude` to change the behavior of `Create All Tokens` to be in line with how the card works. I will give three cases to explain this in detail.
 
@@ -101,9 +101,11 @@ As above, the less likely option is excluded, allowing `Create All Tokens` to ma
 
 The first tag gives the player the option to make exactly one insect token and the second tag gives the player the option to get prompted to enter an amount and make multiple instead. Since the `count="x"` option is excluded, `Create All Tokens` will make a single insect token and will not prompt the player to enter an amount, again mimicking the most likely to be used option. Note that you should *not* apply this same logic to cards that makes tokens when spells are cast since each token should be made as each spell resolves.
 
-#### The `related` tag
+#### The `related` Tag
 
-One other tag to note here is `related`. This tag lets you specify a token that is *created by* the token entry instead of creating it. This is useful for tokens that make other tokens (usually when they die) like the Boar token that makes a Food token when it dies. `related` can also have attributes like `count`. `related` and `reverse-related` are redundant with each other; you do not need to add both to set up a relationship (and, in fact, this will make a mess of the token UI).
+One other tag to note here is `related`. This tag lets you specify a token that is *created by* the token entry instead of creating it. This is useful for the occasional tokens that make other tokens (usually when they die) like the Boar token that makes a Food token when it dies. `related` can also have attributes like `count`. `related` and `reverse-related` are redundant with each other; you do not need to add both to set up a relationship (and, in fact, this will make a mess of the token UI).
+
+#### Suggested Workflow for Adding `reverse-related` Tags
 
 Adding in `reverse-related` tags has to be done manually as there is a lot of nuance to it that is not easily automated. Here is the process that I follow to ensure I do it systematically.