Skip to content

Commit 2350e56

Browse files
authored
Merge pull request #537 from cha147/patch-1
fix typos in readme
2 parents 000358e + 46aeab2 commit 2350e56

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,13 +9,13 @@ An automatic web page progress bar.
99

1010
Include [pace.js](https://cdn.jsdelivr.net/npm/pace-js@latest/pace.min.js) and the
1111
[theme](https://codebyzach.github.io/pace/) css of your choice on your page
12-
(as early as is possible), and you're done!
12+
(as early as possible), and you're done!
1313

1414
Pace will automatically monitor your ajax requests, event loop lag, document
1515
ready state, and elements on your page to decide the progress. On ajax navigation
1616
it will begin again!
1717

18-
If you use AMD or Browserify, require pace.js and call `pace.start()` as early in the loading process as is possible.
18+
If you use AMD or Browserify, require pace.js and call `pace.start()` as early in the loading process as possible.
1919

2020
Example
2121
-------
@@ -90,7 +90,7 @@ Collectors are the bits of code which gather progress information. Pace includes
9090

9191
- Elements
9292

93-
Checks for the existance of specific elements on the page
93+
Checks for the existence of specific elements on the page
9494

9595
- Document
9696

@@ -123,7 +123,7 @@ Elements
123123

124124
Elements being rendered to the screen is one way for us to decide that the page has been
125125
rendered. If you would like to use that source of information (not required at all),
126-
specify one or more selectors. You can comma separate the selectors to propertly handle
126+
specify one or more selectors. You can comma separate the selectors to properly handle
127127
error states, where the progress bar should disappear, but the element we are looking for
128128
may never appear:
129129

0 commit comments

Comments
 (0)