fix(docs): updated example image (fixes #111) (#270)

Author: TrapinchO

README.md

@@ -13,18 +13,20 @@ can print out like this (or in any format you like!):
 
 <img src="https://raw.githubusercontent.com/zkat/miette/main/images/serde_json.png" alt="Hi! miette also includes a screen-reader-oriented diagnostic printer that's enabled in various situations, such as when you use NO_COLOR or CLICOLOR settings, or on CI. This behavior is also fully configurable and customizable. For example, this is what this particular diagnostic will look like when the narrated printer is enabled:
 \
-Error: Received some bad JSON from the source. Unable to parse.
-    Caused by: missing field `foo` at line 1 column 1700
+diagnostic error code: oops::my::bad (link)
+Error: oops!
 \
-Begin snippet for https://api.nuget.org/v3/registration5-gz-semver2/json.net/index.json starting
-at line 1, column 1659
+Begin snippet for bad_file.rs starting
+at line 2, column 3
 \
-snippet line 1: gs&quot;:[&quot;json&quot;],&quot;title&quot;:&quot;&quot;,&quot;version&quot;:&quot;1.0.0&quot;},&quot;packageContent&quot;:&quot;https://api.nuget.o
-    highlight starting at line 1, column 1699: last parsing location
+snippet line 1: source
 \
-diagnostic help: This is a bug. It might be in ruget, or it might be in the
-source you're using, but it's definitely a bug and should be reported.
-diagnostic error code: ruget::api::bad_json
+snippet line 2:  text
+    highlight starting at line 1, column 3: This bit here
+\
+snippet line 3: here
+\
+diagnostic help: try doing it better next time?
 " />
 
 > **NOTE: You must enable the `"fancy"` crate feature to get fancy report