chore(i18n,docs): processed translations (#45518)

docs/i18n/chinese-traditional/how-to-work-on-the-component-library.md

@@ -15,7 +15,7 @@ The following steps are recommended when working on a new component:
 
 ## Researching and planning
 
-Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accesibility requirements, you should also pay attention to the accessibility aspect of the components, see which HTML elements and ARIA attributes are used under the hood.
+Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accessibility requirements, you should also pay attention to the accessibility aspect of the component, see which HTML elements and ARIA attributes are used under the hood.
 
 Once you have gathered enough information about the component, you can start thinking about the props interface. Ideally, the interface should be as similar to the current version as possible, to ease the adoption later on. Since we are using Bootstrap components, the simplest approach is to mimic [their implementation](https://github.com/react-bootstrap/react-bootstrap/tree/master/src).
 
@@ -43,11 +43,11 @@ The command will generate a new folder inside the `ui-components` directory, wit
 | `my-component.tsx`         | It is where we implement the component.                |
 | `types.ts`                 | Is is where we locate component's interface and types. |
 
-Each component is different, but in general the components should:
+Each component is different, but in general a component should:
 
 - Support forwarding ref
 - Be styled for both light and dark themes
-- Be styled internally based on their props (the consumers should not need to restyle the components with the `className` prop)
+- Be styled internally based on their props (the consumers should not need to restyle the component with the `className` prop)
 - Utilize the built-in styling system from Tailwind instead of having custom styles
 
 ### Useful links

docs/i18n/chinese/how-to-work-on-the-component-library.md

@@ -15,7 +15,7 @@ The following steps are recommended when working on a new component:
 
 ## Researching and planning
 
-Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accesibility requirements, you should also pay attention to the accessibility aspect of the components, see which HTML elements and ARIA attributes are used under the hood.
+Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accessibility requirements, you should also pay attention to the accessibility aspect of the component, see which HTML elements and ARIA attributes are used under the hood.
 
 Once you have gathered enough information about the component, you can start thinking about the props interface. Ideally, the interface should be as similar to the current version as possible, to ease the adoption later on. Since we are using Bootstrap components, the simplest approach is to mimic [their implementation](https://github.com/react-bootstrap/react-bootstrap/tree/master/src).
 
@@ -43,11 +43,11 @@ The command will generate a new folder inside the `ui-components` directory, wit
 | `my-component.tsx`         | It is where we implement the component.                |
 | `types.ts`                 | Is is where we locate component's interface and types. |
 
-Each component is different, but in general the components should:
+Each component is different, but in general a component should:
 
 - Support forwarding ref
 - Be styled for both light and dark themes
-- Be styled internally based on their props (the consumers should not need to restyle the components with the `className` prop)
+- Be styled internally based on their props (the consumers should not need to restyle the component with the `className` prop)
 - Utilize the built-in styling system from Tailwind instead of having custom styles
 
 ### Useful links

docs/i18n/espanol/how-to-work-on-the-component-library.md

@@ -15,7 +15,7 @@ The following steps are recommended when working on a new component:
 
 ## Researching and planning
 
-Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accesibility requirements, you should also pay attention to the accessibility aspect of the components, see which HTML elements and ARIA attributes are used under the hood.
+Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accessibility requirements, you should also pay attention to the accessibility aspect of the component, see which HTML elements and ARIA attributes are used under the hood.
 
 Once you have gathered enough information about the component, you can start thinking about the props interface. Ideally, the interface should be as similar to the current version as possible, to ease the adoption later on. Since we are using Bootstrap components, the simplest approach is to mimic [their implementation](https://github.com/react-bootstrap/react-bootstrap/tree/master/src).
 
@@ -43,11 +43,11 @@ The command will generate a new folder inside the `ui-components` directory, wit
 | `my-component.tsx`         | It is where we implement the component.                |
 | `types.ts`                 | Is is where we locate component's interface and types. |
 
-Each component is different, but in general the components should:
+Each component is different, but in general a component should:
 
 - Support forwarding ref
 - Be styled for both light and dark themes
-- Be styled internally based on their props (the consumers should not need to restyle the components with the `className` prop)
+- Be styled internally based on their props (the consumers should not need to restyle the component with the `className` prop)
 - Utilize the built-in styling system from Tailwind instead of having custom styles
 
 ### Useful links

docs/i18n/german/how-to-work-on-the-component-library.md

@@ -15,7 +15,7 @@ The following steps are recommended when working on a new component:
 
 ## Researching and planning
 
-Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accesibility requirements, you should also pay attention to the accessibility aspect of the components, see which HTML elements and ARIA attributes are used under the hood.
+Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accessibility requirements, you should also pay attention to the accessibility aspect of the component, see which HTML elements and ARIA attributes are used under the hood.
 
 Once you have gathered enough information about the component, you can start thinking about the props interface. Ideally, the interface should be as similar to the current version as possible, to ease the adoption later on. Since we are using Bootstrap components, the simplest approach is to mimic [their implementation](https://github.com/react-bootstrap/react-bootstrap/tree/master/src).
 
@@ -43,11 +43,11 @@ The command will generate a new folder inside the `ui-components` directory, wit
 | `my-component.tsx`         | It is where we implement the component.                |
 | `types.ts`                 | Is is where we locate component's interface and types. |
 
-Each component is different, but in general the components should:
+Each component is different, but in general a component should:
 
 - Support forwarding ref
 - Be styled for both light and dark themes
-- Be styled internally based on their props (the consumers should not need to restyle the components with the `className` prop)
+- Be styled internally based on their props (the consumers should not need to restyle the component with the `className` prop)
 - Utilize the built-in styling system from Tailwind instead of having custom styles
 
 ### Useful links

docs/i18n/italian/how-to-work-on-the-component-library.md

@@ -15,7 +15,7 @@ The following steps are recommended when working on a new component:
 
 ## Researching and planning
 
-Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accesibility requirements, you should also pay attention to the accessibility aspect of the components, see which HTML elements and ARIA attributes are used under the hood.
+Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accessibility requirements, you should also pay attention to the accessibility aspect of the component, see which HTML elements and ARIA attributes are used under the hood.
 
 Once you have gathered enough information about the component, you can start thinking about the props interface. Ideally, the interface should be as similar to the current version as possible, to ease the adoption later on. Since we are using Bootstrap components, the simplest approach is to mimic [their implementation](https://github.com/react-bootstrap/react-bootstrap/tree/master/src).
 
@@ -43,11 +43,11 @@ The command will generate a new folder inside the `ui-components` directory, wit
 | `my-component.tsx`         | It is where we implement the component.                |
 | `types.ts`                 | Is is where we locate component's interface and types. |
 
-Each component is different, but in general the components should:
+Each component is different, but in general a component should:
 
 - Support forwarding ref
 - Be styled for both light and dark themes
-- Be styled internally based on their props (the consumers should not need to restyle the components with the `className` prop)
+- Be styled internally based on their props (the consumers should not need to restyle the component with the `className` prop)
 - Utilize the built-in styling system from Tailwind instead of having custom styles
 
 ### Useful links

docs/i18n/japanese/how-to-work-on-the-component-library.md

@@ -15,7 +15,7 @@ The following steps are recommended when working on a new component:
 
 ## Researching and planning
 
-Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accesibility requirements, you should also pay attention to the accessibility aspect of the components, see which HTML elements and ARIA attributes are used under the hood.
+Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accessibility requirements, you should also pay attention to the accessibility aspect of the component, see which HTML elements and ARIA attributes are used under the hood.
 
 Once you have gathered enough information about the component, you can start thinking about the props interface. Ideally, the interface should be as similar to the current version as possible, to ease the adoption later on. Since we are using Bootstrap components, the simplest approach is to mimic [their implementation](https://github.com/react-bootstrap/react-bootstrap/tree/master/src).
 
@@ -43,11 +43,11 @@ The command will generate a new folder inside the `ui-components` directory, wit
 | `my-component.tsx`         | It is where we implement the component.                |
 | `types.ts`                 | Is is where we locate component's interface and types. |
 
-Each component is different, but in general the components should:
+Each component is different, but in general a component should:
 
 - Support forwarding ref
 - Be styled for both light and dark themes
-- Be styled internally based on their props (the consumers should not need to restyle the components with the `className` prop)
+- Be styled internally based on their props (the consumers should not need to restyle the component with the `className` prop)
 - Utilize the built-in styling system from Tailwind instead of having custom styles
 
 ### Useful links

docs/i18n/portuguese/how-to-work-on-the-component-library.md

@@ -15,7 +15,7 @@ São recomendados os seguintes passos ao trabalhar em um novo componente:
 
 ## Pesquisar e planejar
 
-Antes de construir um componente, você precisa pesquisar e documentar como a versão existente se comporta e qual é sua aparência, para garantir que o novo tenha estilos correspondentes e suporte todos os usos atuais. Para atender aos requisitos de acessibilidade da web, você também deve prestar atenção ao aspecto de acessibilidade dos componentes, ver quais elementos HTML e atributos ARIA são usados por baixo dos panos.
+Antes de construir um componente, você precisa pesquisar e documentar como a versão existente se comporta e qual é sua aparência, para garantir que o novo tenha estilos correspondentes e suporte todos os usos atuais. In order to meet the web accessibility requirements, you should also pay attention to the accessibility aspect of the component, see which HTML elements and ARIA attributes are used under the hood.
 
 Depois de coletar informações suficientes sobre o componente, você pode começar a pensar na interface de propriedades. Idealmente, a interface deveria ser o mais semelhante possível à versão atual, a fim de facilitar a adoção mais tarde. Como estamos usando componentes do Bootstrap, a abordagem mais simples é imitar a [implementação deles](https://github.com/react-bootstrap/react-bootstrap/tree/master/src).
 
@@ -43,11 +43,11 @@ O comando gerará uma nova pasta dentro do diretório `ui-components`, com os se
 | `my-component.tsx`         | É onde implementamos o componente.                                |
 | `types.ts`                 | É onde localizamos a interface e os tipos do componente.          |
 
-Cada componente é diferente, mas, em geral, os componentes deveriam:
+Each component is different, but in general a component should:
 
 - Dar suporte à ref de encaminhamento
 - Ser estilizados para temas claros e escuros
-- Ser estilizados internamente com base em suas propriedades (os consumidores não devem precisar reestilizar os componentes com a propriedade `className`)
+- Be styled internally based on their props (the consumers should not need to restyle the component with the `className` prop)
 - Usar o sistema de estilo integrado do Tailwind ao invés de ter estilos personalizados
 
 ### Links úteis

docs/i18n/ukrainian/how-to-work-on-the-component-library.md

@@ -15,7 +15,7 @@ The following steps are recommended when working on a new component:
 
 ## Researching and planning
 
-Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accesibility requirements, you should also pay attention to the accessibility aspect of the components, see which HTML elements and ARIA attributes are used under the hood.
+Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accessibility requirements, you should also pay attention to the accessibility aspect of the component, see which HTML elements and ARIA attributes are used under the hood.
 
 Once you have gathered enough information about the component, you can start thinking about the props interface. Ideally, the interface should be as similar to the current version as possible, to ease the adoption later on. Since we are using Bootstrap components, the simplest approach is to mimic [their implementation](https://github.com/react-bootstrap/react-bootstrap/tree/master/src).
 
@@ -43,11 +43,11 @@ The command will generate a new folder inside the `ui-components` directory, wit
 | `my-component.tsx`         | It is where we implement the component.                |
 | `types.ts`                 | Is is where we locate component's interface and types. |
 
-Each component is different, but in general the components should:
+Each component is different, but in general a component should:
 
 - Support forwarding ref
 - Be styled for both light and dark themes
-- Be styled internally based on their props (the consumers should not need to restyle the components with the `className` prop)
+- Be styled internally based on their props (the consumers should not need to restyle the component with the `className` prop)
 - Utilize the built-in styling system from Tailwind instead of having custom styles
 
 ### Useful links