diff --git a/guide/english/certifications/apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning/index.md b/guide/english/certifications/apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning/index.md
index 8d46a6ca3f..7d3e4e5fe7 100644
--- a/guide/english/certifications/apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning/index.md
+++ b/guide/english/certifications/apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning/index.md
@@ -3,8 +3,14 @@ title: Manage npm Dependencies By Understanding Semantic Versioning
---
## Manage npm Dependencies By Understanding Semantic Versioning
-This is a stub. Help our community expand it.
-
-This quick style guide will help ensure your pull request gets accepted.
-
+You should go over to the `package.json` file in your project. SemVer dependencies follow a similar convention like this:
+
+```code
+"dependencies": {
+ "dependency1": "^major.minor.patch"
+ },
+ ...
+```
+
+This is a stub. Help our community expand it.