Avoid using URLs, due to issue #1

README.md

@@ -25,10 +25,10 @@ those badges, just set the appropriate flags in the config file:
 
 
 ```
-# Shows a godoc badge for your package (<a href="https://godoc.org">https://godoc.org</a>)
+# Shows a godoc badge for your package
 showGodocBadge = true
 
-# Shows a Go report card for your package (<a href="https://goreportcard.com">https://goreportcard.com</a>)
+# Shows a Go report card for your package
 showGoReportBadge = false
 ```
 
@@ -37,8 +37,8 @@ For others, specify the markdown in the config file:
 
 ```
 customMarkdownBadges = [
-  "[![Coverage Status](<a href="https://link/to/badge.svg">https://link/to/badge.svg</a>)](<a href="https://link/to/data">https://link/to/data</a>)",
-  "[![Build Status](<a href="https://link/to/badge.svg">https://link/to/badge.svg</a>)](<a href="https://link/to/data">https://link/to/data</a>)",
+  "[![Coverage Status](...)](...)",
+  "[![Build Status](...)](...)",
 ]
 ```
 

docs.go

@@ -33,17 +33,17 @@ in your package directory.
 Some badges are supported directly by the tool (PRs welcome for others). For
 those badges, just set the appropriate flags in the config file:
 
-  # Shows a godoc badge for your package (https://godoc.org)
+  # Shows a godoc badge for your package
   showGodocBadge = true
 
-  # Shows a Go report card for your package (https://goreportcard.com)
+  # Shows a Go report card for your package
   showGoReportBadge = false
 
 For others, specify the markdown in the config file:
 
   customMarkdownBadges = [
-    "[![Coverage Status](https://link/to/badge.svg)](https://link/to/data)",
-    "[![Build Status](https://link/to/badge.svg)](https://link/to/data)",
+    "[![Coverage Status](...)](...)",
+    "[![Build Status](...)](...)",
   ]
 
 Additional markdown can be specified, which will be appended to the output from