<commit_before>#ma

Makes it simple to create a table of contents section with links to header anchors in the content.

---

## Install

`npm install ma -g`

## Use

Define the location of your table of contents by placing it between these two comments: 

1. `<!--- TABLE_OF_CONTENTS -->`
2. `<!--- /TABLE_OF_CONTENTS -->`.

Define the location of your content by placing it between these two comments: 

1. `<!--- CONTENT -->`
2. `<!--- /CONTENT -->`

After that, run `ma myMarkdownFile.md` from your command line.

If you run ma without specifying a file, it will automaticly try to find files with the `.md` and `.markdown` file extension.

#### Auto content
If the content is empty, it will automaticly place headers. When a section of your documentation has a sub section, it will automaticly give it a smaller font size. This font-sizing happens recursively up to `h6` headers.

#### Limitations
There is one limitation to naming sections and sub sections, they have to be unique! Otherwise both Github and ma wouldn't know which content header to match table of contents links with. This is not a ma limitation only. When you write your own markdown documentation, it is also required to use unique names.<commit_msg>Small (grammar) fixes<commit_after>#ma

Makes it simple to create a table of contents section with links to header anchors in the content.

---

## Install

`npm install ma -g`

## Use

Define the location of your table of contents by placing it between these two comments: 

1. `<!--- TABLE_OF_CONTENTS -->`
2. `<!--- /TABLE_OF_CONTENTS -->`.

Define the location of your content by placing it between these two comments: 

1. `<!--- CONTENT -->`
2. `<!--- /CONTENT -->`

After that, run `ma myMarkdownFile.md` from your command line.

If you run ma without specifying a file, it will automaticly try to find files with the `.md` and `.markdown` file extension.

#### Auto content
If the content is empty, it will automaticly place headers. When a section of your documentation has a sub section, it will automaticly give it a smaller font size. This font-sizing happens recursively up to `h6` headers.

#### Limitations
There is one limitation regarding naming of sections and sub sections, they have to be unique! Otherwise both Github and ma wouldn't know which content header to match table of contents links with. This is not a ma limitation only. When you write your own markdown documentation, it is also required to use unique names.
{'fraction_non_alphanumeric': 0.08191403081914031, 'fraction_numerical': 0.0040551500405515, 'mean_word_length': 3.7625482625482625, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '691075', 'n_tokens_mistral': 677, 'n_tokens_neox': 637, 'n_words': 374}