diff --git a/aio/content/guide/creating-libraries.md b/aio/content/guide/creating-libraries.md
index a86919439f..4a933a6193 100644
--- a/aio/content/guide/creating-libraries.md
+++ b/aio/content/guide/creating-libraries.md
@@ -19,7 +19,7 @@ Use the Angular CLI to generate a new library skeleton with the following comman
 </code-example>
 
 <div class="alert is-helpful">
-     <p>You can use the monorepo model to use the same workspace for multiple projects. See [Setting up for a multi-project workspace](guide/file-structure#multiple-projects).</p>
+     <p>You can use the monorepo model to use the same workspace for multiple projects. See <a href="guide/file-structure#multiple-projects">Setting up for a multi-project workspace</a>.</p>
 </div>
 
 This creates the `projects/my-lib` folder in your workspace, which contains a component and a service inside an NgModule.
@@ -213,4 +213,4 @@ This means that the TypeScript source can result in different JavaScript code in
 For this reason, an app that depends on a library should only use TypeScript path mappings that point to the *built library*.
 TypeScript path mappings should *not* point to the library source `.ts` files.
 
-</div>
\ No newline at end of file
+</div>