Skip to content

Commit

Permalink
fix: README typos (#392)
Browse files Browse the repository at this point in the history
  • Loading branch information
baahrens committed Sep 21, 2020
1 parent f9f1df5 commit ca5dda1
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
- [Vanilla JS Example](https://stackblitz.com/edit/vest-vanilla-support-example?file=validation.js)
- ReactJS Examples:
- [Example 1 (groups)](https://codesandbox.io/s/ecstatic-waterfall-4i2ne?file=/src/validate.js)
- [Exmaple 2 (Async)](https://codesandbox.io/s/youthful-williamson-loijb?file=/src/validate.js)
- [Example 2 (Async)](https://codesandbox.io/s/youthful-williamson-loijb?file=/src/validate.js)
- [Example 3](https://stackblitz.com/edit/vest-react-support-example?file=validation.js)
- [Example 4](https://stackblitz.com/edit/vest-react-registration?file=validate.js)
- [VueJS Example](https://codesandbox.io/s/vest-vue-example-1j6r8?file=/src/validations.js)
Expand All @@ -27,7 +27,7 @@ It works great with user-input validation and with validating upon user interact

The idea behind Vest is that your validations can be described as a 'spec' or a contract that reflects your form or feature structure. Your validations run in production, and they are framework agnostic - meaning Vest works well with React, Angular, Vue, or even without a framework at all.

Using Vest for form validation can reduce bloat, improve feature redability and maintainability.
Using Vest for form validation can reduce bloat, improve feature readability and maintainability.

**Basic Example**
![full](https://cdn.jsdelivr.net/gh/ealush/vest@assets/demos/full_3.gif 'full')
Expand Down

0 comments on commit ca5dda1

Please sign in to comment.