avoid implications of shaming in rule categories

Author: chrisvfritz

src/v2/style-guide/index.md

@@ -22,9 +22,7 @@ These rules help prevent errors, so learn and abide by them at all costs. Except
 
 ### Priority B: Strongly Recommended
 
-These rules have been found to vastly improve readability in most projects. If you violate them, your code will still run, but other developers may give you the evil eye [at conferences](https://github.com/vuejs/roadmap#events).
-
-[![Fry from Futurama glaring](https://i.imgur.com/PcOnLxn.jpg)](http://futurama.wikia.com/wiki/Template:FOX_Image)
+These rules have been found to improve readability and/or developer experience in most projects. Your code will still run if you violate them, but violations should be rare and well-justified.
 
 ### Priority C: Recommended
 
@@ -38,8 +36,6 @@ Where multiple, equally good options exist, an arbitrary choice can be made to e
 
 Some features of Vue exist to accommodate rare edge cases or smoother migrations from a legacy code base. When overused however, they can make your code more difficult to maintain or even become a source of bugs. These rules shine a light on potentially risky features, describing when and why they should be avoided.
 
-[![goto from xkcd.com](https://imgs.xkcd.com/comics/goto.png)](https://xkcd.com/292/)
-
 
 
 ## Priority A Rules: Essential (Error Prevention)