Skip to content

Commit eabd5e5

Browse files
docs: typos (#370)
1 parent 9badff2 commit eabd5e5

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

explainer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ This repo outlines an API that can be used to understand movement of DOM element
66

77
## Observing Position
88

9-
The web's traditional position calculation mechanisms rely on explicit queries of DOM state. Some of these are known to cause style recalcuation and layout and, frequently, are redundant thanks to the requirement that scripts poll for this information.
9+
The web's traditional position calculation mechanisms rely on explicit queries of DOM state. Some of these are known to cause style recalculation and layout and, frequently, are redundant thanks to the requirement that scripts poll for this information.
1010

1111
A body of common practice has evolved that relies on these behaviors, however, including (but not limited to):
1212

@@ -164,7 +164,7 @@ function init() {
164164
// Notify when a scroll-item gets within, or moves beyond, 500px from the visible scroll surface.
165165
var opts = {
166166
root: document.querySelector(".container"),
167-
rootMargin: "500px 0px"
167+
rootMargin: "500px 0px"
168168
};
169169
var observer = new IntersectionObserver(manageItemPositionChanges, opts);
170170
// Set up observer on the items

polyfill/README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -61,16 +61,16 @@ There are, however, additional use cases that the default configuration will not
6161

6262
If you need to handle any of these use-cases, you can configure the polyfill to poll the document by setting the `POLL_INTERVAL` property. This can be set either globally or on a per-instance basis.
6363

64-
**Enabling polling for all instance:**
64+
**Enabling polling for all instances:**
6565

66-
To enable polling for all instance, set a value for `POLL_INTERVAL` on the `IntersectionObserver` prototype:
66+
To enable polling for all instances, set a value for `POLL_INTERVAL` on the `IntersectionObserver` prototype:
6767

6868

6969
```js
7070
IntersectionObserver.prototype.POLL_INTERVAL = 100; // Time in milliseconds.
7171
```
7272

73-
**Enabling polling for individual instance:**
73+
**Enabling polling for individual instances:**
7474

7575
To enable polling on only specific instances, set a `POLL_INTERVAL` value on the instance itself:
7676

@@ -94,7 +94,7 @@ var io = new IntersectionObserver(callback);
9494
io.USE_MUTATION_OBSERVER = false;
9595
```
9696

97-
This is recommended in cases where the DOM will update frequently but you know those updates will have no affect on the position or your target elements.
97+
This is recommended in cases where the DOM will update frequently but you know those updates will have no effect on the position or your target elements.
9898

9999

100100
## iframe support
@@ -171,7 +171,7 @@ Legacy support is also possible in very old browsers by including a shim for ES5
171171
<script src="https://polyfill.io/v3/polyfill.min.js?features=IntersectionObserver"></script>
172172
```
173173

174-
With these polyfills, `IntersectionObserver` has been tested an known to work in the following browsers:
174+
With these polyfills, `IntersectionObserver` has been tested and known to work in the following browsers:
175175

176176
<table>
177177
<tr>
@@ -210,4 +210,4 @@ With these polyfills, `IntersectionObserver` has been tested an known to work in
210210

211211
To run the test suite for the `IntersectionObserver` polyfill, open the [`intersection-observer-test.html`](./intersection-observer-test.html) page in the browser of your choice.
212212

213-
If you run the tests in a browser that support `IntersectionObserver` natively, the tests will be run against the native implementation. If it doesn't the tests will be run against the polyfill.
213+
If you run the tests in a browser that supports `IntersectionObserver` natively, the tests will be run against the native implementation. If it doesn't, the tests will be run against the polyfill.

0 commit comments

Comments
 (0)