From d73a95b4fd0549b0e56e2794020c4165931e2b6a Mon Sep 17 00:00:00 2001 From: Mario Romano Date: Thu, 22 Sep 2016 12:12:47 +0100 Subject: [PATCH] Update README.md --- ng2-components/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ng2-components/README.md b/ng2-components/README.md index 63d49c2e4a..b31c28df84 100644 --- a/ng2-components/README.md +++ b/ng2-components/README.md @@ -55,7 +55,7 @@ You can browse all the components at the following address: http://devproducts.alfresco.com/ -### How to test a change to a generic component in its own demo +## How to test a change to a generic component in its own demo Let's suppose that for some reason you have changed a component and you want to test this changes. The example is based on the ng2-alfresco-login component, but you can use the same steps for any component. @@ -88,4 +88,4 @@ npm link ng2-alfresco-login ```sh npm run start -``` \ No newline at end of file +```