Fix image link

src/content/shared-logging-context.md

@@ -60,7 +60,7 @@ The first two points — structured events and static log messages — are intui
 A shared logging context enables a different approach to logging. Instead of emitting additional log events every time useful information is encountered, we can choose to simply update the log context. The common logging that occurs after every web request is completed will include the context that was attached while handling the request.
 
 The following screenshot shows an example Newrelic log search based on shared logging context. In this example query we are searching for all log events relating to customer API requests for a specific customer.
-![Example Newrelic log search, filtering by ](/public/img/newrelic-log-search-example.webp)
+![Example Newrelic log search, filtering by ](/img/newrelic-log-search-example.webp)
 
 Decoupling log event emitters from their surrounding context also improves the separation of concerns in our modules. Emitting a contextualized log event no longer requires the caller's context to be explicitly provided.