From 79d87956335f53bbf21f335b20245d21bdf0f722 Mon Sep 17 00:00:00 2001 From: Aristeidis Bampakos Date: Sun, 6 Sep 2020 13:16:53 +0300 Subject: [PATCH] docs: fix typos in library guide (#38726) This PR fixes minor typos in the Creating libraries guide. PR Close #38726 --- aio/content/guide/creating-libraries.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aio/content/guide/creating-libraries.md b/aio/content/guide/creating-libraries.md index f35ac77583..3cb1598aff 100644 --- a/aio/content/guide/creating-libraries.md +++ b/aio/content/guide/creating-libraries.md @@ -26,7 +26,7 @@ The `ng generate` command creates the `projects/my-lib` folder in your workspace -When you generate a new library, the workspace configuration file, `angular.json`, is updated with a project of type 'library'. +When you generate a new library, the workspace configuration file, `angular.json`, is updated with a project of type `library`. "projects": { @@ -109,7 +109,7 @@ If you want a dropdown that would contain different passed-in values each time, Suppose you want to read a configuration file and then generate a form based on that configuration. If that form will need additional customization by the developer who is using your library, it might work best as a schematic. -However, if the forms will always be the same and not need much customization by developers, then you could create a dynamic component that takes the configuration and generates the form. +However, if the form will always be the same and not need much customization by developers, then you could create a dynamic component that takes the configuration and generates the form. In general, the more complex the customization, the more useful the schematic approach. To learn more, see [Schematics Overview](guide/schematics) and [Schematics for Libraries](guide/schematics-for-libraries).