fixed typo, the word 'familiar' spelled incorrectly (#1279)

* fixed typo, the word 'familiar' spelled incorrectly

* fixed typo

CONTRIBUTING.md

@@ -12,7 +12,7 @@ The animations in Animate.css should follow a few key principles:
 - **Animations should be tolerable.** Related to subtlety, animations should be tolerable—seeing them repeatedly should not become too annoying or overbearing.
 - **Animations should not interfere with document flow or control/input availability.** In other words, the absence of an animation should never reduce usability of a product: they should be non-critical and seen as “progressive enhancements”. Avoid animations that change properties such as `position` or `display`.
 - **Animations should be helpful.** They should be designed to guide users to a point of interest, ease natural reading order, or to communicate relationships between elements.
-- **Animations should feel familial.** Avoid introducing animations that feel out-of-place compared to the existing set.
+- **Animations should feel familiar.** Avoid introducing animations that feel out-of-place compared to the existing set.
 - **Animations should feel natural.** Animations should reflect, as much as is reasonable, motion that occurs in natural physics. Avoid extreme timing functions, and model animations on real-world events.
 
 ## Code Styling
@@ -27,5 +27,5 @@ The animations in Animate.css should follow a few key principles:
 1. [Fork](https://help.github.com/articles/fork-a-repo/) the project
 2. Create a new topic branch on your local forked copy
 3. Push your topic branch up to your fork
-4. Create a [pen](https://codepen.io/) demonstrating what yor change will do.
+4. Create a [pen](https://codepen.io/) demonstrating what your change will do.
 5. [Open a Pull Request](https://help.github.com/articles/about-pull-requests/) with a clear title and description against the `main` branch.