diff --git a/packs/node-js/node-js/config.yml b/packs/node-js/node-js/config.yml
index 03b07d83ec..48996c3afe 100644
--- a/packs/node-js/node-js/config.yml
+++ b/packs/node-js/node-js/config.yml
@@ -7,10 +7,10 @@ description: >-
   Node.js is famous for its asynchronous, event-driven, non-blocking I/O model. However, these attributes can be inconvenient because verifying the correctness of an application with asynchronous nested callbacks is complex. So, it’s important to watch executing Node.js systems closely. Monitoring your Node.js applications ensures optimal performance, allows the maximization of system availability, and ensures that a system’s health is well maintained.
  
   ## What should you look for in a Node.js dashboard? 
-  Any reliable Node.js network monitor must provide enough information to identify the problem sources. Some crucial information includes process ID, log management, request rate, application availability, resource usage, uptime, downtime, system health, error rates and handling, number of connections, load average, and latency. 
+  A reliable Node.js network monitor must provide enough information to identify the problem sources. Some crucial information includes process ID, log management, request rate, application availability, resource usage, uptime, downtime, system health, error rates and handling, number of connections, load average, and latency. 
  
   ## What’s Included in the Node.js Pack?
-  - Multiple high-value alerts, including adpex score and CPU utilization
+  - Multiple high-value alerts, including Apdex score and CPU utilization
   - Informative dashboards (top 5 slowest transactions, throughput comparisons, and more)
  
   ## The Value of New Relic’s Node.js Pack