diff --git a/blog/2022-02-18-paper-elements.md b/blog/2022-02-18-paper-elements.md
index ce61bae3..b73dbdfb 100644
--- a/blog/2022-02-18-paper-elements.md
+++ b/blog/2022-02-18-paper-elements.md
@@ -14,5 +14,8 @@ We are converting our codebase from the deprecated `paper` elements to the new [
 
 ## What should custom cards do?
  
-Custom Card Creators should bundle the components they rely on. This way they can control the version that is being used. The MWC components support registering their elements with custom names so they don't conflict with the Home Assistant frontend: [example from ESP Web Tools](https://github.com/esphome/esp-web-tools/blob/main/src/components/ewt-checkbox.ts)
+You can replace your `paper` elements with `mwc` elements but there is no gaurentee that these elements will be loaded when your users load your editor or cards, like it also was not guaranteed for `paper` elements. We can also not guarentee that we will use these elements forever, and an update of these elements could include breaking changes. We can not support this use case.
 
+Our advise is to bundle your own elements, that don't collide with the elements Home Assistant uses.
+
+See [this old blog post](https://developers.home-assistant.io/blog/2020/10/02/lazyMoreInfo#what-about-external-elements) for more information.