From 9f0d6bd8ba2e95c23bf63ee46cb6847269dff874 Mon Sep 17 00:00:00 2001 From: Andy Date: Sat, 27 Oct 2018 10:32:53 -0700 Subject: [PATCH] fix: typo (#20879) Changed "attibute" to "attribute" --- guide/english/css/before-selector/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/english/css/before-selector/index.md b/guide/english/css/before-selector/index.md index 20038da21d..a5cbfd45b5 100644 --- a/guide/english/css/before-selector/index.md +++ b/guide/english/css/before-selector/index.md @@ -53,7 +53,7 @@ In the example above we are prepending a grey border before every paragraph elem This will show `Hello world!!` in the page. -Not only strings, also images, counters or even nothing ("", useful for clearfix) can be inserted into the `content` attibute, but not HTML. There are a good number of cool things that can be made using ```::before``` and ```after``` in a creative way. You can take a look in the next link if you are curious: A Whole Bunch of Amazing Stuff Pseudo Elements Can Do +Not only strings, also images, counters or even nothing ("", useful for clearfix) can be inserted into the `content` attribute, but not HTML. There are a good number of cool things that can be made using ```::before``` and ```after``` in a creative way. You can take a look in the next link if you are curious: A Whole Bunch of Amazing Stuff Pseudo Elements Can Do #### Single-colon vs. Double-colon There's a bit of discussion about the right way of using pseudo-elements: old style single-colon (```:before```), used in CSS specifications 1 and 2, versus CSS3 recomendation, double-colon (```::before```), mainly to "establish a discrimination between pseudo-classes and pseudo-elements". But for compatibility reasons, single-colon is still accepted. Talking about compatibility, IE8 supports the single-colon notation only.