Skip to content

Commit

Permalink
docs: fix scroll position of History Object (#9062)
Browse files Browse the repository at this point in the history
  • Loading branch information
yuleicul committed Jul 15, 2022
1 parent 334589b commit 912ba86
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 1 deletion.
1 change: 1 addition & 0 deletions contributors.yml
Expand Up @@ -72,3 +72,4 @@
- vijaypushkin
- vikingviolinist
- xcsnowcity
- yuleicul
2 changes: 1 addition & 1 deletion docs/getting-started/concepts.md
Expand Up @@ -35,7 +35,7 @@ Here are some words we use a lot when we talk about React Router. The rest of th

- <a id="csr">**Client Side Routing (CSR)**</a> - A plain HTML document can link to other documents and the browser handles the [history stack](#history-stack) itself. Client Side Routing enables developers to manipulate the browser history stack without making a document request to the server.

- <a id="history-object">**History**</a> - An object that allows React Router to subscribe to changes in the [URL](#url) as well as providing APIs to manipulate the browser [history stack](#history-stack) programmatically.
- <a id="history">**History**</a> - An object that allows React Router to subscribe to changes in the [URL](#url) as well as providing APIs to manipulate the browser [history stack](#history-stack) programmatically.

- <a id="history-action">**History Action**</a> - One of `POP`, `PUSH`, or `REPLACE`. Users can arrive at a [URL](#url) for one of these three reasons. A push when a new entry is added to the history stack (typically a link click or the programmer forced a navigation). A replace is similar except it replaces the current entry on the stack instead of pushing a new one. Finally, a pop happens when the user clicks the back or forward buttons in the browser chrome.

Expand Down

0 comments on commit 912ba86

Please sign in to comment.