Skip to content

Commit

Permalink
Fix a grammatical error
Browse files Browse the repository at this point in the history
  • Loading branch information
hiradary authored Jul 11, 2020
1 parent bd14c90 commit 43a3966
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ This is the most commonly adopted approach. However, I believe it has a few draw
- More boilerplate code. If you were to have 3 modals in a page, you had to use Modal component three times, declare more and more variables to handle visibility, etc.
- Unlike reoverlay, you can't manage your modals outside React scope (e.g Store). Though it's not generally a good practice to manage modals/overlays outside React scope, It comes in handy in some cases. (e.g Using axios interceptors to show modals according to network status, access control, etc.)

<strong>Reoverlay</strong>, on the other hand, offers a rather more readable and easy approach. You'll be given a top-level modal component (`ModalContainer`), and a few APIs to handle triggering hide/show. Check [usage](#usage-) to see how it works.
<strong>Reoverlay</strong>, on the other hand, offers a rather more readable and easier approach. You'll be given a top-level modal component (`ModalContainer`), and a few APIs to handle triggering hide/show. Check [usage](#usage-) to see how it works.

## Usage 🎯

Expand Down

0 comments on commit 43a3966

Please sign in to comment.