Skip to content

small doc changes #200

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maxnorm merged 1 commit into from
Nov 13, 2025
Merged

small doc changes #200

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/docs/foundations/custom-facets.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::


Expand Down
2 changes: 1 addition & 1 deletion website/docs/foundations/resuable-smart-contracts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down