minor cleanup

Author: Lms24

packages/svelte/src/sdk.ts

@@ -24,7 +24,7 @@ export function init(options: BrowserOptions): void {
 
 /**
  * Adds a global event processor to detect if the SDK is initialized in a SvelteKit frontend,
- * in which case add SvelteKit an event.modules entry to outgoing events.
+ * in which case we add SvelteKit an event.modules entry to outgoing events.
  * SvelteKit detection is performed only once, when the event processor is called for the
  * first time. We cannot perform this check upfront (directly when init is called) because
  * at this time, the HTML element might not yet be accessible.
@@ -52,7 +52,8 @@ export function detectAndReportSvelteKit(): void {
 /**
  * To actually detect a SvelteKit frontend, we search the DOM for a special
  * div that's inserted by SvelteKit when the page is rendered. It's identifyed
- * by 'svelte-announcer' and used to improve page accessibility.
+ * by its id, 'svelte-announcer', and it's used to improve page accessibility.
+ * This div is not present when only using Svelte without SvelteKit.
  *
  * @see https://github.com/sveltejs/kit/issues/307 for more information
  */

packages/svelte/test/sdk.test.ts

@@ -13,7 +13,7 @@ addGlobalEventProcessorFunction.mockImplementation(proc => {
 jest.mock('@sentry/browser');
 
 describe('Initialize Svelte SDk', () => {
-  afterEach(() => {
+  afterAll(() => {
     jest.clearAllMocks();
   });
 

packages/utils/src/browser.ts

@@ -124,7 +124,7 @@ export function getLocationHref(): string {
 }
 
 /**
- * Gets a DOM element via document.querySelector.
+ * Gets a DOM element by using document.querySelector.
  *
  * This wrapper will first check for the existance of the function before
  * actually calling it so that we don't have to take care of this check,