<commit_before># Slate Syntax

## Headers

For headers:

    # Level 1 Header
    ## Level 2 Header
    ### Level 3 Header

Note that only level 1 and 2 headers will appear in the table of contents.

## Paragraph Text

For normal text, just type your paragraph on a single line.

    This is some paragraph text. Exciting, no?

Make sure the lines above below your paragraph are empty.

## Code Samples

For code samples:

    ```ruby
    # This is some Ruby code!
    ```

    ```python
    // This is some Python code!
    ```

Code samples will appear in the dark area to the left of the main text. We recommend positioning code samples right under headers in your markdown file.

For the full list of supported languages, see [rouge](http://rouge.jayferd.us/demo).

## Code Annotations

For code annotations:

    ```ruby
    # This is some Ruby code!
    ```

    > This is a code annotation. It will appear in the area to the right, next to the code samples.

    ```ruby
    # This is some more Ruby code!
    ```

Code annotations are essentially the same thing as paragraphs, but they'll appear in the area to the right along with your code samples.

## Tables

Slate uses PHP Markdown Extra style tables:

```markdown
Table Header 1 | Table Header 2 | Table Header 3
-------------- | -------------- | --------------
Row 1 col 1 | Row 1 col 2 | Row 1 col 3
Row 2 col 1 | Row 2 col 2 | Row 2 col 3
```

Note that the pipes do not need to line up with each other on each line.

If you don't like that syntax, feel free to use normal html `<table>`s directly in your markdown.

## Formatting Text:

    This text is ***bold***, this is **italic**, this is an `inline code block`.<commit_msg>Fix incorrect instructions in syntax help file<commit_after># Slate Syntax

## Headers

For headers:

    # Level 1 Header
    ## Level 2 Header
    ### Level 3 Header

Note that only level 1 and 2 headers will appear in the table of contents.

## Paragraph Text

For normal text, just type your paragraph on a single line.

    This is some paragraph text. Exciting, no?

Make sure the lines above below your paragraph are empty.

## Code Samples

For code samples:

    ```ruby
    # This is some Ruby code!
    ```

    ```python
    // This is some Python code!
    ```

Code samples will appear in the dark area to the left of the main text. We recommend positioning code samples right under headers in your markdown file.

For the full list of supported languages, see [rouge](http://rouge.jayferd.us/demo).

## Code Annotations

For code annotations:

    ```ruby
    # This is some Ruby code!
    ```

    > This is a code annotation. It will appear in the area to the right, next to the code samples.

    ```ruby
    # This is some more Ruby code!
    ```

Code annotations are essentially the same thing as paragraphs, but they'll appear in the area to the right along with your code samples.

## Tables

Slate uses PHP Markdown Extra style tables:

```markdown
Table Header 1 | Table Header 2 | Table Header 3
-------------- | -------------- | --------------
Row 1 col 1 | Row 1 col 2 | Row 1 col 3
Row 2 col 1 | Row 2 col 2 | Row 2 col 3
```

Note that the pipes do not need to line up with each other on each line.

If you don't like that syntax, feel free to use normal html `<table>`s directly in your markdown.

## Formatting Text:

    This text is **bold**, this is *italic*, this is an `inline code block`.
{'fraction_non_alphanumeric': 0.09640666082383874, 'fraction_numerical': 0.011685655857435, 'mean_word_length': 2.750273822562979, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 7, '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': '5159320', 'n_tokens_mistral': 1006, 'n_tokens_neox': 911, 'n_words': 531}