10 Common HTML Mistakes we Should Avoid in 2020
                      10 Common HTML 
Mistakes we Should 
Avoid in 2020
1. Assumptions on versions
 Just because the work is similar, most of the beginners think assume 
that all the HTML versions are same. This is a big mistake by the 
beginners.
 The document type declaration differs from versions to version.
2. Don’t place Block elements within Inline elements
 A HTML component is shown as Block or as Inline as a matter of 
course. Square components, for example, divs and sections, make up 
the structure of the report. 
 Inline components live in these blocks, for example, grapple and 
length labels. So you should never put blocks inside inline 
components.
3. Don’t use line breaks to show a list
Wrong Way:
1. India
2. Pakistan/>
3. China
Correct way:

India
Pakistan
China 
4. Don’t use  and  for bolding and italicizing
 Instead of bold use 
 And 
  instead of italic.
5. Multiple line breaks
 The line break tag of  should just be utilized to embed is single line 
breaks in the progression of section content to thump an especially word 
down onto another line. 
 It shouldn't be utilized to make holes between components, rather, split 
the content into discrete passages, or modify the edge styled by CSS.
6. Avoid Inline Styles
 The major reason of semantic HTML and CSS is to separate document 
structure and styling, so it just doesn’t make sense to place styling directly 
in the HTML document.
7.  or 
 It’s recommended not to use  or .
 These tags have never been included in the official HTML standard 
of W3C consortium.
 Hence, ugly and unimpressive to use.
8. Avoid using deprecated elements
 There are some old HTML labels and properties which have been 
pronounced deplored by the W3C consortium. 
 Albeit present-day programs as of now bolster them, they may not 
in the future.
9. Don't rely on text editors
 You have to do is compose your code and spare it with the right 
expansion. 
 Some content tools like Notepad++ accompany punctuation 
featuring and can encourage the experience of composing a page, 
however with regards to the improvement, any of the alternatives 
will do similarly well on the off chance that you are not dependent 
on the fancy odds and ends of a specific one.
10. Don't do away with every attribute/value 
pair
 The repetitive ones can be skipped and a customary 
update is had to know which ones have fallen in that 
class, one such model would be the language 
property in the  tag, which has been 
supplanted by the sort characteristic.