images

Author: marciw

docs/reference/images/elasticsearch-client-net-api-capture-requests-localhost.png

@@ -11,7 +11,7 @@ A web debugging proxy such as [Fiddler](http://www.telerik.com/fiddler) is a use
 
 To capture traffic against a remote cluster is as simple as launching Fiddler! You may want to also filter traffic to only show requests to the remote cluster by using the filters tab
 
-:::{image} /troubleshoot/images/elasticsearch-client-net-api-capture-requests-remotehost.png
+:::{image} ../images/elasticsearch-client-net-api-capture-requests-remotehost.png
 :alt: Capturing requests to a remote host
 :::
 
@@ -37,13 +37,13 @@ var client = new ElasticClient(connectionSettings);
 
 With Fiddler running, the requests and responses will now be captured and can be inspected in the Inspectors tab
 
-:::{image} /troubleshoot/images/elasticsearch-client-net-api-inspect-requests.png
+:::{image} ../images/elasticsearch-client-net-api-inspect-requests.png
 :alt: Inspecting requests and responses
 :::
 
 As before, you may also want to filter traffic to only show requests to `ipv4.fiddler` on the port on which you are running Elasticsearch.
 
-:::{image} /troubleshoot/images/elasticsearch-client-net-api-capture-requests-localhost.png
+:::{image} ../images/elasticsearch-client-net-api-capture-requests-localhost.png
 :alt: Capturing requests to localhost
 :::