Markdown basics

Headings

Heading 1

#Heading 1   or   <h1>Heading 1</h1>

Heading 2

##Heading 2   or   <h2>Heading 2</h2>

Heading 3

###Heading 3   or   <h3>Heading 3</h3>

Heading 4

####Heading 4   or   <h4>Heading 4</h4>

Heading 5

#####Heading 5   or   <h5>Heading 5</h5>

Heading 6

######Heading 6   or   <h6>Heading 6</h6>

Styling text

You can indicate emphasis with bold, italic, or strikethrough text.

• Bold
  
**Bold** or __Bold__

• Italic
  
*Italic* or _Italic_

• Strikethrough
  
Strikethrough
  
• Bold and Italic
  
**Bold and _Italic_**


Quotation

Quoting text

In the words of Abraham Lincoln:

Pardon my French

In the words of Abraham Lincoln:
>Pardon my French

Quoting code

• Inline quotation
  Use git status to list all new or modified files that haven’t yet been committed.
  
Use `git status` to list all new or modified files that haven't yet been committed.

• Block quotation
  Some basic Git commands are:
  
git status
git add
git commit


    Some basic Git commands are:
    ```
    git status
    git add
    git commit
    ```

Syntax highlighting for block quotation

int main()
{
    cout << "Hello World!" << endl;
    return 0;
}

    ```cpp/ruby/php/python/javascript ...
    your cpp code
    ```

We use Linguist to perform language detection and syntax highlighting. You can find out which keywords are valid in the languages YAML file.

Lists

Unordered list

You can make a list by preceding one or more lines of text with - or *.

• Item 1
• Item 2
• Item 3

- Item 1 or * Item 1 - Item 2 or * Item 2 - Item 3 or * Item 3

Ordered list

1. Item 1
2. Item 2
3. Item 3

1. Item 1
2. Item 2
3. Item 3

NOTE: pay attention to .

Nested list

1. Make my changes
   
   • Fix bug
   • Improve formatting
     
     • Make the headings bigger
2. Push my commits to GitHub
3. Open a pull request
   
   • Describe my changes
   • Mention all the members of my team
     
     • Ask for feedback

1. Make my changes
  - Fix bug
  - Improve formatting
      - Make the headings bigger
2. Push my commits to GitHub
3. Open a pull request
  * Describe my changes
  * Mention all the members of my team
     * Ask for feedback