From 200ddce88fa27d4e6aaa6f53bcfdc29e99d7c791 Mon Sep 17 00:00:00 2001 From: Sabareesh Kappagantu Date: Sun, 4 Sep 2022 23:33:31 -0600 Subject: [PATCH] docs: update angular-package-format guide (#47342) PR Close #47342 --- aio/content/guide/angular-package-format.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aio/content/guide/angular-package-format.md b/aio/content/guide/angular-package-format.md index 32e4ad05823..ef9efadd45c 100644 --- a/aio/content/guide/angular-package-format.md +++ b/aio/content/guide/angular-package-format.md @@ -267,7 +267,7 @@ Not all libraries require such granularity. Most libraries with a single logical purpose should be published as a single entrypoint. `@angular/core` for example uses a single entrypoint for the runtime, because the Angular runtime is generally used as a single entity. -### Resolution of secondary entrypoints +### Resolution of secondary entry points Secondary entrypoints can be resolved via the `"exports"` field of the `package.json` for the package.