[RU] Remove `name` attribute from headings (#2788)

1 files changed, 12 insertions, 12 deletions

diff --git a/files/ru/learn/css/howto/css_faq/index.html b/files/ru/learn/css/howto/css_faq/index.html
index c4ab7459a5..f68e864cfc 100644
--- a/files/ru/learn/css/howto/css_faq/index.html
+++ b/files/ru/learn/css/howto/css_faq/index.html
@@ -35,11 +35,11 @@ original_slug: Web/CSS/Common_CSS_Questions
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 </pre>
 
-<h2 id="My_CSS_is_valid.2C_but_not_correctly_rendered" name="My_CSS_is_valid.2C_but_not_correctly_rendered">Why doesn't my CSS, which is valid, render at all?</h2>
+<h2 id="My_CSS_is_valid.2C_but_not_correctly_rendered">Why doesn't my CSS, which is valid, render at all?</h2>
 
 <p>To be applied, a CSS stylesheet must be served with a <code>text/css</code> MIME type. If the Web server doesn't serve it with this type, it won't be applied.</p>
 
-<h2 id="Difference_between_id_and_class" name="Difference_between_id_and_class">What is the difference between <code>id</code> and <code>class</code>?</h2>
+<h2 id="Difference_between_id_and_class">What is the difference between <code>id</code> and <code>class</code>?</h2>
 
 <p>HTML elements can have an id and/or class attribute. The id attribute assigns a name to the element it is applied to, and for valid markup, there can be only one element with that name. The class attribute assigns a class name to the element, and that name can be used on many elements within the page. CSS allows you to apply styles to particular id and/or class names.<br>
  <br>
@@ -51,17 +51,17 @@ original_slug: Web/CSS/Common_CSS_Questions
 
 <p>See <a href="/en-US/docs/CSS/Getting_Started/Selectors" title="CSS/Getting_Started/Selectors"> CSS selectors</a></p>
 
-<h2 id="Restoring_the_default_property_value" name="Restoring_the_default_property_value">How do I restore the default value of a property?</h2>
+<h2 id="Restoring_the_default_property_value">How do I restore the default value of a property?</h2>
 
 <p>Initially CSS didn't provide a "default" keyword and the only way to restore the default value of a property is to explicitly re-declare that property.</p>
 
 <p>This has changed with CSS 2; the keyword <a href="/es/CSS/initial" title="initial">initial</a> is now a valid value for a CSS property. It resets it to its default value, which is defined in the CSS specification of the given property.</p>
 
-<h2 id="Derived_styles" name="Derived_styles">How do I derive one style from another?</h2>
+<h2 id="Derived_styles">How do I derive one style from another?</h2>
 
 <p>CSS does not allow one style to be defined in terms of another. (See <a href="http://archivist.incutio.com/viewlist/css-discuss/2685">Eric Meyer's note about the Working Group's stance</a>). However, assigning multiple classes to a single element can provide the same effect.</p>
 
-<h2 id="Assigning_multiple_classes" name="Assigning_multiple_classes">How do I assign multiple classes to an element?</h2>
+<h2 id="Assigning_multiple_classes">How do I assign multiple classes to an element?</h2>
 
 <p>HTML elements can be assigned multiple classes by listing the classes in the <code>class</code> attribute, with a blank space to separate them.</p>
 
@@ -77,11 +77,11 @@ original_slug: Web/CSS/Common_CSS_Questions
 
 <p>If the same property is declared in both rules, the conflict is resolved first through specificity, then according to the order of the CSS declarations. The order of classes in the <code>class</code> attribute is not relevant.</p>
 
-<h2 id="Style_rules_that_don.27t_work" name="Style_rules_that_don.27t_work">Why don't my style rules work properly?</h2>
+<h2 id="Style_rules_that_don.27t_work">Why don't my style rules work properly?</h2>
 
 <p>Style rules that are syntactically correct may not apply in certain situations. You can use <a href="/en-US/docs/DOM_Inspector" title="DOM_Inspector">DOM Inspector</a>'s <em>CSS Style Rules</em> view to debug problems of this kind, but the most frequent instances of ignored style rules are listed below.</p>
 
-<h3 id="HTML_elements_hierarchy" name="HTML_elements_hierarchy">HTML elements hierarchy</h3>
+<h3 id="HTML_elements_hierarchy">HTML elements hierarchy</h3>
 
 <p>The way CSS styles are applied to HTML elements depends also on the elements hierarchy. It is important to remember that a rule applied to a descendent overrides the style of the parent, in spite of any specificity or priority of CSS rules.</p>
 
@@ -96,7 +96,7 @@ original_slug: Web/CSS/Common_CSS_Questions
 
 <p>In case of complex HTML hierarchies, if a rule seems to be ignored, check if the element is inside another element with a different style.</p>
 
-<h3 id="Explicitly_re-defined_style_rule" name="Explicitly_re-defined_style_rule">Explicitly re-defined style rule</h3>
+<h3 id="Explicitly_re-defined_style_rule">Explicitly re-defined style rule</h3>
 
 <p>In CSS stylesheets, order <strong>is</strong> important. If you define a rule and then you re-define the same rule, the last definition is used.</p>
 
@@ -115,7 +115,7 @@ original_slug: Web/CSS/Common_CSS_Questions
 
 <p>To avoid this kind of error, try to define rules only once for a certain selector, and group all rules belonging to that selector.</p>
 
-<h3 id="Use_of_a_shorthand_property" name="Use_of_a_shorthand_property">Use of a shorthand property</h3>
+<h3 id="Use_of_a_shorthand_property">Use of a shorthand property</h3>
 
 <p>Using shorthand properties for defining style rules is good because it uses a very compact syntax. Using shorthand with only some attributes is possible and correct, but it must be remembered that undeclared attributes are automatically reset to default. This means that a previous rule for a single attribute could be implicitly overridden.</p>
 
@@ -135,7 +135,7 @@ original_slug: Web/CSS/Common_CSS_Questions
 }
 </pre>
 
-<h3 id="Use_of_the_.2A_selector" name="Use_of_the_.2A_selector">Use of the <code>*</code> selector</h3>
+<h3 id="Use_of_the_.2A_selector">Use of the <code>*</code> selector</h3>
 
 <p>The <code>*</code> wildcard selector refers to any element, and it has to be used with particular care.</p>
 
@@ -153,7 +153,7 @@ original_slug: Web/CSS/Common_CSS_Questions
 
 <p>The use of the * selector should be minimized as it is a slow selector, especially when not used as the first element of a selector. Its use should be avoided as much as possible.</p>
 
-<h3 id="Specificity_in_CSS" name="Specificity_in_CSS">Specificity in CSS</h3>
+<h3 id="Specificity_in_CSS">Specificity in CSS</h3>
 
 <p>When multiples rules apply to a certain element, the rule chosen depends on its style <a href="/en-US/docs/CSS/Specificity" title="Specificity">specificity</a>. Inline style (in HTML <code>style</code> attributes) comes first, followed by ID selectors, then class selectors and eventually element-name selectors.</p>
 
@@ -166,7 +166,7 @@ original_slug: Web/CSS/Common_CSS_Questions
 
 <p>The rules are more complicated when the selector has multiple parts. More detailed information about how selector specificity is calculated can be found in the <a href="http://www.w3.org/TR/CSS21/cascade.html#specificity">CSS 2.1 Specification chapter 6.4.3</a>.</p>
 
-<h2 id="What_do_the_-moz-.2A_properties_do.3F" name="What_do_the_-moz-.2A_properties_do.3F">What do the -moz-*, -ms-*, -webkit-*, -o-* and -khtml-* properties do?</h2>
+<h2 id="What_do_the_-moz-.2A_properties_do.3F">What do the -moz-*, -ms-*, -webkit-*, -o-* and -khtml-* properties do?</h2>
 
 <p>These properties, called <em>prefixed properties</em>, are extensions to the CSS standard. They are used to use experimental and non-standard features without polluting the regular namespace, preventing future incompatibilities to arise when the standard is extended.</p>