Grammar consistency fix. (#24228)

Entire article is using "isn't" so the "wasn't" seems out of place. I'm just following https://english.stackexchange.com/questions/283758/proper-use-of-was-vs-is
This commit is contained in:
Ismael Casimpan
2018-12-05 00:12:48 +08:00
committed by nik
parent 355878e921
commit cffe1be295

View File

@ -9,7 +9,7 @@ videoUrl: 'https://scrimba.com/c/cpVKBfQ'
<section id='description'> <section id='description'>
There are several default fonts that are available in all browsers. These generic font families include <code>monospace</code>, <code>serif</code> and <code>sans-serif</code> There are several default fonts that are available in all browsers. These generic font families include <code>monospace</code>, <code>serif</code> and <code>sans-serif</code>
When one font isn't available, you can tell the browser to "degrade" to another font. When one font isn't available, you can tell the browser to "degrade" to another font.
For example, if you wanted an element to use the <code>Helvetica</code> font, but degrade to the <code>sans-serif</code> font when <code>Helvetica</code> wasn't available, you will specify it as follows: For example, if you wanted an element to use the <code>Helvetica</code> font, but degrade to the <code>sans-serif</code> font when <code>Helvetica</code> isn't available, you will specify it as follows:
<blockquote>p {<br>&nbsp;&nbsp;font-family: Helvetica, sans-serif;<br>}</blockquote> <blockquote>p {<br>&nbsp;&nbsp;font-family: Helvetica, sans-serif;<br>}</blockquote>
Generic font family names are not case-sensitive. Also, they do not need quotes because they are CSS keywords. Generic font family names are not case-sensitive. Also, they do not need quotes because they are CSS keywords.
</section> </section>