Skip to content

Commit ffcb5da

Browse files
authored
Fix grammar
1 parent cf33b67 commit ffcb5da

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

2-ui/2-events/04-default-browser-action/article.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ There are two ways to tell the browser we don't want it to act:
1717
- The main way is to use the `event` object. There's a method `event.preventDefault()`.
1818
- If the handler is assigned using `on<event>` (not by `addEventListener`), then returning `false` also works the same.
1919

20-
In this HTML a click on a link doesn't lead to navigation, browser doesn't do anything:
20+
In this HTML, a click on a link doesn't lead to navigation; the browser doesn't do anything:
2121

2222
```html autorun height=60 no-beautify
2323
<a href="/" onclick="return false">Click here</a>
@@ -96,7 +96,7 @@ That's because the browser action is canceled on `mousedown`. The focusing is st
9696

9797
The optional `passive: true` option of `addEventListener` signals the browser that the handler is not going to call `preventDefault()`.
9898

99-
Why that may be needed?
99+
Why might that be needed?
100100

101101
There are some events like `touchmove` on mobile devices (when the user moves their finger across the screen), that cause scrolling by default, but that scrolling can be prevented using `preventDefault()` in the handler.
102102

0 commit comments

Comments
 (0)