diff --git a/spec/SPECIFICATION.md b/spec/SPECIFICATION.md
index 6ee3f2e9f3fe0dbcbe63a463df748f79dcfa9da3..9659080b0e3f806ec799cdbb31e79ae0eb4bbcde 100644
--- a/spec/SPECIFICATION.md
+++ b/spec/SPECIFICATION.md
@@ -14,13 +14,13 @@ This document specifies the visual design of Shields badges.
 
 #### Bad
 
-![bad example](https://img.shields.io/badge/MySuperSaaSisSoAwesome.com-1.1.1-orange.svg)
+![Bad example, with the text "MySuperSaaSisSoAwesome.com" on the left side](https://img.shields.io/badge/MySuperSaaSisSoAwesome.com-1.1.1-orange.svg)
 
 The key is shamelessly promoting the service provider instead of giving context to the value. If service providers want to promote themselves, they can simply encourage people to link back to them and let folks who are curious click on the button for more information.
 
 #### Good
 
-![good example](https://img.shields.io/badge/version-1.1.1-green.svg)
+![Good example, with the text "version" on the left side](https://img.shields.io/badge/version-1.1.1-green.svg)
 
 The key clearly explains what the value stands for (the version of the software provided). The platform or service hosting the version of the software is only relevant to people who decide to click on an eventual link added to the badge itself but the value stands on its own with the metadata value it provides to viewers.