diff --git a/website/docs/foundations/custom-facets.mdx b/website/docs/foundations/custom-facets.mdx
index 6cb8a25e..578d8509 100644
--- a/website/docs/foundations/custom-facets.mdx
+++ b/website/docs/foundations/custom-facets.mdx
@@ -34,7 +34,7 @@ contract GameNFTFacet {
 }
 ```
 :::tip[Key Insight]
-Your custom `GameNFTFacet` and the standard `ERC721Facet` both operate on the **same storage** within your diamond. This shared-storage architecture is what makes Compose composable.
+Your custom `GameNFTFacet` and the standard `ERC721Facet` both operate on the **same storage** within your diamond. This shared-storage architecture is what makes composition possible.
 :::
 
 
diff --git a/website/docs/foundations/resuable-smart-contracts.mdx b/website/docs/foundations/resuable-smart-contracts.mdx
index 0cd8e561..d5b5390f 100644
--- a/website/docs/foundations/resuable-smart-contracts.mdx
+++ b/website/docs/foundations/resuable-smart-contracts.mdx
@@ -16,7 +16,7 @@ A diamond contract is a simple, tiny contract that **uses the code of other onch
 
 Below is a diagram showing a diamond connected to multiple facets that provide its functionality.
 
-<DiamondFacetsSVG style={{ width: '800', height: 'auto' }} />
+<DiamondFacetsSVG style={{ maxWidth: '100%', height: 'auto' }} />
 
 When you use Compose, you *do* deploy new contracts—but only the small diamond contract that ties together existing onchain facets.