diff --git a/files/pt-br/_redirects.txt b/files/pt-br/_redirects.txt
index 03eef4f3c784f5..30a8fb2bb3e3a5 100644
--- a/files/pt-br/_redirects.txt
+++ b/files/pt-br/_redirects.txt
@@ -381,7 +381,6 @@
/pt-BR/docs/JavaScript/Reference/Statements/let /pt-BR/docs/Web/JavaScript/Reference/Statements/let
/pt-BR/docs/JavaScript/uma_reintroduction_ao_JavaScript /pt-BR/docs/Web/JavaScript/Language_overview
/pt-BR/docs/Learn/Accessibility/Acessibilidade_problemas /pt-BR/docs/Learn/Accessibility/Accessibility_troubleshooting
-/pt-BR/docs/Learn/Accessibility/CSS_e_JavaScript /pt-BR/docs/Learn/Accessibility/CSS_and_JavaScript
/pt-BR/docs/Learn/CSS/CSS_layout/Fluxo_Normal /pt-BR/docs/Learn/CSS/CSS_layout/Normal_Flow
/pt-BR/docs/Learn/CSS/CSS_layout/Intro_leiaute_CSS /pt-BR/docs/Learn/CSS/CSS_layout/Introduction
/pt-BR/docs/Learn/CSS/CSS_layout/Layout_de_varias_colunas /pt-BR/docs/Learn/CSS/CSS_layout/Multiple-column_Layout
@@ -442,7 +441,6 @@
/pt-BR/docs/Localização /pt-BR/docs/Glossary/Localization
/pt-BR/docs/MDN/About /pt-BR/docs/MDN/Writing_guidelines
/pt-BR/docs/MDN/Contribute/Content /pt-BR/docs/conflicting/MDN/Writing_guidelines
-/pt-BR/docs/MDN/Contribute/Content/Style_guide /pt-BR/docs/MDN/Writing_guidelines/Writing_style_guide
/pt-BR/docs/MDN/Contribute/Estruturas /pt-BR/docs/conflicting/MDN/Writing_guidelines/Page_structures
/pt-BR/docs/MDN/Contribute/Estruturas/Compatibility_tables /pt-BR/docs/MDN/Writing_guidelines/Page_structures
/pt-BR/docs/MDN/Contribute/Estruturas/Macros /pt-BR/docs/conflicting/MDN/Writing_guidelines/Page_structures_978c99f4f82eae196d51ce675e5181c7
@@ -469,8 +467,6 @@
/pt-BR/docs/MDN/Contribute/guia/Create_an_interactive_exercise_to_help_learning_the_web/distant_example /pt-BR/docs/conflicting/MDN/Contribute/Howto/Create_an_interactive_exercise_to_help_learning_the_web
/pt-BR/docs/MDN/Feedback /pt-BR/docs/MDN/Community
/pt-BR/docs/MDN/Guidelines /pt-BR/docs/conflicting/MDN/Writing_guidelines
-/pt-BR/docs/MDN/Guidelines/Style_guide /pt-BR/docs/MDN/Writing_guidelines/Writing_style_guide
-/pt-BR/docs/MDN/Guidelines/Writing_style_guide /pt-BR/docs/MDN/Writing_guidelines/Writing_style_guide
/pt-BR/docs/MDN/Kuma /pt-BR/docs/orphaned/MDN/Yari
/pt-BR/docs/MDN/Primeiros_Passos /pt-BR/docs/MDN/Community/Contributing/Getting_started
/pt-BR/docs/MDN/Structures /pt-BR/docs/conflicting/MDN/Writing_guidelines/Page_structures
@@ -492,7 +488,6 @@
/pt-BR/docs/Mozilla/Add-ons/WebExtensions/pre-requisitos /pt-BR/docs/Mozilla/Add-ons/WebExtensions/Prerequisites
/pt-BR/docs/Mozilla/Add-ons/WebExtensions/sua_primeira_WebExtension /pt-BR/docs/Mozilla/Add-ons/WebExtensions/Your_first_WebExtension
/pt-BR/docs/Mozilla/Add-ons/WebExtensions/user_interface/Itens_do_menu_de_contexto /pt-BR/docs/Mozilla/Add-ons/WebExtensions/user_interface/Context_menu_items
-/pt-BR/docs/Mozilla/Firefox/Novas_funcionalidades /pt-BR/docs/Mozilla/Firefox/Experimental_features
/pt-BR/docs/Mozilla/Firefox/Releases/3/Zoom_de_página_inteira /pt-BR/docs/Mozilla/Firefox/Releases/3/Full_page_zoom
/pt-BR/docs/Quirks_Mode_and_Standards_Mode /pt-BR/docs/Web/HTML/Quirks_Mode_and_Standards_Mode
/pt-BR/docs/SVG /pt-BR/docs/Web/SVG
diff --git a/files/pt-br/learn/accessibility/css_and_javascript/index.md b/files/pt-br/learn/accessibility/css_and_javascript/index.md
deleted file mode 100644
index 22d3676216f712..00000000000000
--- a/files/pt-br/learn/accessibility/css_and_javascript/index.md
+++ /dev/null
@@ -1,355 +0,0 @@
----
-title: CSS e JavaScript - melhores práticas de acessibilidade
-slug: Learn/Accessibility/CSS_and_JavaScript
-original_slug: Learn/Accessibility/CSS_e_JavaScript
----
-
-{{LearnSidebar}}{{PreviousMenuNext("Learn/Accessibility/HTML","Learn/Accessibility/WAI-ARIA_basics", "Learn/Accessibility")}}
-
-CSS e JavaScript, quando usados de maneira correta, têm também potencial para permitir experiências web acessíveis... ou podem causar danos significativos se usados de forma indevida. Este artigo descreve algumas das melhores práticas em CSS e JavaScript a serem consideradas para garantir que até mesmo conteúdos complexos estejam tão acessíveis quanto possível.
-
-
-
-
- Pré-requisitos:
-
- Conhecimento básico de computação, Conhecimento básico de HTML, CSS, e
- JavaScript, e entendimento sobre
- o que é acessibilidade .
-
-
-
- Objetivo:
-
- Tornar-se familiarizado com o uso de CSS e JavaScript apropriadamente em
- seus documentos web para maximizar a acessibilidade e não diminuir sua
- importância.
-
-
-
-
-
-## CSS e JavaScript são acessíveis?
-
-CSS e JavaScript não têm a mesma importância imediata que o HTML, mas eles continuam sendo capazes de ajudar ou causar danos à acessibilidade, dependendo de como são usados. Ou seja, é importante que você considere algumas das melhores práticas para assegurar que o seu uso de CSS e JavaScript não danifiquem a acessibilidade de seus documentos.
-
-## CSS
-
-Vamos começar dando uma olhada no CSS.
-
-### Semântica correta e expectativas do usuário
-
-É possível usar CSS para fazer qualquer elemento HTML se parecer com qualquer coisa, mas isso não quer dizer que você deve. Como frequentemente mencionado no nosso artigo [HTML: Uma boa base para acessibilidade](/pt-BR/docs/Learn/Accessibility/HTML), você deve utilizar a semântica apropriada do elemento para determinada tarefa, sempre que possível. Se não o fizer, isso poderá acarretar confusão e problemas de usabilidade para todos, particularmente para usuários portadores de deficiência. Utilizar uma semântica correta tem muito a ver com as expectativas do usuário — elementos se parecem e se comportam de certas maneiras, de acordo com suas funcionalidades, e essas convenções são esperadas pelos usuários.
-
-Por exemplo, um usuário utilizando um leitor de tela não consegue navegar por uma página através de elementos de heading se o desenvolvedor não tiver usado apropriadamente estes elementos para marcação do conteúdo. Da mesma forma, um heading perde o seu propósito visual se você estilizá-lo de maneira que ele não se pareça com um heading.
-
-A regra de ouro é que você pode atualizar o estilo de recurso de página para se adequar ao seu design, mas não o altere tanto ao ponto de não mais se parecer ou se comportar como o esperado. As sessões que se seguem resumem os principais recursos HTML a serem considerados.
-
-#### Estrututa "standard" de conteúdo textual
-
-Headings, parágrafos, listss — o núcleo do conteúdo textual da sua página:
-
-```html
-Heading
-
-Parágrafo
-
-
- Minha lista
- tem dois itens.
-
-```
-
-Um código CSS típico pode se parecer com isso:
-
-```css
-h1 {
- font-size: 5rem;
-}
-
-p, li {
- line-height: 1.5;
- font-size: 1.6rem;
-}
-```
-
-Você tem de:
-
-- Selecionar tamanhos de fonte sensíveis, altura de linhas, espaçamento entre letras, etc. para fazer com que o seu texto seja lógico, legível e de leitura confortável.
-- Tenha certeza que os seus headings se destaquem do corpo do seu texto, geralmente grande e em negrito conforme o estilo padrão.
-- A cor do seu texto deve ter um bom contraste com a cor de fundo.
-
-Veja [HTML fundamentos de texto](/pt-BR/docs/Learn/HTML/Introduction_to_HTML/HTML_text_fundamentals) e [Estilizando texto](/pt-BR/docs/Learn/CSS/Styling_text) para maiores informações.
-
-#### Texto em negrito
-
-Elemento de marcação que confere ênfase específica ao texto envolvido por ele:
-
-```html
-A água está muito quente .
-
-Gotículas de água em superfícies são chamadas de condensação .
-```
-
-Você pode querer adicionar alguma cor no seu texto em negrito:
-
-```css
-strong, em {
- color: #a60000;
-}
-```
-
-De qualquer forma, você raramente irá precisar de estilizar um elemento de ênfase. As convenções para texto em negrito e itálico são bastante reconhecidas e alterar seu estilo pode causar confusão. Para saber mais sobre elemento ênfase (negrito), veja [Emphasis and importance](/pt-BR/docs/Learn/HTML/Introduction_to_HTML/HTML_text_fundamentals#Emphasis_and_importance).
-
-#### Abreviações
-
-É um elemento que permite abreviação, acrônimo ou inicialização que esteja associada com sua expansão:
-
-```html
-Web content is marked up using HTML .
-```
-
-Novamente, você pode querer estilizá-lo de alguma forma:
-
-```css
-abbr {
- color: #a60000;
-}
-```
-
-A convenção de estilo que é reconhecida para abreviações é uma linha pontilhada, e não é recomendado estilizá-la. Para saber mais sobre abreviações, veja [Abbreviations](/pt-BR/docs/Learn/HTML/Introduction_to_HTML/Advanced_text_formatting#Abbreviations).
-
-#### Links
-
-Hyperlinks — the way you get to new places on the web:
-
-```html
-Visit the Mozilla homepage .
-```
-
-Some very simple link styling is shown below:
-
-```css
-a {
- color: #ff0000;
-}
-
-a:hover, a:visited, a:focus {
- color: #a60000;
- text-decoration: none;
-}
-
-a:active {
- color: #000000;
- background-color: #a60000;
-}
-```
-
-The standard link conventions are underlined and a different color (default: blue) in their standard state, another color variation when the link has previously been visited (default: purple), and yet another color when the link is activated (default: red). In addition, the mouse pointer changes to a pointer icon when links are moused over, and the link receives a highlight when focused (e.g. via tabbing) or activated. The following image shows the highlight in both Firefox (a dotted outline) and Chrome (a blue outline):
-
-
-
-
-
-You can be creative with link styles, as long as you keep giving users feedback when they interact with the links. Something should definitely happen when states change, and you shouldn't get rid of the pointer cursor or the outline — both are very important accessibility aids for those using keyboard controls.
-
-#### Form elements
-
-Elements to allow users to input data into websites:
-
-```html
-
- Enter your name
-
-```
-
-You can see some good example CSS in our [form-css.html](https://github.com/mdn/learning-area/blob/master/accessibility/css/form-css.html) example ([see it live](http://mdn.github.io/learning-area/accessibility/css/form-css.html) also).
-
-Most of the CSS you'll write for forms will be for sizing the elements, lining up labels and inputs, and getting them looking neat and tidy.
-
-You shouldn't however deviate too much from the expected visual feedback form elements receive when they are focused, which is basically the same as links (see above). You could style form focus/hover states to make this behaviour more consistent across browsers or fit in better with your page design, but don't get rid of it altogether — again, people rely on these clues to help them know what is going on.
-
-#### Tables
-
-Tables for presenting tabular data.
-
-You can see a good, simple example of table HTML and CSS in our [table-css.html](https://github.com/mdn/learning-area/blob/master/accessibility/css/table-css.html) example ([see it live also](http://mdn.github.io/learning-area/accessibility/css/table-css.html)).
-
-Table CSS generally serves to make the table fit better into your design and look less ugly. It is a good idea to make sure the table headers stand out (normally using bold), and use zebra striping to make different rows easier to parse.
-
-### Color and color contrast
-
-When choosing a color scheme for your website, make sure that the text (foreground) color contrasts well with the background color. Your design might look cool, but it is no good if people with visual impairments like color blindness can't read your content.
-
-There is an easy way to check whether your contrast is large enough to not cause problems. There are a number of contrast checking tools online that you can enter your foreground and background colors into, to check them. For example WebAIM's [Color Contrast Checker](http://webaim.org/resources/contrastchecker/) is simple to use, and provides an explanation of what you need to conform to the WCAG criteria around color contrast.
-
-> **Nota:** A high contrast ratio will also allow anyone using a smartphone or tablet with a glossy screen to better read pages when in a bright environment, such as sunlight.
-
-Another tip is to not rely on color alone for signposts/information, as this will be no good for those who can't see the color. Instead of marking required form fields in red, for example, mark them with an asterisk and in red.
-
-### Hiding things
-
-There are many instances where a visual design will require that not all content is shown at once. For example, in our [Tabbed info box example](http://mdn.github.io/learning-area/css/css-layout/practical-positioning-examples/info-box.html) (see [source code](https://github.com/mdn/learning-area/blob/master/css/css-layout/practical-positioning-examples/info-box.html)) we have three panels of information, but we are [positioning](/pt-BR/docs/Learn/CSS/CSS_layout/Positioning) them on top of one another and providing tabs that can be clicked to show each one (it is also keyboard accessible — you can alternatively use Tab and Enter/Return to select them).
-
-
-
-Screen reader users don't care about any of this — they are happy with the content as long as the source order makes sense, and they can get to it all. Absolute positioning (as used in this example) is generally seen as one of the best mechanisms of hiding content for visual effect, because it doesn't stop screen readers from getting to it.
-
-On the other hand, you shouldn't use {{cssxref("visibility")}}`:hidden` or {{cssxref("display")}}`:none`, because they do hide content from screen readers. Unless of course, there is a good reason why you want this content to be hidden from screen readers.
-
-> **Nota:** [Invisible Content Just for Screen Reader Users](http://webaim.org/techniques/css/invisiblecontent/) has a lot more useful detail surrounding this topic.
-
-### Accept that users can override styles
-
-#### Accept that users can override your styles
-
-It is possible for users to override your styles with their own custom styles, for example:
-
-- See Sarah Maddox's [How to use a custom style sheet (CSS) with Firefox](https://www.itsupportguides.com/knowledge-base/computer-accessibility/how-to-use-a-custom-style-sheet-css-with-firefox/) for a useful guide covering how to do this manually in Firefox, and [How to use a custom style sheet (CSS) with Internet Explorer](https://www.itsupportguides.com/knowledge-base/computer-accessibility/how-to-use-a-custom-style-sheet-css-with-internet-explorer/) by Adrian Gordon for the equivalent IE instructions.
-- It is probably easier to do it using an extension, for example the Stylish extension is available for [Firefox](https://addons.mozilla.org/en-US/firefox/addon/stylish/), [Safari](https://safari-extensions.apple.com/details/?id=com.sobolev.stylish-5555L95H45), [Opera](https://addons.opera.com/en/extensions/details/stylish/), and [Chrome](https://chrome.google.com/webstore/detail/stylish/fjnbnpbmkenffdnngjfgmeleoegfcffe).
-
-Users might do this for a variety of reasons. A visually impaired user might want to make the text bigger on all websites they visit, or a user with severe color deficiency might want to put all websites in high contrast colors that are easy for them to see. Whatever the need, you should be comfortable with this, and make your designs flexible enough so that such changes will work in your design. As an example, you might want to make sure your main content area can handle bigger text (maybe it will start to scroll to allow it all to be seen), and won't just hide it, or break completely.
-
-## JavaScript
-
-JavaScript can also break accessibility, depending on how it is used.
-
-Modern JavaScript is a powerful language, and we can do so much with it these days, from simple content and UI updates to fully-fledged 2D and 3D games. There is no rule that says all content has to be 100% accessible to all people — you just need to do what you can, and make your apps as accessible as possible.
-
-Simple content and functionality is arguably easy to make accessible — for example text, images, tables, forms and push button that activate functions. As we looked at in our [HTML: A good basis for accessibility](/pt-BR/docs/Learn/Accessibility/HTML) article, the key considerations are:
-
-- Good semantics: Using the right element for the right job. For example, making sure you use headings and paragraphs, and {{htmlelement("button")}} and {{htmlelement("a")}} elements
-- Making sure content is available as text, either directly as text content, good text labels for form elements, or [text alternatives](/pt-BR/docs/Learn/Accessibility/HTML#Text_alternatives), e.g. alt text for images.
-
-We also looked at an example of how to use JavaScript to build in functionality where it is missing — see [Building keyboard accessibility back in](/pt-BR/docs/Learn/Accessibility/HTML#Building_keyboard_accessibility_back_in). This is not ideal — really you should just use the right element for the right job — but it shows that it is possible in situations where for some reason you can't control the markup that is used. Another way to improve accessibility for non-semantic JavaScript-powered widgets is to use WAI-ARIA to provide extra semantics for screen reader users. The next article will also cover this in detail.
-
-Complex functionality like 3D games are not so easy to make accessible — a complex 3D game created using [WebGL](/pt-BR/docs/Web/API/WebGL_API) will be rendered on a {{htmlelement("canvas")}} element, which has no facility at this time to provide text alternatives or other information for severely visually impaired users to make use of. It is arguable that such a game doesn't really have this group of people as a part of its main target audience, and it would be unreasonable to expect you to make it 100% accessible to blind people, however you could implement [keyboard controls](/pt-BR/docs/Games/Techniques/Control_mechanisms/Desktop_with_mouse_and_keyboard) so it is usable by non-mouse users, and make the color scheme contrasting enough to be usable by those with color deficiencies.
-
-### The problem with too much JavaScript
-
-The problem often comes when people rely on JavaScript too much. Sometimes you'll see a website where everything has been done with JavaScript — the HTML has been generated by JavaScript, the CSS has been generated by JavaScript, etc. This has all kinds of accessibility and other issues associated with it, so it is not advised.
-
-As well as using the right element for the right job, you should also make sure you are using the right technology for the right job! Think carefully about whether you need that shiny JavaScript-powered 3D information box, or whether plain old text would do. Think carefully about whether you need a complex non-standard form widget, or whether a text input would do. And don't generate all your HTML content using JavaScript if at all possible.
-
-### Keeping it unobtrusive
-
-You should keep **unobtrusive JavaScript** in mind when creating your content. The idea of unobtrusive JavaScript is that it should be used wherever possible to enhance functionality, not build it in entirely — basic functions should ideally work without JavaScript, although it is appreciated that this is not always an option. But again, a large part of it is using built-in browser functionality where possible.
-
-Good example uses of unobtrusive JavaScript include:
-
-- Providing client-side form validation, which alerts users to problems with their form entries quickly, without having to wait for the server to check the data. If it isn't available, the form will still work, but validation might be slower.
-- Providing custom controls for HTML5 ``s that are accessible to keyboard-only users, along with a direct link to the video that can be used to access it if JavaScript is not available (the default `` browser controls aren't keyboard accessible in most browsers).
-
-As an example, we've written a quick and dirty client-side form validation example — see [form-validation.html](https://github.com/mdn/learning-area/blob/master/accessibility/css/form-validation.html) (also [see the demo live](http://mdn.github.io/learning-area/accessibility/css/form-validation.html)). Here you'll see a simple form; when you try to submit the form with one or both fields left empty, the submit fails, and an error message box appears to tell you what is wrong.
-
-This kind of form validation is unobtrusive — you can still use the form absolutely fine without the JavaScript being available, and any sensible form implementation will have server-side validation active as well, because it is too easy for malicious users to bypass client-side validation (for example, by turning JavaScript off in the browser). The client-side validation is still really useful for reporting errors — users can know about mistakes they make instantly, rather than having to wait for a round trip to the server and a page reload. This is a definite usability advantage.
-
-> **Nota:** Server-side validation has not been implemented in this simple demo.
-
-We've made this form validation pretty accessible too. We've used {{htmlelement("label")}} elements to make sure the form labels are unambiguously linked to their inputs, so screen readers can read them out alongside:
-
-```html
-Enter your name:
-/docs/"._
-
-#### Maisuculização de títulos e cabeçalhos
-
-Títulos de páginas e seções de cabeçalho devem usar letras maiúsculas no estilo da frase (Maiúsculas so na primeira palavra e nomes próprios) em vez de letras maiúsculas no estilo de título:
-
-- **Correto**: "Um novo método para criar sobreposições Javascript"
-- **Incorreto**: "Um Novo Método para Criar Sobreposições Javascript"
-
-Nós temos muitas páginas antigas que foram escritas antes que essa regra de estilo fosse estabelecida. Sinta-se livre para atualizá-las se achar necessário. Estamos atualizando-as gradualmente.
-
-#### Escolhendo títulos e slugs
-
-Slugs de página devem ser mantidas curtas; quando criar um novo nível de hierarquia, o componente do novo nível no slug, geralmente, deve ser só uma ou duas palavras.
-
-Títulos de páginas, por outro lado, podem ser grandes o quanto quiser, sendo razoável, e devem ser descritivos.
-
-#### Criando novas subárvores
-
-Quando você precisar adicionar vários artigos sobre um tópico ou um assunto do tópico, você normalmente fará isso criando uma página de destino e adicionando subpáginas para cada um dos artigos individuais. A página de destino deve abrir com um ou dois parágrafos descrevendo o tópico ou a técnologia e, em seguida, fornecer uma lista de subpáginas com descrições de cada página. Você pode automatizar a inserção de páginas na lista usando algumas macros que criamos.
-
-Por exemplo, considere a guia [JavaScript](/pt-BR/docs/Web/JavaScript), que é estruturada da seguinte forma:
-
-- [JavaScript/Guide](/pt-BR/docs/Web/JavaScript/Guide) - Página principal do sumário.
-- [JavaScript/Guide/JavaScript Overview](/pt-BR/docs/Web/JavaScript/Guide/JavaScript_Overview)
-- [JavaScript/Guide/Functions](/pt-BR/docs/JavaScript/Guide/Functions)
-- [JavaScript/Guide/Details of the Object Model](/pt-BR/docs/JavaScript/Guide/Details_of_the_Object_Model)
-
-Tente evitar colocar seu artigo no topo da hierarquia, o que torna lento o site e menos eficiente a pesquisa e a navegação.
-
-### Orientações gerais do conteúdo do artigo
-
-Quando estiver escrevendo qualquer documento é importante conhecer o quanto falar. Se ficar divagando muito o artigo fica tedioso de ler e ninguém ira usa-lo. Escolher a quantidade certa a falar sobre o assunto é muito importante por diversas razões. Entre essas razões: assegurar que o leitor encontre a informação que eles precisam, prover suficiente material de qualidade para os engines de pesquisa poderem analizar e classificar o artigo de maneira adequada. Iremos discutir ao respeito disso aqui. Para aprender um pouco mais sobre como fazer as páginas são classificadas pelos engines de pesquisa, vejam o artigo [Como escrever SEO para MDN](/pt-BR/docs/MDN/Contribute/Howto/Write_for_SEO).
-
-### Seções, parágrafos e novas linhas
-
-Use os níveis de cabeçalho em ordem decrescente na hierarquia: {{HTMLElement("h2")}} depois {{HTMLElement("h3")}} depois {{HTMLElement("h4")}}, sem pular níveis. {{HTMLElement("h2")}} é o maior nível permitido, pois {{HTMLElement("h1")}} está reservado para o título da página. Se perceber que precisará de mais de 3 ou 4 níveis de cabeçalho, considere fragmentar seu artigo em artigos menores, ou colocando uma landing page, linkando estes com o [Next](https://github.com/mdn/yari/blob/main/kumascript/macros/Next.ejs), [Previous](https://github.com/mdn/yari/blob/main/kumascript/macros/Previous.ejs), e [PreviousNext](https://github.com/mdn/yari/blob/main/kumascript/macros/PreviousNext.ejs) macros.
-
-O Enter (ou Return) do seu teclado inicia um novo parágrafo. Para inserir uma nova linha sem espaço, faça Shift + Enter.
-
-#### Algumas regras
-
-- Não crie listas com apenas um item. Não divida um tópico em um. No mínimo dois, ou nenhum.
-- Não crie cabeçalhos em sequência. É visualmente feio, e é importante para os leitores apresentar algum texto antes de iniciar outras seções.
-- Evite usar macros de cabeçalhos, com exceção de algumas macros específicas para tal.
-- Não use estilos e classes nos cabeçalhos; especificamente falando do elemento \. Portanto, não faça um cabeçalho "Usando a interface `SuperAmazingThing`". Em vez disso, escreva "Usando a interface SuperAmazingThing".
-
-### Text formatting and styles
-
-Use the "Formatting Styles" drop-down list to apply predefined styles to selected content.
-
-> **Nota:** The "Note" style is used to call out important notes, like this one.
-
-> **Aviso:** Similarly, the "Warning" style creates warning boxes like this.
-
-Unless specifically instructed to do so, **do not** use the HTML `style` attribute to manually style content. If you can't do it using a predefined class, drop into [Matrix](https://chat.mozilla.org/#/room/#mdn:mozilla.org) and ask for help.
-
-### Code sample style and formatting
-
-#### Tabs and line breaks
-
-Use two spaces per tab in all code samples. Code should be indented cleanly, with open-brace ("{") characters on the same line as the statement that opens the block. For example:
-
-```js
-if (condition) {
- /* handle the condition */
-} else {
- /* handle the "else" case */
-}
-```
-
-Long lines shouldn't be allowed to stretch off horizontally to the extent that they require horizontal scrolling to read. Instead, break at natural breaking points. Some examples follow:
-
-```js
-if (class.CONDITION || class.OTHER_CONDITION || class.SOME_OTHER_CONDITION
- || class.YET_ANOTHER_CONDITION ) {
- /* something */
-}
-
-var toolkitProfileService = Components.classes["@mozilla.org/toolkit/profile-service;1"]
- .createInstance(Components.interfaces.nsIToolkitProfileService);
-```
-
-#### Inline code formatting
-
-Use the "Code" button (labeled with two angle brackets "<>") to apply inline code-style formatting to function names, variable names, and method names (this uses the {{HTMLElement("code")}} element). For example, "the `frenchText()` function".
-
-Method names should be followed by a pair of parentheses: `doSomethingUseful()`. This helps to differentiate methods from other code terms.
-
-#### Syntax highlighting
-
-Entire lines (or multiple lines) of code should be formatted using syntax highlighting rather than the {{HTMLElement("code")}} element. Click the "pre" button in the toolbar to create the preformatted content box in which you'll then write your code. Then, with the text entry cursor inside the code box, select the appropriate language from the language list button to the right of the "pre" button, as seen in the screenshot to the right. The following example shows text with JavaScript formatting:
-
-```js
-for (var i = 0, j = 9; i <= 9; i++, j--)
- document.writeln("a[" + i + "][" + j + "]= " + a[i][j]);
-```
-
-If no appropriate transformation is available, use the `pre` tag without specifying a language ("No Highlight" in the language menu).
-
-```
-x = 42;
-```
-
-#### Styling HTML element references
-
-There are various specific rules to follow when writing about HTML elements, in order to consistently describe the various components of elements, and to ensure that they're properly linked to detailed documentation.
-
-- Element names
- - : Use the [`HTMLElement`](https://github.com/mdn/yari/blob/main/kumascript/macros/HTMLElement.ejs) macro, which creates a link to the page for that element. For example, writing \\{{HTMLElement("title")}} produces "{{HTMLElement("title")}}". If you don't want to create a link, **enclose the name in angle brackets** and use "Code (inline)" style (e.g., ``).
-- Attribute names
- - : Use **bold face**.
-- Attribute values
- - : Use "Code (inline)" style, and do not use quotation marks around strings, unless needed by the syntax of a code sample. E.g.: When the **type** attribute of an `<input>` element is set to `email` or `tel` ...
-- Labeling attributes
- - : Use labels like HTML 5 thoughtfully. For example, use them next to the bold attribute name but not for every occurrence in your body text.
-
-### Latin abbreviations
-
-#### In notes and parentheses
-
-- Common Latin abbreviations (etc., i.e., e.g.) may be used in parenthetical expressions and in notes. Use periods in these abbreviations.
-
- - **Correct**: Web browsers (e.g. Firefox) can be used ...
- - **Incorrect**: Web browsers e.g. Firefox can be used ...
- - **Incorrect**: Web browsers, e.g. Firefox, can be used ...
- - **Incorrect**: Web browsers, (eg: Firefox) can be used ...
-
-#### In running text
-
-- In regular text (i.e. text outside of notes or parentheses), use the English equivalent of the abbreviation.
-
- - **Correct**: ... web browsers, and so on.
- - **Incorrect**: ... web browsers, etc.
- - **Correct**: Web browsers such as Firefox can be used ...
- - **Incorrect**: Web browsers e.g. Firefox can be used ...
-
-#### Meanings and English equivalents of Latin abbreviations
-
-| Abbrev | Latin | English |
-| ------ | ---------------- | ----------------------- |
-| cf. | _confer_ | compare |
-| e.g. | _exempli gratia_ | for example |
-| et al. | _et alii_ | and others |
-| etc. | _et cetera_ | and so forth, and so on |
-| i.e. | _id est_ | that is, in other words |
-| N.B. | _nota bene_ | note well |
-| P.S. | _post scriptum_ | postscript |
-
-> **Nota:** Always consider whether it's truly beneficial to use a Latin abbreviation. Some of these are used so rarely that many readers won't understand the meaning, and others are often confused with one another. And be sure that **you** use them correctly, if you choose to do so. For example, be careful not to confuse "e.g." with "i.e.", which is a common error.
-
-### Acronyms and abbreviations
-
-#### Capitalization and periods
-
-Use full capitals and delete periods in all acronyms and abbreviations, including organizations such as "US" and "UN".
-
-- **Correct**: XUL
-- **Incorrect**: X.U.L.; Xul
-
-#### Expansion
-
-On the first mention of a term on a page, expand acronyms likely to be unfamiliar to users. When in doubt, expand it, or, better, link it to the article or [glossary](/pt-BR/docs/Glossary) entry describing the technology.
-
-- **Correct**: "XUL (XML User Interface Language) is Mozilla's XML-based language..."
-- **Incorrect**: "XUL is Mozilla's XML-based language..."
-
-#### Plurals of acronyms and abbreviations
-
-For plurals of acronyms or abbreviations, add _s_. Don't use an apostrophe. Ever. Please.
-
-- **Correct**: CD-ROMs
-- **Incorrect**: CD-ROM's
-
-### Capitalization
-
-Use standard English capitalization rules in body text, and capitalize "World Wide Web" and "Web".
-
-Keyboard keys should use sentence-style capitalization, not all-caps capitalization. For example, "Enter" not "ENTER."
-
-### Contractions
-
-Use contractions (e.g. "don't", "can't", "shouldn't") if you prefer. We're not that formal!
-
-### Pluralization
-
-Use English-style plurals, not the Latin- or Greek-influenced forms.
-
-- **Correct**: syllabuses, octopuses
-- **Incorrect**: syllabi, octopi
-
-### Hyphenation
-
-Hyphenate compounds when the last letter of the prefix is a vowel and is the same as the first letter of the root.
-
-- **Correct**: email, re-elect, co-op
-- **Incorrect**: e-mail, reelect, coop
-
-### Gender-neutral language
-
-It is a good idea to use gender-neutral language in any kind of writing where gender is irrelevant to the subject matter, to make the text as inclusive as possible. So for example, if you are talking about the actions of a specific man, usage of he/his would be fine, but if the subject is a person of either gender, he/his isn't really appropriate.
-
-Let's take the following example:
-
-> A confirmation dialog appears, asking the user if he allows the web page to make use of his web cam.
-
-> A confirmation dialog appears, asking the user if she allows the web page to make use of her web cam.
-
-Both versions in this case are gender-specific. This could be fixed by using gender-neutral pronouns:
-
-> A confirmation dialog appears, asking the user if they allow the web page to make use of their web cam.
-
-> **Nota:** MDN allows the use of this very common syntax (which is controversial among usage authorities), in order to make up for the lack of a neutral gender in English. The use of the third-person plural as a neutral gender pronoun (that is, using "they," them", "their," and "theirs") is an accepted practice, commonly known as "[singular 'they.'](http://en.wikipedia.org/wiki/Singular_they)"
-
-You can use both genders:
-
-> A confirmation dialog appears, asking the user if he or she allows the web page to make use of his/her web cam.
-
-making the users plural:
-
-> A confirmation dialog appears, asking the users if they allow the web page to make use of their web cams.
-
-The best solution, of course, is to rewrite and eliminate the pronouns completely:
-
-> A confirmation dialog appears, requesting the user's permission for web cam access.
-
-> A confirmation dialog box appears, which asks the user for permission to use the web cam.
-
-The last way of dealing with the problem is arguably better, as it is not only grammatically more correct but removes some of the complexity associated with dealing with genders across different languages that may have wildly varying gender rules. This can make translation easier, both for readers reading English, then translating it into their own language as they read, and for localizers translating articles into their own language.
-
-### Numbers and numerals
-
-#### Dates
-
-For dates (not including dates in code samples) use the format "January 1, 1990".
-
-- **Correct**: February 24, 2006
-- **Incorrect**: February 24th, 2006; 24 February, 2006; 24/02/2006
-
-Alternately, you can use the YYYY/MM/DD format.
-
-- **Correct**: 2006/02/24
-- **Incorrect**: 02/24/2006; 24/02/2006; 02/24/06
-
-#### Decades
-
-For decades, use the format "1990s". Don't use an apostrophe.
-
-- **Correct**: 1990s
-- **Incorrect**: 1990's
-
-#### Plurals of numerals
-
-For plurals of numerals add "s". Don't use an apostrophe.
-
-- **Correct**: 486s
-- **Incorrect**: 486's
-
-#### Commas
-
-In running text, use commas only in five-digit and larger numbers.
-
-- **Correct**: 4000; 54,000
-- **Incorrect**: 4,000; 54000
-
-### Punctuation
-
-#### Serial comma
-
-**Use the serial comma**. The serial (also known as "Oxford") comma is the comma that appears before the conjunction in a series of three or more items.
-
-- **Correct**: I will travel on trains, planes, and automobiles.
-- **Incorrect**: I will travel on trains, planes and automobiles.
-
-> **Nota:** This is in contrast to the [One Mozilla style guide](http://www.mozilla.org/pt-BR/styleguide/), which specifies that the serial comma is not to be used. MDN is an exception to this rule.
-
-### Spelling
-
-For words with variant spellings, always use the first entry at [Answers.com](http://www.answers.com/library/Dictionary). Do not use variant spellings.
-
-- **Correct**: localize, honor
-- **Incorrect**: localise, honour
-
-### Terminology
-
-#### Obsolete vs. deprecated
-
-It's important to be clear on the difference between the terms **obsolete** and **deprecated**.
-
-- Obsolete:
- - : On MDN, the term **obsolete** marks an API or technology that is not only no longer recommended, but also no longer implemented in the browser. For Mozilla-specific technologies, the API is no longer implemented in Mozilla code; for Web standard technology, the API or feature is no longer supported by current, commonly-used browsers.
-- Deprecated:
- - : On MDN, the term **deprecated** marks an API or technology that is no longer recommended, but is still implemented and may still work. These technologies will in theory eventually become _obsolete_ and be removed, so you should stop using them. For Mozilla-specific technologies, the API is still supported in Mozilla code; for Web standard technology, the API or feature has been removed or replaced in a recent version of the defining standard.
-
-#### HTML elements
-
-Use "elements" to refer to HTML and XML elements, rather than "tags". In addition, they should almost always be wrapped in "<>", and should be in the {{HTMLElement("code")}} style. Also, at least the first time you reference a given element in a section should use the [`HTMLElement`](https://github.com/mdn/yari/blob/main/kumascript/macros/HTMLElement.ejs) macro, to create a link to the documentation for the element (unless you're writing within that element's reference document page).
-
-- **Correct**: the {{HTMLElement("span")}} element
-- **Incorrect**: the span tag
-
-#### User interface actions
-
-In task sequences, describe user interface actions using the imperative mood. Identify the user interface element by its label and type.
-
-- **Correct**: Click the Edit button.
-- **Incorrect**: Click Edit.
-
-### Voice
-
-While the active voice is generally preferred, the passive voice is also acceptable, given the informal feel of our content. Try to be consistent, though.
-
-## Wiki markup and usage
-
-### External links
-
-To automatically create a link to a Bugzilla bug, use this template:
-
-```
-\{{Bug(322603)}}
-```
-
-This results in:
-
-{{Bug(322603)}}
-
-### Page tags
-
-Tags provide meta information about a page and/or indicate that a page has specific improvements needed to its content. Every page in the wiki should have tags. You can find details on tagging in our [How to properly tag pages](/pt-BR/docs/MDN/Contribute/Howto/Tag) guide.
-
-The tagging interface lives at the bottom of a page while you're in edit mode, and looks something like this:
-
-
-
-To add a tag, click in the edit box at the end of the tag list and type the tag name you wish to add. Tags will autocomplete as you type. Press enter (or return) to submit the new tag. Each article may have as many tags as needed. For example, an article about using JavaScript in AJAX programming might have both "JavaScript" and "AJAX" as tags.
-
-To remove a tag, simply click the little "X" icon in the tag.
-
-#### Tagging pages that need work
-
-In addition to using tags to track information about the documentation's quality and content, we also use them to mark articles as needing specific types of work.
-
-#### Tagging obsolete pages
-
-Use the following tags for pages that are not current:
-
-- _Junk_: Use for spam, pages created by mistake, or content that is so bad that it should be deleted. Pages with this tag are deleted from time to time.
-- _Obsolete_: Use for content that is technically superceded, but still valid in context. For example an HTML element that is obsolete in HTML5 is still valid in HTML 4.01. You can also use the [`obsolete_header`](https://github.com/mdn/yari/blob/main/kumascript/macros/Obsolete_Header.ejs) macro to put a prominent banner on the topic.
-- _Archive_: Use for content that is technically superceded and no longer useful. If possible, add a note to the topic referring readers to a more current topic. For example, a page that describes how to use the Mozilla CVS repository should refer readers to a current topic on using Mercurial repos. (If no corresponding current topic exists, use the _NeedsUpdate_ tag, and add an explanation on the Talk page.) Pages with the Archive tag are eventually moved from the main content of MDN to the [Archive](/pt-BR/docs/Archive) section.
-
-### SEO summary
-
-The SEO summary is a very short summary of the page. It will be reported as a summary of the article to robots crawling the site, and will then appear in search results for the page. It is also used by macros that automate the construction of landing pages inside MDN itself.
-
-By default, the first pagragraph of the page is used as the SEO summary. However you can override this behavior by marking a section with the ["SEO summary" style in the WYSIWYG editor](/pt-BR/docs/Project:MDN/Contributing/Editor_guide/Editing#Formatting_styles).
-
-### Landing pages
-
-**Landing pages** are pages at the root of a topic area of the site, such as the main [CSS](/pt-BR/docs/CSS) or [HTML](/pt-BR/docs/HTML) pages. They have a standard format that consists of three areas:
-
-1. A brief (typically one paragraph) overview of what the technology is and what it's used for. See [Writing a landing page overview](#writing_a_landing_page_overview) for tips.
-2. A two-column list of links with appropriate headings. See [Creating a page link list](#creating_a_page_link_list) for guidelines.
-3. An **optional** "Browser compatibility" section at the bottom of the page.
-
-#### Creating a page link list
-
-The link list section of an MDN landing page consists of two columns. These are created using the following HTML:
-
-```html
-<div class="row topicpage-table">
- <div class="section">
- ... left column contents ...
- </div>
- <div class="section">
- ... right column contents ...
- </div>
-</div>
-```
-
-The left column should be a list of articles, with an `<h2>` header at the top of the left column explaining that it's a list of articles about the topic (for example "Documentation and tutorials about foo"); this header should use the CSS class "Documentation". Below that is a `<dl>` list of articles with each article's link in a `<dt>` block and a brief one-or-two sentence summary of the article in the corresponding `<dd>` block.
-
-The right column should contain one or more of the following sections, in order:
-
-- Getting help from the community
- - : This should provide information on Matrix rooms and mailing lists available about the topic. The heading should use the class "Community".
-- Tools
- - : A list of tools the user can look at to help with the use of the technology described in this section of MDN. The heading should use the class "Tools".
-- Related topics
- - : A list of links to landing pages for other, related, technologies of relevance. The heading should use the class "Related_Topics".
-
-**<<\<finish this once we finalize the landing page standards>>>**
-
-## Using, inserting images
-
-It's sometimes helpful to provide an image in an article you create or modify, especially if the article is very technical. To include an image:
-
-1. Attach the desired image file to the article (at the bottom of every article in edit mode)
-2. Create an image in the WYSIWYG editor
-3. In the WYSIWYG editor in the drop-down list listing attachments, select the newly created attachment which is your image
-4. Press OK.
-
-## Other References
-
-### Preferred style guides
-
-If you have questions about usage and style not covered here, we recommend referring to the [Economist style guide](http://www.economist.com/research/StyleGuide/) or, failing that, the [Chicago Manual of Style](http://www.amazon.com/gp/product/0226104036/).
-
-### Preferred dictionary
-
-For questions of spelling, please refer to [Answers.com](http://www.answers.com/library/Dictionary). The spell-checker for this site uses American English. Please do not use variant spellings (e.g., use _honor_ rather than _honour_).
-
-We will be expanding the guide over time, so if you have specific questions that aren't covered in this document, please send them to the [MDC mailing list](/pt-BR/docs/Project:Community) or [project lead](/User:Sheppy) so we know what should be added.
-
-### MDN-specific
-
-- [Custom CSS classes](/pt-BR/docs/Project:Custom_CSS_Classes) defined for all MDC pages.
-- [Custom templates](/pt-BR/docs/Project:Custom_Templates) created for use on MDC, with explanations.
-
-### Language, grammar, spelling
-
-If you're interested in improving your writing and editing skills, you may find the following resources to be helpful.
-
-- [On Writing Well](http://www.amazon.com/Writing-Well-30th-Anniversary-Nonfiction/dp/0060891548), by William Zinsser (Amazon link)
-- [Style: The Basics of Clarity and Grace](http://www.amazon.com/Style-Basics-Clarity-Grace-4th/dp/0205830765/), by Joseph Williams and Gregory Colomb (Amazon link)
-- [American Heritage Book of English Usage](http://www.bartleby.com/64/)
-- [Common Errors in English](http://www.wsu.edu/~brians/errors/)
-- [English Grammar FAQ](http://www-personal.umich.edu/~jlawler/aue.html) (alt.usage.english)
-- [Bob's quick guide to the apostrophe, you idiots](http://www.angryflower.com/bobsqu.gif) (funny)
-- [Merriam-Webster's Concise Dictionary of English Usage](http://www.amazon.com/Merriam-Websters-Concise-Dictionary-English-Usage/dp/B004L2KNI2) (Amazon link): Scholarly but user-friendly, evidence-based advice; very good for non-native speakers, especially for preposition usage.
diff --git a/files/pt-br/mdn/writing_guidelines/writing_style_guide/syntax-highlighting-menu.png b/files/pt-br/mdn/writing_guidelines/writing_style_guide/syntax-highlighting-menu.png
deleted file mode 100644
index ee0a58906d65dc..00000000000000
Binary files a/files/pt-br/mdn/writing_guidelines/writing_style_guide/syntax-highlighting-menu.png and /dev/null differ
diff --git a/files/pt-br/mdn/writing_guidelines/writing_style_guide/tag-interface.png b/files/pt-br/mdn/writing_guidelines/writing_style_guide/tag-interface.png
deleted file mode 100644
index 255c72295c255a..00000000000000
Binary files a/files/pt-br/mdn/writing_guidelines/writing_style_guide/tag-interface.png and /dev/null differ
diff --git a/files/pt-br/mozilla/firefox/experimental_features/index.md b/files/pt-br/mozilla/firefox/experimental_features/index.md
deleted file mode 100644
index abd7fda3be47e3..00000000000000
--- a/files/pt-br/mozilla/firefox/experimental_features/index.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Novas funcionalidades no Firefox
-slug: Mozilla/Firefox/Experimental_features
-original_slug: Mozilla/Firefox/Novas_funcionalidades
----
-
-{{FirefoxSidebar}}
-
-Com intuito de testar as novas funcionalidades, a Mozilla publica uma versão de testes do navegador Firefox, [Firefox Nightly](https://nightly.mozilla.org/), diariamente. Funcionalidades experimentais, por exemplo implementações de propostas de padrões para plataforma Web, estão disponíveis. Essa página lista funcionalidades que estão nas versões Nightly do Firefox juntamente com informações de como ativá-las, se necessário. Você pode testar seus websites e aplicações antes dessas funcionalidades serem lançadas e garantir que tudo ainda irá funcionar com os recursos mais recentes da tecnologia da Web.
-
-Para testar essas funcionalidades experimentais, você precisa baixar o [Firefox Nightly](https://nightly.mozilla.org/) ou o [Firefox Developer Edition](https://www.mozilla.org/pt-BR/firefox/developer/).
-
-## CSS
-
-| Feature | Firefox Nightly | Firefox Developer Edition | Firefox Beta | Firefox Release | Preference |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------ |
-| **[Grid Layout](/pt-BR/docs/Web/CSS/CSS_Grid_Layout)** | 40 | 40 | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1217086) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1217086) | `layout.css.grid.enabled` |
-| **Subgrids** | Disabled | Disabled | Disabled | Disabled | `layout.css.grid-template-subgrid-value.enabled` |
-| **Logical values for `clear` and `float` CSS properties** The values `{{cssxref("clear")}}: inline-start` and `clear: inline-end` as well as `{{cssxref("float")}}: inline-start` and `float: inline-end` are making easier to create layouts that are agnostic to the text directionality. | 45 | 45 | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1253919) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1253919) | `layout.css.float-logical-values.enabled` |
-| **Display stray control characters in CSS as hex boxes** This feature renders control characters (Unicode category Cc) other than _tab_ (`U+0009`), _line feed_ (`U+000A`), _form feed_ (`U+000C`), and _carriage return_ (`U+000D`) as a hexbox when they are not expected. | 43 | 43 | Disabled | Disabled | `layout.css.control-characters.enabled` |
-| **The `transform-box` property** Controls the box the relative values of {{cssxref("transform-origin")}} and {{cssxref("transform")}} relate too. | 41 | 41 | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1208550) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1208550) | `svg.transform-box.enabled` |
-| **Basic shapes in** **`clip-path`** Adds the functions `circle()`, `ellipse()`, and `polygon()` to the set of possible values for {{cssxref("clip-path")}}. | [Enabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1303654) (available since 47, enabled by default since 53) | [Enabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1303654) (available since 47, enabled by default since 53) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1247229) (available since 47) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1247229) (available since 47) | `layout.css.clip-path-shapes.enabled` |
-| **The `font-display` descriptor for `@font-face`** To improve Web fonts performance, {{cssxref("@font-face")}} has an experimental {{cssxref("@font-face/font-display", "font-display")}} descriptor. | Disabled (available since 46) | Disabled (available since 46) | Disabled (available since 46) | Disabled (available since 46) | `layout.css.font-display.enabled` |
-| **Longhand properties of CSS Masks** The [longhand properties of CSS Masks](/pt-BR/docs/Web/CSS/CSS_Masks) are only available behind a compile flag (`MOZ_ENABLE_MASK_AS_SHORTHAND`). | --- | --- | --- | --- | --- |
-| **The touch-action CSS property** The {{cssxref("touch-action")}} CSS property is part of the {{SpecName("Pointer Events")}} specification, and lets the CSS specify how and in what way the user is able to manipulate an object by touch. | 50 | --- | --- | --- | `layout.css.touch_action.enabled` |
-
-## JavaScript
-
-See also [ECMAScript Next support](/pt-BR/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_Next_support_in_Mozilla) for implemented features of ECMAScript 2016 and later, that are not experimental and thus available without preferences in Firefox Release.
-
-| Feature | Firefox Nightly | Firefox Developer Edition | Firefox Beta | Firefox Release | Preference |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------- | ------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------- | ---------------------------------- |
-| **[Exponentiation operator](/pt-BR/docs/Web/JavaScript/Reference/Operators/Arithmetic_Operators#Exponentiation)** | 42 | Will ship in version 52, see {{bug(1291212)}} | Will ship in version 52, see {{bug(1291212)}} | Will ship in version 52, see {{bug(1291212)}} | None |
-| **Additions to the `ArrayBuffer` object** Adds the {{jsxref("ArrayBuffer.transfer()")}} that returns a new `ArrayBuffer` whose contents have been taken from the `oldBuffer`'s data ([spec](https://gist.github.com/lukewagner/2735af7eea411e18cf20)). | 36 | Disabled | Disabled | Disabled | None |
-| **TypedObject objects** ([spec](https://github.com/dslomov-chromium/typed-objects-es7)) | Enabled | Disabled | Disabled | Disabled | None |
-| [SIMD](/pt-BR/docs/Web/JavaScript/Reference/Global_Objects/SIMD) ([specification and polyfill](https://github.com/johnmccutchan/ecmascript_simd)) | Enabled | Disabled | Disabled | Disabled | None |
-| **Shared Memory objects** {{jsxref("SharedArrayBuffer")}} {{jsxref("Atomics")}} | Enabled (available since 46) | Disabled (available since 46) | Disabled (available since 46) | Disabled (available since 46) | `javascript.options.shared_memory` |
-
-## APIs
-
-### Canvas & WebGL
-
-| Feature | Firefox Nightly | Firefox Developer Edition | Firefox Beta | Firefox Release | Preference |
-| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ----------------------------- | --------------------------------------------------------------- | --------------------------------------------------------------- | ---------------------------------- |
-| **WebGL 2** The {{domxref("WebGL2RenderingContext")}} interface provides the OpenGL ES 3.0 rendering context for the drawing surface of an HTML {{HTMLElement("canvas")}} element. | 46 (implemented with disabled pref before 46) | Enabled in 51 | Enabled in 51 | Enabled in 51 | `webgl.enable-webgl2` |
-| **`WEBGL_debug_renderer_info` extension** The {{domxref("WEBGL_debug_renderer_info")}} extension allows to transmit information useful to help debugging problems to the server. | 42 | 42 | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=742798) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=742798) | `webgl.enable-debug-renderer-info` |
-| **OffscreenCanvas** The {{domxref("OffscreenCanvas")}} interface provides a canvas that can be rendered off screen. It is available in both the window and [worker](/pt-BR/docs/Web/API/Web_Workers_API) contexts. | Disabled (available since 44) | Disabled (available since 44) | Disabled (available since 44) | Disabled (available since 44) | `gfx.offscreencanvas.enabled` |
-| **[Hit regions](/pt-BR/docs/Web/API/Canvas_API/Tutorial/Hit_regions_and_accessibility)** Whether the mouse coordinates are within a particular area on the canvas, is a common problem to solve. The hit region API allows you define an area of your canvas and provides another possibility to expose interactive content on a canvas to accessibility tools. | Disabled (available since 30) | Disabled (available since 30) | Disabled (available since 30) | Disabled (available since 30) | `canvas.hitregions.enabled` |
-
-### DOM
-
-| Feature | Firefox Nightly | Firefox Developer Edition | Firefox Beta | Firefox Release | Preference |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
-| **WebVR API** The [WebVR API](/pt-BR/docs/Web/API/WebVR_API) allows to control and use virtual reality devices. | 46 A major update of the interface happened in version 51. | 46 A major update of the interface happened in version 51. | Disabled | Disabled | `dom.vr.enabled` |
-| **FlyWeb** [FlyWeb](https://flyweb.github.io/) is a project at Mozilla focused on bringing a new set of APIs to the browser for advertising and discovering local-area web servers. | 51 | Disabled | Disabled | Disabled | `dom.flyweb.enabled` |
-| **`HTMLMediaElement.seekToNextFrame()`** Part of an experimentation process around support non-real-time access to media for tasks including filtering, editing, and so forth, the {{domxref("HTMLMediaElement.seekToNextFrame()")}} advances the the current play position to the next frame in the media. | 49 (Fundamental update in version 50) | 49 (Fundamental update in version 50) | Disabled | Disabled | `media.seekToNextFrame.enabled` |
-| **`GeometryUtils.getBoxQuads()`** ({{bug(917755)}}) | 31 | 31 | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1107559) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1107559) | `layout.css.getBoxQuads.enabled` |
-| **`GeometryUtils.convertPointFromNode()`**, **`GeometryUtils.RectFromNode()`**, and **`GeometryUtils.convertQuadFromNode()`** ({{bug(918189)}}) | 31 | 31 | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1107559) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1107559) | `layout.css.convertFromNode.enabled` |
-| **`Node.rootNode`** The {{domxref("Node.rootNode")}} property returns a {{domxref("Node")}} object representing the topmost node in the tree, or the current node if it's the topmost node in the tree. _This feature is kept experimental as its naming poses Web compatibility problems. It will be renamed in the future._ | 48 | 48 | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1269155) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1269155) | `dom.node.rootNode.enabled` |
-| **Performance Observer API** The {{domxref("PerformanceObserver")}} interface is used to _observe_ performance measurement events and be notified of new [performance entries](/pt-BR/docs/Web/API/PerformanceEntry) as they are recorded in the browser's _performance timeline_. | 49 | Disabled | Disabled | Disabled | `dom.enable_performance_observer` |
-| **WebVTT Regions API** [WebVTT](/pt-BR/docs/Web/API/Web_Video_Text_Tracks_Format) regions are parts of the video viewport that provide a rendering area for WebVTT cues. The {{domxref("VTTRegion")}} is the interface exposing the WebVTT cues. _This interface is considered to be in flux and isn't therefore activated in any version by default._ | Disabled (Experimental implementation since version 30) | Disabled | Disabled | Disabled | `media.webvtt.regions.enabled` |
-| **Support for audio and video tracks** Implements {{domxref("HTMLMediaElement.audioTracks")}} and {{domxref("HTMLMediaElment.videoTracks")}}. _Firefox doesn't support multiple audio or video tracks, preventing the most common use cases for these properties to work properly. That's why these properties are not activated by default in any version._ | Disabled (Experimental implementation since version 33) | Disabled | Disabled | Disabled | `media.track.enabled` |
-| **Better value for `Event.timestamp`** The property {{domxref("Event.timestamp")}} is returning a {{domxref("DOMHighResTimeStamp")}}, but the value is not the time since but since the reboot. This change allow for returning a timestamp relative to the Unix epoch. | 32 (Windows) 43 (Linux) | 32 (Windows) 43 (Linux) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1026804) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1026804) | `media.track.enabled` |
-| **Pointer Events** | 50 | Disabled | Disabled | Disabled | `dom.w3c_pointer_events.enabled` |
-| **`MediaDevices.ondevicechange` and the `devicechange` event** The {{domxref("MediaDevices.ondevicechange")}} event handler and corresponding {{event("devicechange")}} event make it possible to detect and react when audio and video devices are attached to or removed from the computer. | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1308115) 51 (Mac)Enabled 52 (Mac) 52 (Windows) 52 (Linux) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1308115) 51 (Mac)Enabled 52 (Mac) 52 (Windows) 52 (Linux) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1308115) 51 (Mac)Enabled 52 (Mac) 52 (Windows) 52 (Linux) | [Disabled](https://bugzilla.mozilla.org/show_bug.cgi?id=1308115) 51 (Mac)Enabled 52 (Mac) 52 (Windows) 52 (Linux) | `media.ondevicechange.enabled` |
-
-## Developer Tools
-
-| Feature | Firefox Nightly | Firefox Developer Edition | Firefox Beta | Firefox Release | Preference |
-| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------------- | ------------ | --------------- | ------------------------------------------ |
-| **Debugger rewrite in HTML** | 52 | 52 | 52 | 52 | `devtools.debugger.new-debugger-frontend` |
-| **Console rewrite in HTML** | 52 | Disabled | Disabled | Disabled | `devtools.webconsole.new-frontend-enabled` |
-| **Responsive Design Mode rewrite in HTML** A rewrite of Responsive Design Mode using HTML adds new features like a device selector (applies size, UA, dPR), UI redesign, and there's more still to come. | 52 | 52 | 52 | 52 | `devtools.responsive.html.enabled` |
-| **Experimental Performance tool options** Enables options in the UI for JIT optimizations, memory, etc. | 41 | Disabled | Disabled | Disabled | `devtools.performance.ui.experimental` |
-
-## See also
-
-- [Firefox developer release notes](/pt-BR/docs/Mozilla/Firefox/Releases)
-- [Firefox Nightly](https://nightly.mozilla.org/)
-- [Firefox Developer Edition](https://www.mozilla.org/pt-BR/firefox/developer/)
diff --git a/files/pt-br/mozilla/firefox/releases/50/index.md b/files/pt-br/mozilla/firefox/releases/50/index.md
deleted file mode 100644
index 1a894347f6ea3e..00000000000000
--- a/files/pt-br/mozilla/firefox/releases/50/index.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: Firefox 50 for developers
-slug: Mozilla/Firefox/Releases/50
----
-{{FirefoxSidebar}}
-
-O Firefox 50 foi lançado em 15 de novembro de 2016. Este artigo lista as principais alterações que são úteis não só para os desenvolvedores Web, mas também para os desenvolvedores do Firefox e Gecko, assim como os desenvolvedores do Add-on.
-
-## Mudanças para desenvolvedores web
-
-### Developer Tools
-
-Nenhuma mudança.
-
-### HTML
-
-- For compatibility purposes, the non-standard [`webkitdirectory`](/pt-BR/docs/Web/HTML/Element/input#webkitdirectory) attribute of the {{HTMLElement("input")}} element, as well as the property {{domxref("HTMLInputElement.webkitDirectory")}} property, have been implemented ({{bug(1258489)}}).
-- The default style of {{HTMLElement("bdo")}} now has a {{cssxref("unicode-bidi")}} with the `isolate-override` value ({{bug(1249497)}}).
-
-### CSS
-
-- Border-radiused corner with dashed and dotted style is now rendered with specified style instead of solid style ({{bug(382721)}}).
-- The non-standard {{cssxref(":-moz-full-screen-ancestor")}} pseudo-class selector has been removed ({{bug(1199529)}}).
-- The {{cssxref("box-sizing")}}`: padding-box` has been removed, since it’s no longer a part of the spec and Firefox was the only major browser to implement it ({{bug(1166728)}}).
-- Our experimental implementation of {{cssxref('mask-position')}} now supports animation of this property ({{bug(1273804)}}). It is still available only on Nightly.
-- The three values `isolate`, `isolate-override`, and `plaintext` of the {{cssxref("unicode-bidi")}} have been unprefixed ({{bug(1141895)}}).
-- In quirk mode, the bullet of a list now inherit the size of the list, like in standard mode ({{bug(648331)}}).
-- Changed behavior of the {{cssxref(":in-range")}} and {{cssxref(":out-of-range")}} pseudo-classes to not match disabled or read-only inputs ({{bug(1264157)}}).
-- Unprefixed {{cssxref(":any-link")}} pseudo-class {{bug(843579)}}.
-- Implemented `space` value of {{cssxref("border-image-repeat")}} ({{bug(720531)}}).
-
-### JavaScript
-
-- The ES2015 {{jsxref("Symbol.hasInstance")}} property has been implemented ({{bug(1054906)}}).
-- The ES2017 {{jsxref("Object.getOwnPropertyDescriptors()")}} method has been implemented ({{bug(1245024)}}).
-- The behavior of \W in {{jsxref("RegExp")}} with unicode and ignoreCase flags is changed to match recent draft spec. Now it doesn't match to K, S, k, s, and KELVIN SIGN (U+212A), and LATIN SMALL LETTER LONG S (U+017F) ({{bug(1281739)}}).
-
-### Interfaces/APIs/DOM
-
-#### DOM & HTML DOM
-
-- The {{domxref("HTMLInputElement.webkitdirectory")}} property is now supported ({{bug(1258489)}}).
-- Support `once` option for {{domxref("EventTarget.addEventListener()")}} ({{bug(1287706)}}).
-
-#### Canvas
-
-_No change._
-
-#### WebGL
-
-- The {{domxref("EXT_shader_texture_lod")}} WebGL extension has been implemented ({{bug(1111689)}}).
-
-#### IndexedDB
-
-_No change._
-
-#### Service Workers
-
-- The {{domxref("WindowClient.navigate()")}} method has been implemented. This method lets you open a specified URL into a client window which is being controlled by the service worker ({{bug(1218148)}}).
-
-#### WebRTC
-
-- The {{domxref("RTCDataChannel.stream")}} property has been removed. This was replaced with {{domxref("RTCDataChannel.id")}} in [Firefox 24](/pt-BR/docs/Mozilla/Firefox/Releases/24), but was supported for backward compatibility. Please be sure to update your code to use the `id` property if you haven't done so yet.
-
-#### New APIs
-
-_No change._
-
-#### Others
-
-- {{domxref("XMLHttpRequest.getResponseHeader()")}} and {{domxref("XMLHttpRequest.getAllResponseHeaders()")}} now also return empty headers by default. This can be controlled via the preference `network.http.keep_empty_response_headers_as_empty_string` ({{bug(918721)}}).
-
-### MathML
-
-_No change._
-
-### SVG
-
-_No change._
-
-### Audio/Video
-
-_No change._
-
-## HTTP
-
-- The experimental (and deprecated) [SPDY](https://en.wikipedia.org/wiki/SPDY) 3.1 is now disable by default {{bug(1287132)}}.
-- Support for {{HTTPHeader("X-Content-Type-Options")}} has been added ({{bug(471020)}}).
-
-## Networking
-
-- The [`ping`](/pt-BR/docs/Web/HTML/Element/a#ping) attribute of {{htmlelement("a")}} element is now abiding by the [`connect-src`](/pt-BR/docs/Web/Security/CSP/CSP_policy_directives#connect-src) [CSP 1.1 policy directive](/pt-BR/docs/Web/Security/CSP/CSP_policy_directives) ({{bug(1100181)}}).
-- Support of the [`sandbox`](/pt-BR/docs/Web/Security/CSP/CSP_policy_directives#sandbox) [CSP](/pt-BR/docs/Web/Security/CSP) directive has been added ({{bug(671389)}}).
-
-## Segurança
-
-Nenhuma mudança.
-
-## Changes for add-on and Mozilla developers
-
-### Interfaces
-
-_No change._
-
-### XUL
-
-_No change._
-
-### JavaScript code modules
-
-_No change._
-
-### XPCOM
-
-_No change._
-
-### Outroas
-
-_No change._
-
-## Versões mais antigas
-
-{{Firefox_for_developers(49)}}
diff --git a/files/pt-br/mozilla/firefox/releases/57/index.md b/files/pt-br/mozilla/firefox/releases/57/index.md
deleted file mode 100644
index a40bef43f84d15..00000000000000
--- a/files/pt-br/mozilla/firefox/releases/57/index.md
+++ /dev/null
@@ -1,237 +0,0 @@
----
-title: Firefox Quantum 57 for developers
-slug: Mozilla/Firefox/Releases/57
----
-
-{{FirefoxSidebar}}This article provides information about the changes in Firefox 57 (a.k.a. Firefox Quantum) that will affect developers. Firefox 57 was released on November 14, 2017.
-
-## Firefox 57 === Firefox Quantum
-
-O Firefox 57 recebeu o nome de lançamento **Quantum**, após o projeto de engenharia Firefox [Quantum](https://wiki.mozilla.org/Quantum) que tem como objetivo reconstruir o Firefox a partir do zero, trazendo consigo grande desempenho, estabilidade e melhorias visuais. This is the first version of Firefox to ship some of these improvements, so we wanted to mark the occasion.
-
-> **Nota:** Para ler mais sobre os recursos do Quantum nesta versão, veja: [Firefox Quantum Developer Edition: the fastest Firefox ever with Photon UI and better tooling](https://hacks.mozilla.org/2017/09/firefox-quantum-developer-edition-fastest-firefox-ever/) por Dan Callahan.
-
-[Firefox's new parallel CSS engine](https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-engine-quantum-css-aka-stylo/) — também conhecido como **Quantum CSS** ou **Stylo** ─ está habilitado por padrão no Firefox 57 para desktop, com versões móveis do Firefox para seguir mais tarde. Os desenvolvedores não devem notar nada significativamente diferente, além de toda uma série de melhorias de desempenho. Existem, no entanto, algumas pequenas diferenças funcionais no Stylo, implementado para corrigir o comportamento não padronizado do Gecko que deve ser eliminado. Nos reportaremos tais diferenças nas páginas de referência e nas notas de lançamento conforme apropriado (veja [Quantum CSS notes](#quantum_css_notes)).
-
-## Changes for Web developers
-
-### Ferramentas de desenvolvimento
-
-Sem mudanças.
-
-### HTML
-
-- Os types {{htmlelement("input")}} [date](/pt-BR/docs/Web/HTML/Element/Input/data) e [time](/pt-BR/docs/Web/HTML/Element/Input/time) agora estão habilitados em todos builds. ({{bug("1399036")}})
-
-### CSS
-
-- Os valores `minimal-ui` e `standalone` do media query [display-mode](/pt-BR/docs/Web/CSS/@media/display-mode) agora são suportados ({{bug(1369815)}}). Veja também o [Web app manifest `display` field](/pt-BR/docs/Web/Manifest#display).
-- As propriedades {{CSSxRef("grid-row-gap")}} e {{CSSxRef("grid-column-gap")}} não são mais redefinidas pelo {{CSSxRef("grid")}} de forma abreviada ({{bug(1387410)}}).
-- A preferência `layout.css.clip-path-shapes.enabled` foi removida ({{bug(1399767)}}). Esta preferência permite desabilitar a {{CSSxRef("<basic-shape>")}} suportado em {{CSSxRef("clip-path")}}. Este suporte foi enviado no Firefox 54 e não pode mais ser desativado.
-
-#### Quantum CSS notes
-
-Following bugs have been fixed in Quantum:
-
-- Radial gradient values like `radial-gradient(circle gold,red)` will work in the old Gecko style system, even though they shouldn't because of the missing comma between `circle` and `gold` ({{bug(1383323)}}).
-- When you animate an offscreen element onscreen but specify a delay, Gecko does not repaint on some platforms, e.g. Windows ({{bug(1383239)}}).
-- In Gecko, {{htmlelement("details")}} elements can't be made open by default using the `open` attribute if they have an {{CSSxRef("animation")}} active on them ({{bug(1382124)}}).
-- In Gecko, {{CSSxRef("transition", "transitions")}} will not work when transitioning from a {{CSSxRef("text-shadow")}} with a color specified to a `text-shadow` without a color specified ({{bug(726550)}}).
-- In Gecko, cancelling a filling animation (e.g. with `animation-fill-mode: forwards` set) can trigger a transition set on the same element, although only once (see {{bug(1192592)}} and [these test cases](https://bug1192592.bmoattachments.org/attachment.cgi?id=8843824) for more information). In general declarative animations should not trigger transitions.
-- Animations using em units are not affected by changes to the {{CSSxRef("font-size")}} on the animated element's parent in Gecko, whereas they should be ({{bug(1254424)}}).
-- Gecko also deals with `font-size` inheritance differently from Quantum CSS, meaning that for some language settings inherited font sizes end up being smaller than expected (see {{bug(1391341)}}).
-- Gecko reuses the same mechanism used when parsing a url-token when parsing the `domain()` or `url-prefix()` URL matching functions for a {{CSSxRef("@document", "@-moz-document")}} rule. Quantum CSS does not use the same mechanism and it does not consider tokens invalid when they contain brackets or quotes ({{bug(1362333)}}).
-- In Gecko, when you set a system font as the value of a canvas 2D context's {{DOMxRef("CanvasRenderingContext2D.font", "font")}} (e.g. `menu`), getting the font value fails to return the expected font (it returns nothing). This has been fixed in Quantum. ({{bug(1374885)}}).
-- In Gecko, when you create a detached subtree (e.g. a {{htmlelement("div")}} created using {{DOMxRef("Document.createElement","createElement()")}} that is not yet inserted into the DOM), the subtree's root element is set as a block-level element. In Quantum CSS this is set as inline, as per spec ({{bug(1374994)}}).
-- In Gecko, {{CSSxRef("calc")}} expressions are rejected — causing the value to be invalid — when used as the radius component of a {{CSSxRef("radial-gradient")}} function ({{bug(1376019)}}).
-- In Gecko, `calc(1*2*3)` is not parsed successfully; Quantum CSS fixes this ({{bug(1379467)}}).
-- In Quantum CSS, [`calc()` is supported everywhere that the spec explains it should be](https://drafts.csswg.org/css-values-3/#calc-notation) ({{bug(1350857)}}). In Gecko it is not.
-- Gecko has a bug whereby the {{CSSxRef("::before")}} and {{CSSxRef("::after")}} pseudo-elements are still generated even if the {{CSSxRef("content")}} property value is set to `normal` or `none`. As per spec, they shouldn't be ({{bug(1387931)}}).
-- Another Gecko bug means that the {{CSSxRef("background-position")}} property can't be transitioned between two values containing different numbers of {{CSSxRef("<position>")}} values, for example `background-position: 10px 10px;` and `background-position: 20px 20px, 30px 30px;` (see {{bug(1390446)}}).
-
-### SVG
-
-Sem mudanças.
-
-### JavaScript
-
-- O não-padronizado {{JSxRef("Statements/for_each...in", "for each...in")}} (E4X) loop foi removido. Por favor, use o {{JSxRef("Statements/for...of", "for...of")}} ao invés disso e veja [Warning: JavaScript 1.6's for-each-in loops are deprecated](/pt-BR/docs/Web/JavaScript/Reference/Errors/For-each-in_loops_are_deprecated) para ajudar na migração. ({{bug(1083470)}}).
-- Os métodos {{JSxRef("Object.prototype.watch()")}} e {{JSxRef("Object.unwatch", "unwatch()")}} estão descontinuados, agora lançará um alerta(warning) quando usado, e será removido em breve. ({{bug(934669)}}).
-- Os objetos não-padronizados Iterator e StopIteration assim como o protocolo de iteração legado foram removidos ({{bug(1098412)}}).
-- Async generator está agora ativado. ({{bug(1352312)}}).
-- A sintaxe for await (...of...) está agora ativado. ({{bug(1352312)}}).
-
-#### Novas APIs
-
-- A {{DOMxRef("PerformanceObserver")}} está habilitado por padrão(default). ({{bug(1386021)}}).
-- As interfaces {{DOMxRef("AbortController")}} e {{DOMxRef("AbortSignal")}} (conhecidos como o Abort API) foram adicionados, permitindo requisições DOM (tal como [fetch requests](/pt-BR/docs/Web/API/WindowOrWorkerGlobalScope/fetch)) ser abortado se desejar. ({{bug(1378342)}}).
-- \[2] O [Storage API](/pt-BR/docs/Web/API/Storage_API) está implementado e habilitado por padrão(default). ({{bug(1399038)}}).
-
-#### DOM
-
-- A propriedade {{DOMxRef("Selection.type")}} do [Selection API](/pt-BR/docs/Web/API/Selection_API) está agora implementado ({{bug(1359157)}}).
-- {{DOMxRef("Document.createEvent", "Document.createEvent('FocusEvent')")}} está agora implementado ({{bug(1388069)}}).
-- A propriedade `files` da interface {{DOMxRef("HTMLInputElement")}} está agora definível ({{bug(1384030)}}).
-- O método `HTMLDocument.getSelection()` foi movido para a interface {{DOMxRef("Document.getSelection","Document")}}, por isso está disponível para documentos XML ({{bug(718711)}}).
-- O evento {{Event("messageerror")}} está agora implementado e pode ter código executado em resposta a disparar através de manipuladores de eventos implementados em destinos de mensagens ─ Veja {{DOMxRef("MessagePort.onmessageerror")}}, {{DOMxRef("DedicatedWorkerGlobalScope.onmessageerror")}}, {{DOMxRef("Worker.onmessageerror")}}, {{DOMxRef("BroadcastChannel.onmessageerror")}}, e {{DOMxRef("Window.onmessageerror")}} ({{bug(1359017)}}).
-- Quando os valores do {{DOMxRef("Headers")}} são iterados, eles são automaticamente classificados em ordem lexicográfico e valores de nomes de cabeçalho duplicados são combinados ({{bug(1396848)}}).
-
-#### DOM events
-
-Sem mudanças.
-
-#### Media and WebRTC
-
-- Suporte para mensagens de tamanho arbitrário (até 1GiB, apesar de 256kiB é mais interoperável) está agora suportados em {{DOMxRef("RTCDataChannel")}} através do uso da flag end-of-record (EOR) em messagens SCTP. Veja [Noções básicas sobre limites de tamanho de mensagem](/pt-BR/docs/Web/API/WebRTC_API/Using_data_channels#understanding_message_size_limits) para mais informações ({{bug(979417)}}).
-
- > **Nota:** Porque o Firefox ainda não suporta o protocolo SCTP ndata que fornece a capacidade de intercalar mensagens SCTP de múltiplas fontes, o envio de objetos de dados grandes pode causar atrasos significativos em todos os outros tráfegos SCTP. Veja {{bug(1381145)}} para acompanhar o progresso na implementação e implementação do suporte a ndata no Firefox.
-
-- O método {{DOMxRef("RTCDataChannel.send()")}} pode agora lançar uma exceção `TypeError` se o tamanho da mensagem que você está tentando enviar não é compatível com o recebimento {{Glossary("user agent")}} (Isto está implementado como parte do {{bug(979417)}}).
-- O [MediaStream Recording API](/pt-BR/docs/Web/API/MediaStream_Recording_API) foi atualizado, assim, os eventos de {{event("error")}} enviados para relatar problemas que ocorrem durante a gravação agora são do tipo {{DOMxRef("MediaRecorderErrorEvent")}}, em vez de serem eventos genéricos.
-- Atualizado a documentação ao redor {{DOMxRef("OfflineAudioContext")}} desde o seu campos construtores pode agora se especificado ao invés de uma lista de parâmetros ({{bug(1388591)}}).
-- O [Web Audio API](/pt-BR/docs/Web/API/API_Web_Audio) agora suporta corretamente a saída multicanal ({{bug(1378070)}}).
-
-### Security
-
-- URLs `resources://` não mais vazar informações ({{bug(863246)}}).
-- Data URIs agora são tratados como origens opacas únicas, em vez de herdar a origem do objeto de configuração responsável pela navegação ({{bug(1324406)}}).
-
-### Plugins
-
-Sem mudanças.
-
-### Outros
-
-- Firefox [headless mode](/pt-BR/docs/Mozilla/Firefox/Headless_mode) agora incluídos uma flag `-screenshot` que permite você pegar screenshots de website diretamente da linha de comando ({{bug(1378010)}}).
-
-## Removals from the web platform
-
-### HTML
-
-- `<link rel=”preload”>` (see [Preloading content with rel="preload"](/pt-BR/docs/Web/HTML/Preloading_content)) foi desabilitado no Firefox 57 por causa de vários problemas de compatibilidade da web (por exemplo {{bug(1405761)}}). Espera-se que uma versão melhorada que funcione para recursos não armazenáveis em cache chegue ao Firefox 58.
-
-### APIs
-
-- Propriedade da Mozilla [Social API](/pt-BR/docs/Archive/Social_API) foi completamente removido ({{bug(1388902)}}).
-
-### SVG
-
-Sem mudanças.
-
-## Alterações para add-on e desenvolvedores Mozilla
-
-> **Nota:** Começando no Firefox 57, todo suporte para XPCOM-based add-ons foi removido. Todas as extensões devem ser convertidas no novo [browser extensions](/pt-BR/Add-ons/WebExtensions) (também conhecido como WebExtensions) ou eles não vão funcionar.
-
-### WebExtensions
-
-As seguintes APIs foram adicionadas ou estendidas:
-
-- [`bookmarks`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/bookmarks)
-
- - support for separators through [`bookmarks.BookmarkTreeNodeType`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/bookmarks/BookmarkTreeNodeType)
-
-- [`browser_action`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_action)
-
- - `theme_icons` property for light/dark theme icons
-
-- [`browserAction`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/browserAction)
-
- - [`browserAction.openPopup()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/browserAction/openPopup)
-
-- [`browserSettings`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/browserSettings)
-
- - [`allowPopupsForUserEvents`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/browserSettings/allowPopupsForUserEvents)
- - [`homepageOverride`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/browserSettings/homepageOverride)
- - [`imageAnimationBehavior`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/browserSettings/imageAnimationBehavior)
- - [`newTabPageOverride`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/browserSettings/newTabPageOverride)
-
-- [`browsingData`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/browsingData)
-
- - [`browsingData.removeLocalStorage()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/browsingData/removeLocalStorage)
-
-- [`clipboard`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/clipboard)
-
- - [`setImageData()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/clipboard/setImageData)
-
-- [`contextualIdentities`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/contextualIdentities)
-
- - [`onCreated`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/contextualIdentities/onCreated)
- - [`onRemoved`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/contextualIdentities/onRemoved)
- - [`onUpdated`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/contextualIdentities/onUpdated)
- - `colorCode` and `iconUrl` in [`contextualIdentitities.ContextualIdentity`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/contextualIdentities/ContextualIdentity)
-
-- [`devtools.panels`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/devtools.panels)
-
- - [`devtools.panels.ElementsPanel.createSidebarPane()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/devtools.panels/ElementsPanel/createSidebarPane)
-
-- [`downloads`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/downloads)
-
- - `incognito` option in [`downloads.download()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/downloads/download)
- - `estimatedEndTime` property in [`downloads.DownloadItem`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/downloads/DownloadItem)
-
-- [`find`](/pt-BR/Add-ons/WebExtensions/API/find)
-
- - [`find()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/find/find)
- - [`highlightResults()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/find/highlightResults)
- - [`removeHighlighting()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/find/removeHighlighting)
-
-- [`pageAction.openPopup()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/pageAction/openPopup)
-- [`privacy`](/pt-BR/Add-ons/WebExtensions/API/privacy/websites)
-
- - [`websites.trackingProtectionMode`](/pt-BR/Add-ons/WebExtensions/API/privacy/websites)
-
-- [`proxy`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/proxy)
-
- - `FindProxyForURL()` can now return an object
-
-- [`runtime`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/runtime)
-
- - [`runtime.openOptionsPage()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/runtime/openOptionsPage) support on Android
-
-- [`sessions`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/sessions)
-
- - [`setTabValue()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/sessions/setTabValue)
- - [`getTabValue()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/sessions/getTabValue)
- - [`removeTabValue()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/sessions/removeTabValue)
- - [`setWindowValue()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/sessions/setWindowValue)
- - [`getWindowValue()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/sessions/getWindowValue)
- - [`removeWindowValue()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/sessions/removeWindowValue)
-
-- [`sidebarAction`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/sidebarAction)
-
- - [`sidebarAction.open()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/sidebarAction/open)
-
-- [`storage`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/storage)
-
- - [`storage.managed`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/storage/managed)
-
-- [`tabs`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/tabs)
-
- - `loadReplace` option in [`tabs.update()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/tabs/update)
- - `discarded` property in [`tabs.Tab`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/tabs/Tab), [`tabs.onUpdated`](/pt-BR/docs/), and [`tabs.query()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/tabs/query)
- - [`tabs.create()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/tabs/create) can open "view-source:" URLs
- - `openerTabId` property in [`tabs.Tab`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/tabs/Tab), [`tabs.create()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/tabs/create), [`tabs.query()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/tabs/query), and [`tabs.update()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/tabs/update)
-
-- [`theme`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/manifest.json/theme)
-
- - `colors.toolbar`
- - `colors.toolbar_field`
- - `colors.toolbar_field_text`
- - `colors.toolbar_text`
-
-- [`theme`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/theme)
-
- - `windowId` option to [`theme.update()`](/pt-BR/Add-ons/WebExtensions/API/theme/update)
-
-- [`webRequest`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/webRequest)
-
- - [`filterResponseData()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/filterResponseData)
- - `proxyInfo` property in [`webRequest`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/webRequest) events
-
-- [`windows`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/windows)
-
- - `allowScriptsToClose` option in [`windows.create()`](/pt-BR/docs/Mozilla/Add-ons/WebExtensions/API/windows/create)
-
-## Versões anteriores
-
-{{Firefox_for_developers(56)}}
diff --git a/files/pt-br/web/api/document/getelementsbytagname/index.md b/files/pt-br/web/api/document/getelementsbytagname/index.md
deleted file mode 100644
index 253c57a06c63fc..00000000000000
--- a/files/pt-br/web/api/document/getelementsbytagname/index.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: Document.getElementsByTagName()
-slug: Web/API/Document/getElementsByTagName
----
-
-{{APIRef("DOM")}}
-
-O método getElementsByTagName da interface Document retorna um HTMLCollection de elementos com o nome da tag fornecido. O documento completo é pesquisado, incluindo o nó raiz. A HTMLCollection retornada é ao vivo, o que significa que ela se atualiza automaticamente para permanecer em sincronia com a árvore DOM sem ter que chamar document.getElementsByTagName () novamente.
-
-`O método getElementsByTagName` da {{domxref("Document")}} interface returns an {{domxref("HTMLCollection")}} of elements with the given tag name. The complete document is searched, including the root node. The returned `HTMLCollection` is live, meaning that it updates itself automatically to stay in sync with the DOM tree without having to call `document.getElementsByTagName()` again.
-
-## Syntax
-
-```
-var elements = document.getElementsByTagName(name);
-```
-
-- _elements_ is a live {{domxref("HTMLCollection")}} (but see the note below) of found elements in the order they appear in the tree.
-- _name_ is a string representing the name of the elements. The special string "\*" represents all elements.
-
-> **Nota:** [The latest W3C specification](https://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html) says _elements_ is an `HTMLCollection`; however, this method returns a {{domxref("NodeList")}} in WebKit browsers. See {{bug(14869)}} for details.
-
-## Example
-
-In the following example, `getElementsByTagName()` starts from a particular parent element and searches top-down recursively through the DOM from that parent element, building a collection of all descendant elements which match the tag `name` parameter. This demonstrates both `document.getElementsByTagName()` and the functionally identical {{domxref("Element.getElementsByTagName()")}}, which starts the search at a specific element within the DOM tree.
-
-Clicking the buttons uses `getElementsByTagName()` to count the descendant paragraph elements of a particular parent (either the document itself or one of two nested {{HTMLElement("div")}} elements).
-
-```html
-<!DOCTYPE html>
-<html lang="en">
-<head>
- <meta charset="UTF-8" />
- <title>getElementsByTagName example
-
-
-
- Some outer text
- Some outer text
-
-
-
Some div1 text
-
Some div1 text
-
Some div1 text
-
-
-
Some div2 text
-
Some div2 text
-
-
Some outer text
- Some outer text
-
-
- show all p elements in document
- show all p elements in div1 element
- show all p elements in div2 element
-
-
-