diff --git a/src/guide/extras/web-components.md b/src/guide/extras/web-components.md
index 5c3696f486..c5e3076730 100644
--- a/src/guide/extras/web-components.md
+++ b/src/guide/extras/web-components.md
@@ -307,8 +307,7 @@ declare module 'vue' {
 Here is the recommended way to enable type checking in SFC templates of Custom Elements that are not built with Vue.
 
 :::tip Note
-- This approach is one possible way to do it, but it may vary depending on the
-- framework being used to create the custom elements.
+This approach is one possible way to do it, but it may vary depending on the framework being used to create the custom elements.
 :::
 
 Suppose we have a custom element with some JS properties and events defined, and it is shipped in a library called `some-lib`:
@@ -391,10 +390,7 @@ type VueEmit<T extends EventMap> = EmitFn<{
 ```
 
 :::tip Note
-- We marked `$props` and `$emit` as deprecated so that when we get a `ref` to
-- a custom element we will not be tempted to use these properties, as these
-- properties are for type checking purposes only when it comes to custom elements.
-- These properties do not actually exist on the custom element instances.
+We marked `$props` and `$emit` as deprecated so that when we get a `ref` to a custom element we will not be tempted to use these properties, as these properties are for type checking purposes only when it comes to custom elements. These properties do not actually exist on the custom element instances.
 :::
 
 Using the type helper we can now select the JS properties that should be exposed for type checking in Vue templates: