Skip to content

Commit b84c9ea

Browse files
author
Gabe Rosenhouse
committed
Fixed formatting of curl commands
Use of <pre> with embedded <username> or <token> messed up the rendering (see http://developer.github.com/v3/auth/#working-with-two-factor-authentication)
1 parent ab49fe8 commit b84c9ea

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

content/v3/auth.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,8 @@ For example, if you're accessing the API via [cURL][curl], the following command
3333
would authenticate you if you replace `<username>` with your GitHub username.
3434
(cURL will prompt you to enter the password.)
3535

36-
<pre class='terminal'>
37-
curl -u <username> https://api.github.com/user
38-
</pre>
36+
curl -u <username> https://api.github.com/user
37+
3938

4039
### Via OAuth Tokens
4140

@@ -45,9 +44,7 @@ the username and provide a blank password or a password of `x-oauth-basic`. If
4544
you're accessing the API via cURL, replace `<token>` with your OAuth token in
4645
the following command:
4746

48-
<pre class='terminal'>
49-
curl -u <token>:x-oauth-basic https://api.github.com/user
50-
</pre>
47+
curl -u <token>:x-oauth-basic https://api.github.com/user
5148

5249
This approach is useful if your tools only support Basic Authentication but you
5350
want to take advantage of OAuth access token security features.

0 commit comments

Comments
 (0)