diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index 88c4a8f7c4c..37876749657 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -83,10 +83,10 @@ There are several ways to localize components' string resources:
     1.2. Localize all resources for a component type - each component which supports localization has input property `resourceStrings`. To localize all instances of a given component in the application the following steps should be performed - get the value of the input property `resourceStrings` of the component to be localized; do not create a new instance but replace the existing strings within the object. By default all components of a given type in an application share one instance of the resource strings. Replacing a value in that instance affects all components of that type in the application.
     1.3. Localize all resources for all components - use global method `getCurrentResourceStrings` to get an object containing current resource strings for all components. To provide localized resources just pass an object of type `IResourceStrings` to the global method `changei18n`.
 
-2. Using NuGet package:
+2. Using npm package:
 We've created new repository which will hold the resource strings for languages different than English:
 https://github.com/IgniteUI/igniteui-angular-i18n
-A NuGet package should be published each time we release new version of IgniteUI for Angular. Its version should correspond to the version of the igniteui-angular NuGet package.
+A npm package should be published each time we release new version of IgniteUI for Angular. Its version should correspond to the version of the igniteui-angular npm package.
 One could localize an application by importing the corresponding localized resource strings from the localization package (`igniteui-angular-i18n`) and use the methods described in the previous bullet to localize the whole application or part of it.
 Example:
 Inside app.module you can perform: