diff --git a/docs/catalog/cloud/use-circuit-breaker.md b/docs/catalog/cloud/use-circuit-breaker.md
index 21000b61..b11c9295 100644
--- a/docs/catalog/cloud/use-circuit-breaker.md
+++ b/docs/catalog/cloud/use-circuit-breaker.md
@@ -18,7 +18,7 @@ If the other application is not reachable, all network requests against this oth
 
 ## Solution
 
-Circuit breaker patterns reject the request to the other application if health checks against the other application have failed to complete successfully. In this case a lot of network requests can be saved. 
+Circuit breaker patterns reject the request to the other application if health checks against the other application have failed to complete successfully. In this case a lot of network requests, and energy, can be saved.
 The circuit breaker will reset itself automatically, if health checks against the other application are successful again.
 
 ## SCI Impact
@@ -37,7 +37,9 @@ The circuit breaker pattern reduces the following aspect:
 ## Considerations
 
 - Consider implementing an back-off strategy to automatically re-enable the requests if the resource becomes available again
+- Consider handling different errors of the called application differently. For example exceptions that indicate that the called application will not be available for a longer time should be handled differently than exceptions that indicate only a short time in-availability.
 
 ## References
 
 - [Azure Well-Architected Framework Sustainability Pillar](https://learn.microsoft.com/en-us/azure/architecture/framework/sustainability/sustainability-application-design)
+- [Azure Circuit Breaker Pattern Description](https://learn.microsoft.com/en-us/azure/architecture/patterns/circuit-breaker)