diff --git a/CHANGELOG.md b/CHANGELOG.md
index 250b49462..b4acb3713 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,7 @@
 
 - Fixed issue when target tarball is part of tarball content in `pilet pack` (#642)
 - Moved `piral-jest-utils` and `piral-ie11polyfills-utils` into a separate repository
+- Updated documentation on `piral-ng` (#646)
 - Updated dependencies (#641)
 - Updated generated code to fully use ES2020
 - Added `piral-react` as converter for React
diff --git a/src/converters/piral-ng/README.md b/src/converters/piral-ng/README.md
index 44f8b77e6..ed0b57290 100644
--- a/src/converters/piral-ng/README.md
+++ b/src/converters/piral-ng/README.md
@@ -41,13 +41,13 @@ export function setup(piral: PiletApi) {
 }
 ```
 
-We recommend that you still put these components into modules as you would normally do. In order for Piral to use that module you need to define it first. This also allows you to use special Piral declarations such as the `NgExtension` or the `ResourceUrlPipe`. All these declarations come with the `SharedModule` available via import from `piral-ng/common`.
+We recommend that you still put these components into modules as you would normally do. In order for Piral to use that module you need to define it first. This also allows you to use special Piral declarations such as the `NgExtension` or the `ResourceUrlPipe`. All these declarations come with the `SharedModule` available via import from `piral-ng-common`.
 
 Example (app) module:
 
 ```ts
 import { NgModule } from '@angular/core';
-import { SharedModule } from 'piral-ng/common';
+import { SharedModule } from 'piral-ng-common';
 import { AngularPage } from './AngularPage';
 
 @NgModule({
@@ -347,7 +347,7 @@ The related packages should be shared with the pilets via the *package.json*:
       "@angular/core": "",
       "@angular/platform-browser": "",
       "@angular/platform-browser-dynamic": "",
-      "piral-ng/common": "",
+      "piral-ng-common": "",
       "rxjs": "",
       "zone.js": ""
     }