fix typo: hanlde -> handle

Author: junhoyeo

docs/figma-autolayout.md

@@ -144,6 +144,6 @@ We use Stretched Token for specifing specific widget to be stretched. Learn more
 ## Hug contents item (Not having any intrinsic size)
 
 > Hug contents will follow its items size, not having a intrinsic size of its own.
-> Learn how to hanlde this here at [box-sizing#Not having-any-intrinsic-size](./css-box-sizing.md)
+> Learn how to handle this here at [box-sizing#Not having-any-intrinsic-size](./css-box-sizing.md)
 
 <!-- Code examples WIP -->

editor/pages/figma/inspect-component.tsx

@@ -32,7 +32,7 @@ export default function InspectComponent() {
       <div style={{ margin: 60 }}>
         <h2>Not a component</h2>
         <p>
-          This page cannot hanlde other types than <code>COMPONENT</code> or
+          This page cannot handle other types than <code>COMPONENT</code> or
           <code>INSTANCE</code>
         </p>
         <p>

packages/builder-web-react/react-styled-component-widget/from-reusable-widget-tree.ts

@@ -19,9 +19,9 @@ export function finalizeReactReusable_StyledComponents__Experimental({
   tree: InstanceWidget;
   components: MasterComponentWidget[];
 }) {
-  const hanlde = (token) => {
+  const handle = (token) => {
     if (token instanceof InstanceMetaToken) {
-      const children = token.master["children"]?.map(hanlde);
+      const children = token.master["children"]?.map(handle);
       return {
         ...token.master,
         children,
@@ -31,7 +31,7 @@ export function finalizeReactReusable_StyledComponents__Experimental({
     }
   };
 
-  const token = hanlde(tree);
+  const token = handle(tree);
   const webwi = compose(token, {});
   const builder = new ReactStyledComponentsModuleBuilder({
     entry: webwi,

packages/designto-token/README.md

@@ -28,9 +28,9 @@ For example,
 In this scenario, regardingless how much single pltform's design is exceptional, the data should follow the hierarchical shape to satisfy all platfrom.
 
 **The reason is..**
-all the processing logic should be handled on tokenizer and the tokens are the result of the decision tree. No heavy, decision changing logic should be hanlded after the tokenization.
+all the processing logic should be handled on tokenizer and the tokens are the result of the decision tree. No heavy, decision changing logic should be handled after the tokenization.
 
-e.g. All design elements has its position, but not all nodes are being placed statically on that posision. by wrapping (not as property) the position, we can tell the later hanlders that this is already decided to be positioned and have its static posision specified. - if we don't do this way each logic by frameworks will be fragmented and unable to maintain.
+e.g. All design elements has its position, but not all nodes are being placed statically on that posision. by wrapping (not as property) the position, we can tell the later handlers that this is already decided to be positioned and have its static posision specified. - if we don't do this way each logic by frameworks will be fragmented and unable to maintain.
 
 ### The first approach (noisy and accurate one)