# Appendix: Markdown

## Headings

```
# Heading Level 1
## Heading Level 2
### Heading Level 3
```

## Unordered List

```
* item 1
* item 2
    * first subitem of item 2
    * second subitem of item 2
```

Above creates the following

* item 1
* item 2
  * first subitem of item 2
  * second subitem of item 2

## Ordered List

```
1. item 1
1. item 2
    1. first subitem of item 2
    1. second subitem of item 2
```

Above creates this.  Note that the number before the dot is irrelevant.  Markdown will automatically number it for you.

1. item 1
2. item 2
   1. first subitem of item 2
   2. second subitem of item 2

## Tables

To make a table:

```
| heading 1 | heading 2 |
|---|---|
|col 1, row1|col2 row 1|
|col 1, row2|col2 row 2|
```

creates:

| heading 1 | heading 2  |
| --------- | ---------- |
| col1,row1 | col2 row 1 |
| co1, row2 | col2 row 2 |

## Code

````
 ```language name
    code goes here
 ```

````

## For pretty math formulas

the only way to make your mathematical formulas look good is to use LaTex.  You can do this if you wish but its not necessary.  To put a mathematical formula written in LaTex into your wiki, you can use google charts api.  You create an image link tag and then fill link it to a call the the charts api.  For example:

```
...
![formula]
... rest of your page
...
[formula]: http://chart.apis.google.com/chart?cht=tx&chl=LaTex_Formatted_Expression
```

For example:

```
...
![formula]
... rest of your page
...
[formula]: http://chart.apis.google.com/chart?cht=tx&chl=3n%2B4
```

this would produce following in your wiki page where you have !\[formula]

 $$3n+4$$ 


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://catherine-leung.gitbook.io/data-strutures-and-algorithms/appendix-markdown.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.