Skip to content

Commit 83bd0e2

Browse files
authored
docs: removed unnecessary visible <br/> tag in fields/blocks (#10456)
There was a `<br/>` tag, which was visible on the docs page. Also, I removed spacing from the second tip box, to keep in consistent with tips in other places in docs.
1 parent 4c96028 commit 83bd0e2

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

docs/fields/blocks.mdx

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ This is super handy if you'd like to present your editors with a very deliberate
9696
For example, if you have a `gallery` block, you might want to actually render the gallery of images directly in your Lexical block. With the `admin.components.Block` property, you can do exactly that!
9797

9898
<Banner type="success">
99-
**Tip:**<br/>
99+
**Tip:**
100100
If you customize the way your block is rendered in Lexical, you can import utility components to easily edit / remove your block - so that you don't have to build all of this yourself.
101101
</Banner>
102102

@@ -135,7 +135,6 @@ Blocks are defined as separate configs of their own.
135135

136136
<Banner type="success">
137137
**Tip:**
138-
139138
Best practice is to define each block config in its own file, and then import them into your
140139
Blocks field as necessary. This way each block config can be easily shared between fields. For
141140
instance, using the "layout builder" example, you might want to feature a few of the same blocks

0 commit comments

Comments
 (0)