We've got our issue, Python track courses to be completed and

now let's add a description and make use of the markdown formatting.

Documentation for markdown is linked here, so let's take a look at it.

This link is also in the teacher's notes.

So it looks like there's an intro and some examples.

Let's see the examples.

We can see that using the double asterisk makes a word bold and

using one asterisk makes the word italic.

To create a link, you use brackets and the URL in parentheses.

There are additional examples of how to create

a numbered list and a bulleted list.

How to embed an image.

Use Headers and Quotes.

Style Code.

And also, how to create task lists and use emoji.

We'll use most of these in our issue.

Back in our issue body,

I'll add the equivalent of an h2 tag with two hashes and type TODO.

I can preview it to make sure it looks like I want it to.

Looks good.

Next, I'll add some italics.

I'll use a task list to check the remaining courses to be completed.

And I'll add some emoji to show my excitement.

There's also a link to the emoji cheat sheet in the teachers notes with a list of

all the emojis supported on GitHub.

Last by typing an at symbol followed a username,

you can notify a person to come and view the comment, also called an at mention.

I'll CC my friend Kyle since he said,

he was interested to know what courses I'm taking.

We'll Preview.

Awesome, it looks great and click Submit new Issue.

When I finish my courses, I'll check them off.

And eventually, close the issue when the tasks are all completed.

Also, cool is every issue has a unique URL that I can send to someone and go back and

reference even after the issue is closed.

Back in the Issues view, we can see that we've got our two open issues.

To review,

you can open an issue to create a note of something related to your repository and

we learned how to effectively use Markdown to style our text.

In the next video,

we'll talk about a best practice as a work flow to make changes to a project.