From 90184ef87ce29c33bd33bf0bb15284f74df83190 Mon Sep 17 00:00:00 2001
From: albert <9526587+ebicoglu@users.noreply.github.com>
Date: Tue, 26 Oct 2021 10:25:21 +0300
Subject: [PATCH] Update Client-Side-Package-Management.md

---
 docs/en/UI/AspNetCore/Client-Side-Package-Management.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/en/UI/AspNetCore/Client-Side-Package-Management.md b/docs/en/UI/AspNetCore/Client-Side-Package-Management.md
index 4ad8d2ace0..8742688af2 100644
--- a/docs/en/UI/AspNetCore/Client-Side-Package-Management.md
+++ b/docs/en/UI/AspNetCore/Client-Side-Package-Management.md
@@ -22,7 +22,7 @@ The benefit of a **standard package** is:
 
 Depending on a standard package is easy. Just add it to your **package.json** file like you normally do. Example:
 
-```
+```json
 {
   ...
   "dependencies": {
@@ -37,7 +37,7 @@ It's suggested to depend on a standard package instead of directly depending on
 
 After depending on a NPM package, all you should do is to run the **yarn** command from the command line to install all the packages and their dependencies:
 
-```
+```bash
 yarn
 ```
 
@@ -69,7 +69,7 @@ The **startup templates** are already configured to work all these out of the bo
 
 A module should define a JavaScript file named `abp.resourcemapping.js` which is formatted as in the example below:
 
-```js
+```json
 module.exports = {
     aliases: {
         "@node_modules": "./node_modules",
@@ -91,7 +91,7 @@ module.exports = {
 
 An example mapping configuration is shown below:
 
-```js
+```json
 mappings: {
     "@node_modules/bootstrap/dist/css/bootstrap.css": "@libs/bootstrap/css/",
     "@node_modules/bootstrap/dist/js/bootstrap.bundle.js": "@libs/bootstrap/js/",