mui · oliviertassinari · Mar 21, 2020 · Mar 21, 2020
diff --git a/docs/src/pages/components/about-the-lab/about-the-lab-de.md b/docs/src/pages/components/about-the-lab/about-the-lab-de.md
@@ -2,13 +2,13 @@
 
 <p class="description">Dieses Paket enthält die Inkubator-Komponenten, die noch nicht bereit sind, in den Kern aufgenommen zu werden.</p>
 
-The main difference between the lab and the core is how the components are versioned. Having a separate lab package allows us to release breaking changes when necessary while the core package follows a [slower-moving policy](https://material-ui.com/versions/#release-frequency).
+Der Hauptunterschied zwischen dem Labor und dem Kern besteht darin, wie die Komponenten versioniert werden. Having a separate lab package allows us to release breaking changes when necessary while the core package follows a [slower-moving policy](https://material-ui.com/versions/#release-frequency).
 
 As developers use and test the components and report issues, the maintainers learn more about shortcomings of the components: missing features, accessibility issues, bugs, API design, etc. The older and more used a component is, the less likely it is that new issues will be found and subsequently need to introduce breaking changes.
 
 For a component to be ready to move to the core, the following criteria are considered:
 
-* It needs to be **used**. The Material-UI team uses Google Analytics stats among other metrics to evaluate the usage of each component. A lab component with low usage either means that it isn't fully working yet or that there is a low demand for it.
+* Es muss **verwendet werden**. Das Material-UI-Team verwendet neben anderen Metriken Google Analytics Statistiken, um die Nutzung der einzelnen Komponenten zu bewerten. Eine Laborkomponente mit geringem Verbrauch bedeutet entweder, dass sie noch nicht vollständig funktioniert oder dass eine geringe Nachfrage besteht.
 * It needs to match the **code quality** of the core components. It doesn't have to be perfect to be a part of the core, but the component should be reliable enough that developers can depend on it. 
     * Each component needs **type definitions**. It is not currently required that a lab component is typed, but it would need to be typed to move to the core.
     * Requires good **test coverage**. Some of the lab components don't currently have comprehensive tests.
@@ -17,7 +17,7 @@ For a component to be ready to move to the core, the following criteria are cons
 
 ## Installation
 
-Install the package in your project directory with:
+Installieren Sie das Paket innerhalb des Projektordners mit:
 
 ```sh
 // mit npm

diff --git a/docs/src/pages/components/about-the-lab/about-the-lab-fr.md b/docs/src/pages/components/about-the-lab/about-the-lab-fr.md
@@ -2,7 +2,7 @@
 
 <p class="description">Ce package contient des composants en incubation (en développement) qui ne sont pas encore prêts à être ajoutés au package principal.</p>
 
-The main difference between the lab and the core is how the components are versioned. Having a separate lab package allows us to release breaking changes when necessary while the core package follows a [slower-moving policy](https://material-ui.com/versions/#release-frequency).
+La principale différence entre le laboratoire et le noyau est la façon dont les composants sont versionnés. Le fait de disposer d'un paquet de laboratoire séparé nous permet de publier les modifications de rupture si nécessaire, tandis que le paquet de base suit une [politique plus lente](https://material-ui.com/versions/#release-frequency).
 
 As developers use and test the components and report issues, the maintainers learn more about shortcomings of the components: missing features, accessibility issues, bugs, API design, etc. The older and more used a component is, the less likely it is that new issues will be found and subsequently need to introduce breaking changes.
 

diff --git a/docs/src/pages/components/about-the-lab/about-the-lab-pt.md b/docs/src/pages/components/about-the-lab/about-the-lab-pt.md
@@ -2,22 +2,22 @@
 
 <p class="description">Este pacote hospeda os componentes da incubadora que ainda não estão prontos para mover para o núcleo (core).</p>
 
-The main difference between the lab and the core is how the components are versioned. Having a separate lab package allows us to release breaking changes when necessary while the core package follows a [slower-moving policy](https://material-ui.com/versions/#release-frequency).
+A principal diferença entre o lab e o core (núcleo) é como os componentes são versionados. Tendo um pacote separado para o lab, podemos liberar alterações radicais quando necessário, enquanto o pacote do core segue uma [política de movimentação mais lenta](https://material-ui.com/versions/#release-frequency).
 
-As developers use and test the components and report issues, the maintainers learn more about shortcomings of the components: missing features, accessibility issues, bugs, API design, etc. The older and more used a component is, the less likely it is that new issues will be found and subsequently need to introduce breaking changes.
+À medida que os desenvolvedores usam, testam os componentes e relatam problemas, os mantenedores aprendem mais sobre as deficiências dos componentes: recursos ausentes, problemas de acessibilidade, bugs, design de API, etc. Quanto mais antigo e mais usado for um componente, menor é a probabilidade de novos problemas serem encontrados e, posteriormente, novas alterações radicais precisarão ser introduzidas.
 
-For a component to be ready to move to the core, the following criteria are considered:
+Para que um componente esteja pronto para ir para o core, são considerados os seguintes critérios:
 
-* It needs to be **used**. The Material-UI team uses Google Analytics stats among other metrics to evaluate the usage of each component. A lab component with low usage either means that it isn't fully working yet or that there is a low demand for it.
-* It needs to match the **code quality** of the core components. It doesn't have to be perfect to be a part of the core, but the component should be reliable enough that developers can depend on it. 
-    * Each component needs **type definitions**. It is not currently required that a lab component is typed, but it would need to be typed to move to the core.
-    * Requires good **test coverage**. Some of the lab components don't currently have comprehensive tests.
-* Can it be used as **leverage** to incentivize users to upgrade to the latest major release? The less fragmented the community is, the better.
-* It needs to have a low probability of a **breaking change** in the short/medium future. For instance, if it needs a new feature that will likely require a breaking change, it may be preferable to delay its promotion to the core.
+* Ele precisa ser **utilizado**. A equipe do Material-UI usa o Google Analytics e outras métricas para avaliar o uso de cada componente. Um componente do lab com baixo uso significa que ainda não está totalmente funcionando ou que há uma baixa demanda por ele.
+* Ele precisa corresponder à **qualidade de código** dos componentes principais. O componente não precisa ser perfeito para fazer parte do core, mas ele deve ser confiável o suficiente para que os desenvolvedores possam depender dele. 
+    * Cada componente precisa de **definições de tipo**. Atualmente, não é necessário que um componente do lab seja tipado, mas ele precisará ser tipado para passar para o core.
+    * Requer boa **cobertura de teste**. Atualmente, alguns dos componentes do lab não têm testes abrangentes.
+* O componente pode ser usado como **alavancagem** para incentivar os usuários a atualizar para a versão mais recente? Quanto menos fragmentada a comunidade, melhor.
+* Ele precisa ter uma baixa probabilidade de **alterações radicais** no curto/médio prazo. Por exemplo, se o componente precisar de um novo recurso que provavelmente precisará de alterações radicais, pode ser preferível adiar sua promoção para o core.
 
 ## Instalação
 
-Install the package in your project directory with:
+Instale o pacote no diretório do projeto com:
 
 ```sh
 // usando npm
@@ -27,7 +27,7 @@ npm install @material-ui/lab
 yarn add @material-ui/lab
 ```
 
-The lab has a peer dependency on the core components. If you are not already using Material-UI in your project, you can install it with:
+O lab tem dependências com os componentes do core. Se você ainda não está utilizando o Material-UI em seu projeto, poderá instalá-lo com:
 
 ```sh
 // usando npm

diff --git a/docs/src/pages/components/about-the-lab/about-the-lab-zh.md b/docs/src/pages/components/about-the-lab/about-the-lab-zh.md
@@ -2,22 +2,22 @@
 
 <p class="description">此依赖包包含了一些还在开发中的组件，它们还不能移到 core（核心）库中。</p>
 
-核心库（core）和实验室（lab）之间的主要差别就是组件是如何版本化的 Having a separate lab package allows us to release breaking changes when necessary while the core package follows a [slower-moving policy](https://material-ui.com/versions/#release-frequency).
+核心库（core）和实验室（lab）之间的主要差别就是组件是如何版本化的 拥有独立的实验室版本，我们就可以在必要的时候发布一些会影响原本代码的改动，并且核心库遵循 [slower-moving policy](https://material-ui.com/versions/#release-frequency)
 
-As developers use and test the components and report issues, the maintainers learn more about shortcomings of the components: missing features, accessibility issues, bugs, API design, etc. The older and more used a component is, the less likely it is that new issues will be found and subsequently need to introduce breaking changes.
+程序员在使用和测试组件后向项目报漏洞，维护者就知道更多关于组件的缺点：如缺少功能，能不能访问的问题、漏洞，API设计等等的问题 一个组建被使用的时间越久，新问题被发现以及因此需要引入重大更改的可能性就越少。
 
-For a component to be ready to move to the core, the following criteria are considered:
+那些准备放到核心库里的组件，需要考虑以下几点：
 
-* It needs to be **used**. The Material-UI team uses Google Analytics stats among other metrics to evaluate the usage of each component. A lab component with low usage either means that it isn't fully working yet or that there is a low demand for it.
-* It needs to match the **code quality** of the core components. It doesn't have to be perfect to be a part of the core, but the component should be reliable enough that developers can depend on it. 
-    * Each component needs **type definitions**. It is not currently required that a lab component is typed, but it would need to be typed to move to the core.
-    * Requires good **test coverage**. Some of the lab components don't currently have comprehensive tests.
-* Can it be used as **leverage** to incentivize users to upgrade to the latest major release? The less fragmented the community is, the better.
-* It needs to have a low probability of a **breaking change** in the short/medium future. For instance, if it needs a new feature that will likely require a breaking change, it may be preferable to delay its promotion to the core.
+* 它需要**被使用过** Material-UI 团队使用谷歌分析的数据去评估每个组件的使用情况。 如果一个实验室组件使用量太少，意味着它并不能全部正常工作，或者需求量比较小。
+* 它需要和核心组件的**代码质量**相似 作为核心代码的一部分，它不需要很完美，但是这个组件应该要很可靠，要另其他开发者可以依赖它 
+    * 每个组件需要**类型定义** 就目前来说，实验室组件不需要定义类型，但是当搬到核心代码之后就需要定义好类型了。
+    * 需要一个好的**测试覆盖率**。 有一些实验室组件目前并没有进行综合的测试。
+* 这个组建是否可以作为一个激励用户更新到最新版本的**杠杆**？ 一个社区的分裂程度越低越好。
+* 需要极少可能地在不久地将来就引入**重大更改**。 例如，如果它需要一个新的功能并因此将有可能引入重大更改，那么最好推迟将其纳入核心库。
 
 ## 安装
 
-Install the package in your project directory with:
+请在您的项目目录中用以下方式安装依赖包：
 
 ```sh
 // 用 npm 安装
@@ -27,7 +27,7 @@ npm install @material-ui/lab
 yarn add @material-ui/lab
 ```
 
-The lab has a peer dependency on the core components. If you are not already using Material-UI in your project, you can install it with:
+该 lab 和那些核心组件是对等依赖的。 若您还未在项目中使用 Material-UI，那可以按如下方式安装：
 
 ```sh
 // 用 npm 安装

diff --git a/docs/src/pages/components/alert/alert-de.md b/docs/src/pages/components/alert/alert-de.md
@@ -1,29 +1,29 @@
 ---
-title: Alert React component
+title: Hinweis React-Komponente
 components: Alert
 ---
 
-# Alert
+# Hinweis
 
-<p class="description">An alert displays a short, important message in a way that attracts the user's attention without interrupting the user's task.</p>
+<p class="description">Ein Hinweis zeigt eine kurze, wichtige Nachricht auf eine Weise, welche die Aufmerksamkeit des Benutzers auf sich zieht ohne die Aufgabe des Benutzers zu unterbrechen.</p>
 
-**Note:** This component is not documented in the [Material Design guidelines](https://material.io/), but Material-UI supports it.
+**Hinweis:** Diese Komponente ist nicht in den [Material-Design-Richtlinien](https://material.io/) dokumentiert, wird aber von Material-UI unterstützt.
 
-## Simple alerts
+## Einfache Hinweise
 
-The alert offers four severity levels that set a distinctive icon and color.
+Der Hinweis bietet vier Schweregrade an welche je ein eigenes Icon und eine eigene Farbe besitzen.
 
 {{"demo": "pages/components/alert/SimpleAlerts.js"}}
 
 ## Beschreibung
 
-You can use the `AlertTitle` component to display a formatted title above the content.
+Die `AlertTitle`-Komponente kann verwendet werden um einen formatierten Titel über dem Inhalt anzuzeigen.
 
 {{"demo": "pages/components/alert/DescriptionAlerts.js"}}
 
-## Actions
+## Aktionen
 
-An alert can have an action, such as a close or undo button. It is rendered after the message, at the end of the alert.
+Ein Hinweis kann eine Aktion wie zum Beispiel Schließen oder Zurücksetzen haben. Sie wird am Ende des Hinweises, hinter der Nachricht, angezeigt.
 
 If an `onClose` callback is provided and no `action` prop is set, a close icon is displayed. The `action` prop can be used to provide an alternative action, for example using a Button or IconButton.
 

diff --git a/docs/src/pages/components/alert/alert-es.md b/docs/src/pages/components/alert/alert-es.md
@@ -39,25 +39,25 @@ Puede utilizar el componente de [ transition ](/components/transitions/) como `C
 
 El `icon` prop permite añadir un icono para el inicio del componente Alert. Esto anulará el icono por defecto para la gravedad especificada.
 
-You can change the default severity to icon mapping with the `iconMapping` prop. This can be defined globally using [theme customization](/customization/globals/#default-props).
+Puede cambiar el ícono de la gravedad por defecto mediante la propidad  `iconMapping`. Esta puede ser definida de forma global usando  [Tema personalizado](/customization/globals/#default-props).
 
-Setting the icon prop to false will remove the icon altogether.
+Al establecer la propiedad `icon` en false, el ícono no se mostrará.
 
 {{"demo": "pages/components/alert/IconAlerts.js"}}
 
 ## Variants
 
-Two additional variants are available – outlined, and filled:
+Están disponibles dos variantes adicionales - outlined y filled:
 
-### Outlined
+### Contorno
 
 {{"demo": "pages/components/alert/OutlinedAlerts.js"}}
 
-### Filled
+### Relleno
 
 {{"demo": "pages/components/alert/FilledAlerts.js"}}
 
-## Toast
+## Mensaje emergente
 
 You can use the Snackbar to [display a toast](/components/snackbars/#customized-snackbars) with the Alert.
 

diff --git a/docs/src/pages/components/alert/alert-pt.md b/docs/src/pages/components/alert/alert-pt.md
@@ -21,58 +21,58 @@ Você pode usar o componente `AlertTitle` para exibir um título formatado acima
 
 {{"demo": "pages/components/alert/DescriptionAlerts.js"}}
 
-## Actions
+## Ações
 
-An alert can have an action, such as a close or undo button. It is rendered after the message, at the end of the alert.
+Um alerta pode conter uma ação, como um botão de fechar ou desfazer. É renderizado depois da mensagem na parte final do alerta.
 
-If an `onClose` callback is provided and no `action` prop is set, a close icon is displayed. The `action` prop can be used to provide an alternative action, for example using a Button or IconButton.
+Se um `onClose` callback é dado e um atributo `action` é passado, um ícone de fechar é exibido. O atributo `action` pode ser usado para fornecer uma ação alternativa, por exemplo usando um Button ou IconButton.
 
 {{"demo": "pages/components/alert/ActionAlerts.js"}}
 
-### Transition
+### Transição
 
-You can use a [transition component](/components/transitions/) such as `Collapse` to transition the appearance of the alert.
+Você pode utilizar um [transition component](/components/transitions/) como `Collapse` para realizar uma transição na aparência do alerta.
 
 {{"demo": "pages/components/alert/TransitionAlerts.js"}}
 
 ## Ícones
 
-The `icon` prop allows you to add an icon to the beginning of the alert component. This will override the default icon for the specified severity.
+O atributo `icon` permite que você adicione um ícone no início do componente de alerta. Isto substituirá o ícone padrão de acordo com a gravidade especificada.
 
-You can change the default severity to icon mapping with the `iconMapping` prop. This can be defined globally using [theme customization](/customization/globals/#default-props).
+Você pode alterar a gravidade padrão para mapeamento de ícones com o atributo `iconMapping`. Isto pode ser definido globalmente utilizando [theme customization](/customization/globals/#default-props).
 
-Setting the icon prop to false will remove the icon altogether.
+Definir o atributo ícone como falso removerá o ícone completamente.
 
 {{"demo": "pages/components/alert/IconAlerts.js"}}
 
 ## Variantes
 
-Two additional variants are available – outlined, and filled:
+Duas variantes adicionais estão disponíveis – delineadas e preenchidas:
 
 ### Outlined
 
 {{"demo": "pages/components/alert/OutlinedAlerts.js"}}
 
-### Filled
+### Preenchido
 
 {{"demo": "pages/components/alert/FilledAlerts.js"}}
 
-## Toast
+## Aviso na tela
 
-You can use the Snackbar to [display a toast](/components/snackbars/#customized-snackbars) with the Alert.
+Você pode usar o componente SnackBar para [exibir um aviso na tela](/components/snackbars/#customized-snackbars) com o componente Alert.
 
 ## Cor
 
-The `color` prop will override the default color for the specified severity.
+A propriedade `color` substituirá a cor padrão para a gravidade especificada.
 
 {{"demo": "pages/components/alert/ColorAlerts.js"}}
 
 ## Acessibilidade
 
 (WAI-ARIA: https://www.w3.org/TR/wai-aria-practices/#alert)
 
-When the component is dynamically displayed, the content is automatically announced by most screen readers. At this time, screen readers do not inform users of alerts that are present when the page loads.
+Quando o componente é exibido de forma dinâmica, o conteúdo é automaticamente anunciado pela maioria dos leitores de tela. No momento, os leitores de tela não informam aos usuários sobre alertas que estão presentes quando a página carrega.
 
-Using color to add meaning only provides a visual indication, which will not be conveyed to users of assistive technologies such as screen readers. Ensure that information denoted by the color is either obvious from the content itself (for example the visible text), or is included through alternative means, such as additional hidden text.
+O uso de cores para adicionar significado apenas fornece uma indicação visual, que não vai ser transmitida para usuários de tecnologias assistivas, como leitores de tela. Certifique-se de que a informação indicada pela cor seja clara a partir do próprio próprio conteúdo (por exemplo, o texto visível), ou esteja incluída através de meios alternativos, como um texto oculto adicional.
 
-Actions must have a tab index of 0 so that they can be reached by keyboard-only users.
+As ações devem ter um índice de tabulação igual a 0 para que possam ser alcançadas por usuários que usam apenas o teclado.
diff --git a/docs/src/pages/components/alert/alert-zh.md b/docs/src/pages/components/alert/alert-zh.md
@@ -31,7 +31,7 @@ components: Alert
 
 ### 过渡效果
 
-可以使用 [过渡组件](/components/transitions) ，如 `Collapse（展开）` 来实现「提醒」出现时的过渡效果。
+可以使用 [过渡组件](/components/transitions/) ，如 `Collapse（展开）` 来实现「提醒」出现时的过渡效果。
 
 {{"demo": "pages/components/alert/TransitionAlerts.js"}}