Skip to content

Commit 79b32d8

Browse files
Merge pull request #1888 from mattleff/patch-2
docs: Fix typo
2 parents b32cbfd + 9935029 commit 79b32d8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/fundamentals/lifecycle-events.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ In the following table, `onModuleDestroy`, `beforeApplicationShutdown` and `onAp
2020
| `onApplicationBootstrap()` | Called once all modules have been initialized, but before listening for connections. |
2121
| `onModuleDestroy()`\* | Called after a termination signal (e.g., `SIGTERM`) has been received. |
2222
| `beforeApplicationShutdown()`\* | Called after all `onModuleDestroy()` handlers have completed (Promises resolved or rejected);<br />once complete (Promises resolved or rejected), all existing connections will be closed (`app.close()` called). |
23-
| `onApplicationShutdown()`\* | Called after connections close (`app.close()` resolves. |
23+
| `onApplicationShutdown()`\* | Called after connections close (`app.close()` resolves). |
2424

2525
\* For these events, if you're not calling `app.close()` explicitly, you must opt-in to make them work with system signals such as `SIGTERM`. See [Application shutdown](fundamentals/lifecycle-events#application-shutdown) below.
2626

0 commit comments

Comments
 (0)