diff --git a/src/documents/abbreviations/syntax/index.html.md b/src/documents/abbreviations/syntax/index.html.md
index ae410ac..a2486ba 100644
--- a/src/documents/abbreviations/syntax/index.html.md
+++ b/src/documents/abbreviations/syntax/index.html.md
@@ -67,7 +67,7 @@ With `^` operator, you can climb one level up the tree and change context where
 	
 You can use as many `^` operators as you like, each operator will move one level up:
 
-	div+div>p>span+em^^^bq
+	div+div>p>span+em^^bq
 	
 ...will output to
 
@@ -317,4 +317,4 @@ run: emmet.expand_abbreviation
 This is why Emmet needs some indicators (like spaces) where it should stop parsing to not expand anything that you don’t need. If you’re still thinking that such formatting is required for complex abbreviations to make them more readable:
 
 * Abbreviations are not a template language, they don’t have to be “readable”, they have to be “quickly expandable and removable”.
-* You don’t really need to write complex abbreviations. Stop thinking that “typing” is the slowest process in web-development. You’ll quickly find out that constructing a single complex abbreviation is much slower and error-prone than constructing and typing a few short ones.
\ No newline at end of file
+* You don’t really need to write complex abbreviations. Stop thinking that “typing” is the slowest process in web-development. You’ll quickly find out that constructing a single complex abbreviation is much slower and error-prone than constructing and typing a few short ones.