Skip to content

Commit 40074e0

Browse files
authored
Merge pull request #964 from rezyx/fix-github-casing
Fix GitHub casing (04-promise-error-handling/article.md
2 parents ed86221 + de5059f commit 40074e0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

1-js/11-async/04-promise-error-handling/article.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,7 @@ Let's improve error handling for the user-loading example.
169169

170170
The promise returned by [fetch](mdn:api/WindowOrWorkerGlobalScope/fetch) rejects when it's impossible to make a request. For instance, a remote server is not available, or the URL is malformed. But if the remote server responds with error 404, or even error 500, then it's considered a valid response.
171171

172-
What if the server returns a non-JSON page with error 500 in the line `(*)`? What if there's no such user, and github returns a page with error 404 at `(**)`?
172+
What if the server returns a non-JSON page with error 500 in the line `(*)`? What if there's no such user, and GitHub returns a page with error 404 at `(**)`?
173173

174174
```js run
175175
fetch('no-such-user.json') // (*)
@@ -219,7 +219,7 @@ The great thing about having our own class for errors is that we can easily chec
219219

220220
For instance, we can make a request, and then if we get 404 -- ask the user to modify the information.
221221

222-
The code below loads a user with the given name from github. If there's no such user, then it asks for the correct name:
222+
The code below loads a user with the given name from GitHub. If there's no such user, then it asks for the correct name:
223223

224224
```js run
225225
function demoGithubUser() {

0 commit comments

Comments
 (0)