diff --git a/src/pages/[platform]/build-a-backend/more-features/analytics/analytics-migration-guide/index.mdx b/src/pages/[platform]/build-a-backend/more-features/analytics/analytics-migration-guide/index.mdx
index e44e4892626..b01c3347830 100644
--- a/src/pages/[platform]/build-a-backend/more-features/analytics/analytics-migration-guide/index.mdx
+++ b/src/pages/[platform]/build-a-backend/more-features/analytics/analytics-migration-guide/index.mdx
@@ -28,7 +28,7 @@ export function getStaticProps(context) {
 
 ## Record and Configuration APIs
 
-As of v6 of Amplify, you will now import the functional API’s directly from the `aws-amplify/analytics` path as shown below. 
+As of v6 of Amplify JavaScript, you will now import the functional API’s directly from the `aws-amplify/analytics` path as shown below. 
 
 Note: Red lines of code are v5 and Green lines are v6.
 
@@ -83,7 +83,7 @@ Note: Red lines of code are v5 and Green lines are v6.
 ```
 ## Analytics.identifyUser
 
-You can identify an user with Analytics with `identifyUser` API, 
+You can identify an Analytics user with the `identifyUser` API, 
 
 ```ts
 import { identifyUser } from 'aws-amplify/analytics';
@@ -95,7 +95,7 @@ identifyUser({
 
 ```
 ## Streaming data
-You can stream analytics data to Kinesis. To configure Kinesis with Amplify, reference the [Installation and Configuration](https://docs.amplify.aws/react/build-a-backend/more-features/analytics/streaming-data/#installation-and-configuration) section of the documentation. Below is an example on how to stream data and flush events as needed, 
+You can stream analytics data to Kinesis. To configure Kinesis with Amplify, reference the [Installation and Configuration](https://docs.amplify.aws/react/build-a-backend/more-features/analytics/streaming-data/#installation-and-configuration) section of the documentation. Below is an example on how to stream data and flush events,
 
 ```ts
 import { record, flushEvents } from 'aws-amplify/analytics/kinesis';
diff --git a/src/pages/[platform]/build-a-backend/more-features/in-app-messaging/in-app-messaging-migration-guide/index.mdx b/src/pages/[platform]/build-a-backend/more-features/in-app-messaging/in-app-messaging-migration-guide/index.mdx
index 857bab1c423..54232e17107 100644
--- a/src/pages/[platform]/build-a-backend/more-features/in-app-messaging/in-app-messaging-migration-guide/index.mdx
+++ b/src/pages/[platform]/build-a-backend/more-features/in-app-messaging/in-app-messaging-migration-guide/index.mdx
@@ -21,7 +21,7 @@ export function getStaticProps(context) {
 
 ## Initialization and syncing messages
 
-As of v6 of Amplify, you will now import the functional API’s directly from the `aws-amplify/in-app-messaging` path as shown below. 
+As of v6 of Amplify JavaScript, you will now import the functional API’s directly from the `aws-amplify/in-app-messaging` path as shown below. 
 
 Note: Red lines of code are v5 and Green lines are v6.
 
@@ -70,7 +70,7 @@ const sendEvent = (eventName: string) => {
 
 ## IdentifyUser
 
-The input format of the `identifyUser` has slightly changed. The below table shows the differences in the input type.
+The input format of the `identifyUser` has changed slightly. The below table shows the differences in the input type.
 
 | Difference | v5 | v6 |
 | ---- | ---- | ----------- |
diff --git a/src/pages/[platform]/build-a-backend/push-notifications/push-notifications-migration-guide/index.mdx b/src/pages/[platform]/build-a-backend/push-notifications/push-notifications-migration-guide/index.mdx
index cc7e730e311..4c7e0303e6f 100644
--- a/src/pages/[platform]/build-a-backend/push-notifications/push-notifications-migration-guide/index.mdx
+++ b/src/pages/[platform]/build-a-backend/push-notifications/push-notifications-migration-guide/index.mdx
@@ -21,7 +21,7 @@ export function getStaticProps(context) {
 
 ## Initialize, request permissions, and receive device tokens
 
-As of v6 of Amplify, you will now import the functional API’s directly from the `aws-amplify/push-notifications` path as shown in the code block. You can also see the differences in APIs for initializing push notifications, asking for the permission or it's status and finally how to obtain the device token. 
+As of v6 of Amplify JavaScript, you will now import the functional API’s directly from the `aws-amplify/push-notifications` path as shown in the code block. You can also see the differences in APIs for initializing push notifications, asking for the permission or its status and finally how to obtain the device token. 
 
 Note: Red lines of code are v5 and Green lines are v6.
 
@@ -127,7 +127,7 @@ const myNotificationOpenedHandler = (notification) => {
 ```
 ## IdentityUser
 
-Differences in identifying a user is as shown below. The input type change is identical to the changes made for the `identifyUser` of the In App Messaging category mentioned in its section.
+Differences in identifying a user is as shown below. The input type change is identical to the changes made for the `identifyUser` of the In App Messaging category mentioned above.
 
 ```diff
 - import { Notifications } from 'aws-amplify';