mrtoolkit
diff --git a/‎docs/hackers/images/markdown-0.png
-747 Bytes b/‎docs/hackers/images/markdown-0.png
-747 Bytes
diff --git a/‎docs/hackers/images/markdown-1.png
-50.5 KB b/‎docs/hackers/images/markdown-1.png
-50.5 KB
diff --git a/‎docs/hackers/images/markdown-2.png
7.02 KB b/‎docs/hackers/images/markdown-2.png
7.02 KB
diff --git a/‎docs/hackers/images/markdown-3.png
-374 KB b/‎docs/hackers/images/markdown-3.png
-374 KB
diff --git a/‎docs/hackers/images/markdown-4.png
81.7 KB b/‎docs/hackers/images/markdown-4.png
81.7 KB
diff --git a/‎docs/hackers/images/markdown-5.png
13.5 KB b/‎docs/hackers/images/markdown-5.png
13.5 KB
diff --git a/‎docs/hackers/images/markdown-auto-link-mitre.png
49.5 KB b/‎docs/hackers/images/markdown-auto-link-mitre.png
49.5 KB
diff --git a/‎docs/hackers/images/markdown-blockquote.png
17.4 KB b/‎docs/hackers/images/markdown-blockquote.png
17.4 KB
diff --git a/‎docs/hackers/images/markdown-bullets.png
17.1 KB b/‎docs/hackers/images/markdown-bullets.png
17.1 KB
diff --git a/‎docs/hackers/images/markdown-code-syntax-input.png
16.8 KB b/‎docs/hackers/images/markdown-code-syntax-input.png
16.8 KB
diff --git a/‎docs/hackers/images/markdown-code-syntax.png
21.3 KB b/‎docs/hackers/images/markdown-code-syntax.png
21.3 KB
diff --git a/‎docs/hackers/images/markdown-code.png
16.1 KB b/‎docs/hackers/images/markdown-code.png
16.1 KB
diff --git a/‎docs/hackers/images/markdown-codeblock-input.png
-4.69 KB b/‎docs/hackers/images/markdown-codeblock-input.png
-4.69 KB
diff --git a/‎docs/hackers/images/markdown-codeblock-output.png
21.5 KB b/‎docs/hackers/images/markdown-codeblock-output.png
21.5 KB
diff --git a/‎docs/hackers/images/markdown-headers.png
15.5 KB b/‎docs/hackers/images/markdown-headers.png
15.5 KB
diff --git a/‎docs/hackers/images/markdown-link-3.png
15.5 KB b/‎docs/hackers/images/markdown-link-3.png
15.5 KB
diff --git a/‎docs/hackers/images/markdown-links-2.png
18.8 KB b/‎docs/hackers/images/markdown-links-2.png
18.8 KB
diff --git a/‎docs/hackers/images/markdown-links.png
18.1 KB b/‎docs/hackers/images/markdown-links.png
18.1 KB
diff --git a/‎docs/hackers/images/markdown-multiple.png
19.5 KB b/‎docs/hackers/images/markdown-multiple.png
19.5 KB
diff --git a/‎docs/hackers/images/markdown-numbered-list.png
16.5 KB b/‎docs/hackers/images/markdown-numbered-list.png
16.5 KB
diff --git a/‎docs/hackers/images/markdown-report-reference.png
40.2 KB b/‎docs/hackers/images/markdown-report-reference.png
40.2 KB
diff --git a/‎docs/hackers/images/markdown-user-mentions.png
17.7 KB b/‎docs/hackers/images/markdown-user-mentions.png
17.7 KB
diff --git a/‎docs/hackers/using-markdown.md
Lines changed: 54 additions & 25 deletions b/‎docs/hackers/using-markdown.md
Lines changed: 54 additions & 25 deletions
@@ -56,7 +56,6 @@ Markdown Input:
 *This text is italicized*
 _This text is underlined_
 **This text is bold**
-__This text is bold__
 ~~This text is deleted~~
 ==This text is highlighted==
 ```
@@ -107,6 +106,14 @@ Markdown Input:
 3. Blue
 ```
 
+and this:
+
+```
+1. Red
+1. Green
+1. Blue
+```
+
 Output:
 
 ![ordered list](./images/markdown-numbered-list.png)
@@ -138,12 +145,6 @@ Output:
 
 ![link](./images/markdown-link-3.png)
 
-Optionally, you may include a title attribute in the parentheses. Hover on the link to see the title:
-```
-This is an [example link](http://example.com/ "With a Title").
-```
-This is an [example link](http://example.com/ "With a Title").
-
 Reference-style links allow you to refer to your links by names, which you define elsewhere in your document:
 
 Markdown Input:
@@ -152,16 +153,16 @@ Markdown Input:
 I get 10 times more traffic from [Google][1] than from
 [Yahoo][2] or [MSN][3].
 
-[1]: http://google.com/        "Google"
-[2]: http://search.yahoo.com/  "Yahoo Search"
-[3]: http://search.msn.com/    "MSN Search"
+[1]: http://google.com/
+[2]: http://search.yahoo.com/
+[3]: http://search.msn.com/
 ```
 
 Output:
 
 ![multiple links](./images/markdown-links-2.png)
 
-The title attribute is optional. Link names may contain letters, numbers and spaces, but are not case sensitive:
+Link names may contain letters, numbers and spaces, but are not case sensitive:
 
 Markdown Input:
 
@@ -176,6 +177,26 @@ Output:
 
 ![ny times link](./images/markdown-links.png)
 
+<br>
+
+Links to section headings can be made as well. Every heading will get an ID based on the heading content, and prefixed with `user-content-`. A link can be made to a heading using the following markdown:
+
+```
+# Table of contents
+* [Introduction](#user-content-introduction)
+* [Another section](#user-content-another-section)
+* [Credits](#user-content-credits)
+
+# Introduction
+Text would go here.
+
+# Another section
+Some more text would go here.
+
+# Credits
+And the credits would go here.
+```
+
 #### Email Links
 You don't need to use markdown to create a `mailto:` link. Simply enter the email as is and it will automatically be converted to a `mailto:` link.
 
@@ -207,24 +228,19 @@ To use syntax highlighting, specify the content type after the three opening bac
 
 Markdown Input:
 
-```
-```javascript
-document.location = 'https://hackerone.com';
-```
+![markdown code syntax](./images/markdown-code-syntax-input.png)
 
 Output:
 
 ![markdown code syntax](./images/markdown-code-syntax.png)
 
-Go to the following web page to see which content types are available for syntax highlighting: https://github.com/jneen/rouge/tree/master/lib/rouge/demos.
-
 ### User mentions
 You can mention a user by prefixing username with '@' symbol
 
 Markdown Input:
 
 ```
-@demo-member reported the issue
+@demo-member reported the issue.
 ```
 
 Output:
@@ -238,9 +254,26 @@ Output:
 
 You can reference a report by prefixing report id with '#' symbol
 ```
-#105887 is a publicly disclosed bug
+#105887 is a publicly disclosed bug.
+```
+
+Output:
+
+![markdown report reference](./images/markdown-report-reference.png)
+
+<br>
+
+### Auto-linked references
+
+CVE IDs, CWE IDs, and CAPEC IDs are automatically linked to MITRE:
+
+```
+CVE-2011-0242 could perhaps be categorized as CWE-79 of CAPEC-63.
 ```
-[#105887](https://hackerone.com/reports/105887) is a publicly disclosed bug
+
+Output:
+
+![autolinking references to MITRE](./images/markdown-auto-link-mitre.png)
 
 ### Attachment references
 
@@ -252,18 +285,14 @@ Example: Consider a user is creating a report and uploads an attachment. Once th
 Now you can reference the attachment in the report by writing 'F1' and the attachment is referenced in the report as shown below.
 ![markdown-2](./images/markdown-2.png)
 
-When the link is clicked, the attachment is displayed in the modal.
-![markdown-3](./images/markdown-3.png)
-
 ### Inline images and video
 
 You can inline images and videos in the report description, comments and report summary by writing the attachment reference id within curly braces (as in {F:id}).
 
 Example: For the above attachment, the markdown:
 
-
 ```
- Here is an inlined image of an apple {F1}
+{F1}
 ```
 
 will render the following: