From 92b34a76a2d739d0f5cbed1cbf49fdd8ac04f23c Mon Sep 17 00:00:00 2001
From: Subash-Lamichhane <109226874+Subash-Lamichhane@users.noreply.github.com>
Date: Fri, 13 Oct 2023 13:03:58 +0545
Subject: [PATCH] fixed typo in
 docs\docs\contributor\frontend\advanced\best-practices.mdx (#1993)

---
 docs/docs/contributor/frontend/advanced/best-practices.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/docs/contributor/frontend/advanced/best-practices.mdx b/docs/docs/contributor/frontend/advanced/best-practices.mdx
index 97f9a4edc..a1cdcac6f 100644
--- a/docs/docs/contributor/frontend/advanced/best-practices.mdx
+++ b/docs/docs/contributor/frontend/advanced/best-practices.mdx
@@ -237,7 +237,7 @@ const Form = () => <EmailField value="username@email.com" />;
 
 ## Component as props
 
-Try as much as possible to pass uninstanciated components as props, so chilren can decide on their own of what props they need to pass.
+Try as much as possible to pass uninstanciated components as props, so children can decide on their own of what props they need to pass.
 
 The most common example for that is icon components: 
 
@@ -256,7 +256,7 @@ const MyComponent = ({ MyIcon }: { MyIcon: IconComponent }) => {
 };
 ```
 
-For React to understand that the component is a component, you need to use PascalCase, to later instanciate it with `<MyIcon>`
+For React to understand that the component is a component, you need to use PascalCase, to later instantiate it with `<MyIcon>`
 
 ## Prop Drilling: Keep It Minimal