Skip to content

Commit adf83c6

Browse files
authored
Update article.md
1 parent 80eb70f commit adf83c6

File tree

1 file changed

+1
-1
lines changed
  • 1-js/12-generators-iterators/2-async-iterators-generators

1 file changed

+1
-1
lines changed

1-js/12-generators-iterators/2-async-iterators-generators/article.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -363,7 +363,7 @@ More explanations about how it works:
363363
- The initial URL is `https://api.github.com/repos/<repo>/commits`, and the next page will be in the `Link` header of the response.
364364
- The `fetch` method allows us to supply authorization and other headers if needed -- here GitHub requires `User-Agent`.
365365
2. The commits are returned in JSON format.
366-
3. We should get the next page URL from the `Link` header of the response. It has a special format, so we use a regular expression for that (we will lern this feature in [Regular expressions](info:regular-expressions)).
366+
3. We should get the next page URL from the `Link` header of the response. It has a special format, so we use a regular expression for that (we will learn this feature in [Regular expressions](info:regular-expressions)).
367367
- The next page URL may look like `https://api.github.com/repositories/93253246/commits?page=2`. It's generated by GitHub itself.
368368
4. Then we yield the received commits one by one, and when they finish, the next `while(url)` iteration will trigger, making one more request.
369369

0 commit comments

Comments
 (0)