docs(javascript): update sentry-testkit page (#6445)

Co-authored-by: Billy Vong <billyvg@users.noreply.github.com>
Co-authored-by: Liza Mock <lizka920@gmail.com>

Author: 3 people

src/platforms/javascript/common/configuration/sentry-testkit/index.mdx

@@ -6,9 +6,7 @@ description: "Learn how to assert that the right flow-tracking or error is being
 
 When building tests for your application, you want to assert that the right flow-tracking or error is being sent to Sentry, but without really sending it to the Sentry servers. This way you won't swamp Sentry with false reports during test runs or other CI operations.
 
-Note: [Wix](https://wix.github.io/sentry-testkit/), a Sentry partner, maintains Sentry Testkit.
-
-[Sentry Testkit](https://wix.github.io/sentry-testkit/) is a Sentry plugin that allows intercepting Sentry's reports and further inspection of the data being sent. It enables Sentry to work natively in your application, and by overriding the default Sentry's transport mechanism, the report is not really sent, but rather logged locally into the memory. This way, logged reports can be fetched later for your own usage, verification, or any other use you may have in your local developing/testing environment.
+[Sentry Testkit](https://zivl.github.io/sentry-testkit/) is a Sentry plugin that allows Sentry's reports to be intercepted for further data inspection. It enables Sentry to work natively in your application, by overriding Sentry's default transport mechanism, which makes it so that the report isn't really sent, but rather logged locally into memory. This way, logged reports can be fetched later for your own usage, verification, or any other purpose you may have in your local developing or testing environment.
 
 ## Installation
 
@@ -30,16 +28,23 @@ Sentry.init({
   //... other configurations
 });
 
-// then run any scenario that should call Sentry.catchException(...)
+test('collect error events', function () {
+  // run any scenario that eventually calls Sentry.captureException(...)
+  expect(testkit.reports()).toHaveLength(1);
+  const report = testkit.reports()[0];
+  expect(report).toHaveProperty(/*...*/);
+});
 
-expect(testkit.reports()).toHaveLength(1);
-const report = testkit.reports()[0];
-expect(report).toHaveProperty(/*...*/);
+// Similarly for performance events
+test('collect performance events', function () {
+  // run any scenario that eventually calls Sentry.startTransaction(...)
+  expect(testkit.transactions()).toHaveLength(1);
+});
 ```
 
-You may see more usage examples in the [testing section](https://github.com/wix/sentry-testkit/tree/master/test) of sentry-testkit repository as well.
+You may see more usage examples in the [testing section](https://github.com/zivl/sentry-testkit/tree/master/test) of sentry-testkit repository as well.
 
 ### Testkit API
 
 Sentry Testkit consists of a very simple and straightforward API.
-See the full API description and documentation in [Sentry Testkit Docs](https://wix.github.io/sentry-testkit/).
+See the full API description and documentation in [Sentry Testkit Docs](https://zivl.github.io/sentry-testkit/docs/api).