Update docs/platforms/javascript/common/best-practices/micro-frontends.mdx

lizokm · web-flow · commit 54be2b97a95e · 2024-12-05T14:25:56.000-08:00
diff --git a/docs/platforms/javascript/common/best-practices/micro-frontends.mdx b/docs/platforms/javascript/common/best-practices/micro-frontends.mdx
@@ -22,7 +22,7 @@ keywords:
   ]
 ---
 <Alert>
-In order for the Sentry JavaScript SDK to work with your micro frontends, make sure that all micro frontends that import from an `@sentry/*` package are using the same version of the Sentry SDK.
+To ensure the Sentry JavaScript SDK works with your micro frontends, make sure all micro frontends that import from a `@sentry/*` package are using the same version of the Sentry SDK.
 </Alert>
 
 If your app uses micro frontends, it’s very useful to be able to track which one an error is coming from. To do this with Sentry, you can create either an automatic or a manual setup where you send events to separate Sentry projects representing each of your micro frontends. This makes it easier to see what’s going wrong and where, helping you track issues and fix them faster, especially in complex frontend architectures.

Original file line number	Diff line number	Diff line change
`@@ -22,7 +22,7 @@ keywords:`
`22`	`22`	`]`
`23`	`23`	`---`
`24`	`24`	`<Alert>`
`25`		-In order for the Sentry JavaScript SDK to work with your micro frontends, make sure that all micro frontends that import from an `@sentry/*` package are using the same version of the Sentry SDK.
	`25`	+To ensure the Sentry JavaScript SDK works with your micro frontends, make sure all micro frontends that import from a `@sentry/*` package are using the same version of the Sentry SDK.
`26`	`26`	`</Alert>`
`27`	`27`
`28`	`28`	`If your app uses micro frontends, it’s very useful to be able to track which one an error is coming from. To do this with Sentry, you can create either an automatic or a manual setup where you send events to separate Sentry projects representing each of your micro frontends. This makes it easier to see what’s going wrong and where, helping you track issues and fix them faster, especially in complex frontend architectures.`