Skip to content

Commit e1e3db8

Browse files
Update docs/modules/ROOT/pages/api/macros.adoc
Co-authored-by: Andrew Fleming <[email protected]>
1 parent c8e802d commit e1e3db8

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/modules/ROOT/pages/api/macros.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -18,12 +18,12 @@ openzeppelin_macros = "0.20.0"
1818

1919
This macro simplifies the syntax for adding a set of components to a contract. It:
2020

21-
- _Imports the corresponding components into the contract_
22-
- _Adds the corresponding `component!` macro entries_
23-
- _Adds the storage entries for each component to the Storage struct_
24-
- _Adds the event entries for each component to the Event struct, or creates the struct if it is missing_
25-
- _Brings the corresponding internal implementations into scope_
26-
- _Provides some diagnostics for each specific component to help the developer avoid common mistakes_
21+
- _Imports the corresponding components into the contract._
22+
- _Adds the corresponding `component!` macro entries._
23+
- _Adds the storage entries for each component to the Storage struct._
24+
- _Adds the event entries for each component to the Event struct, or creates the struct if it is missing._
25+
- _Brings the corresponding internal implementations into scope._
26+
- _Provides some diagnostics for each specific component to help the developer avoid common mistakes._
2727

2828
CAUTION: Since the macro does not expose any external implementations, developers must make sure to specify explicitly
2929
the ones required by the contract.

0 commit comments

Comments
 (0)