angular
diff --git a/‎aio/content/guide/reusable-animations.md
Copy file name to clipboardExpand all lines: aio/content/guide/reusable-animations.md
+1-1Lines changed: 1 addition & 1 deletion b/‎aio/content/guide/reusable-animations.md
Copy file name to clipboardExpand all lines: aio/content/guide/reusable-animations.md
+1-1Lines changed: 1 addition & 1 deletion
diff --git a/‎packages/elements/src/create-custom-element.ts
Copy file name to clipboardExpand all lines: packages/elements/src/create-custom-element.ts
+2-2Lines changed: 2 additions & 2 deletions b/‎packages/elements/src/create-custom-element.ts
Copy file name to clipboardExpand all lines: packages/elements/src/create-custom-element.ts
+2-2Lines changed: 2 additions & 2 deletions
@@ -11,7 +11,7 @@ Before continuing with this topic, you should be familiar with the following:
 
 ## Creating reusable animations
 
-To create a reusable animation, use the <code>[animation](api/animations/animation)()</code> function to define an animation in a separate `.ts` file and declare this animation definition as a `const` export variable. You can then import and reuse this animation in any of your application components using the <code>[useAnimation](api/animations/useAnimation)</a>()</code> function.
+To create a reusable animation, use the <code>[animation](api/animations/animation)()</code> function to define an animation in a separate `.ts` file and declare this animation definition as a `const` export variable. You can then import and reuse this animation in any of your application components using the <code>[useAnimation](api/animations/useAnimation)()</code> function.
 
 <code-example path="animations/src/app/animations.1.ts" header="src/app/animations.ts" region="animation-const" language="typescript"></code-example>
 
 
@@ -184,8 +184,8 @@ export function createCustomElement<P>(
     override connectedCallback(): void {
       // For historical reasons, some strategies may not have initialized the `events` property
       // until after `connect()` is run. Subscribe to `events` if it is available before running
-      // `connect()` (in order to capture events emitted suring inittialization), otherwise
-      // subscribe afterwards.
+      // `connect()` (in order to capture events emitted during initialization), otherwise subscribe
+      // afterwards.
       //
       // TODO: Consider deprecating/removing the post-connect subscription in a future major version
       //       (e.g. v11).