fix typo in custom-directives.md (#1148)

lit · Jul 12, 2023 · ef0e128 · ef0e128
1 parent f2271c7
commit ef0e128
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/packages/lit-dev-content/site/docs/v2/templates/custom-directives.md b/packages/lit-dev-content/site/docs/v2/templates/custom-directives.md
@@ -404,7 +404,7 @@ export const resolvePromise = directive(ResolvePromise);
 
 {% endswitchable-sample %}
 
-Here, the rendered template shows "Waiting for promise to resolve," followed by the resolved value of the promise, whenever it resolves.
+Here, the rendered template shows "Waiting for promise to resolve", followed by the resolved value of the promise, whenever it resolves.
 
 Async directives often need to subscribe to external resources. To prevent memory leaks async directives should unsubscribe or dispose of resources when the directive instance is no longer in use.  For this purpose, `AsyncDirective` provides the following extra lifecycle callbacks and API:
 

diff --git a/packages/lit-dev-content/site/docs/v3/templates/custom-directives.md b/packages/lit-dev-content/site/docs/v3/templates/custom-directives.md
@@ -404,7 +404,7 @@ export const resolvePromise = directive(ResolvePromise);
 
 {% endswitchable-sample %}
 
-Here, the rendered template shows "Waiting for promise to resolve," followed by the resolved value of the promise, whenever it resolves.
+Here, the rendered template shows "Waiting for promise to resolve", followed by the resolved value of the promise, whenever it resolves.
 
 Async directives often need to subscribe to external resources. To prevent memory leaks async directives should unsubscribe or dispose of resources when the directive instance is no longer in use.  For this purpose, `AsyncDirective` provides the following extra lifecycle callbacks and API: