diff --git a/docs/preview/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md b/docs/preview/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md
index d7e64b03..d4bc44b3 100644
--- a/docs/preview/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md	
+++ b/docs/preview/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md	
@@ -9,7 +9,7 @@ The concept of service-to-service correlation is big and complex and spans multi
 To use service-to-service correlation in Azure Service Bus solutions, both the sending and receiving side of the separate components have to be adapted. The correlation will be passed through from one service to another via the Azure Service Bus message application properties which Arcus will use to link your services together.
 
 The following diagram shows how a Web API calls a Service Bus with correlation tracking:
-![Messaging correlation diagram](/media/service-to-service-api-worker-diagram-example.png)
+![Messaging correlation diagram](/media/service-to-service-api-worker-w3c-diagram-example.png)
 
 ## How does this work?
 Three kind of correlation ID's are used to create the relationship:
diff --git a/docs/static/media/service-to-service-api-worker-w3c-diagram-example.png b/docs/static/media/service-to-service-api-worker-w3c-diagram-example.png
new file mode 100644
index 00000000..6ef3074d
Binary files /dev/null and b/docs/static/media/service-to-service-api-worker-w3c-diagram-example.png differ
diff --git a/docs/versioned_docs/version-v2.6.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md b/docs/versioned_docs/version-v2.6.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md
index 782cc007..839a5a51 100644
--- a/docs/versioned_docs/version-v2.6.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md	
+++ b/docs/versioned_docs/version-v2.6.0/02-Guidance/Service-to-service Correlation/use-service-to-service-correlation-in-service-bus.md	
@@ -9,7 +9,7 @@ The concept of service-to-service correlation is big and complex and spans multi
 To use service-to-service correlation in Azure Service Bus solutions, both the sending and receiving side of the separate components have to be adapted. The correlation will be passed through from one service to another via the Azure Service Bus message application properties which Arcus will use to link your services together.
 
 The following diagram shows how a Web API calls a Service Bus with correlation tracking:
-![Messaging correlation diagram](/media/service-to-service-api-worker-diagram-example.png)
+![Messaging correlation diagram](/media/service-to-service-api-worker-w3c-diagram-example.png)
 
 ## How does this work?
 Three kind of correlation ID's are used to create the relationship: