From 084a3e7303bb1575270c5f83a8f81e585ed40991 Mon Sep 17 00:00:00 2001
From: Subash-Lamichhane <077bct081.subash@pcampus.edu.np>
Date: Thu, 19 Oct 2023 21:04:56 +0545
Subject: [PATCH] chore: fixed typos

---
 CONTRIBUTING.md | 2 +-
 MIGRATION.md    | 8 ++++----
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9048da5efddf..9af7a880a407 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -132,7 +132,7 @@ Additional labels for categorization can be added, and the Sentry SDK team may a
 ### Pull Requests (PRs)
 
 PRs are merged via `Squash and merge`.
-This means that all commits on the branch will be squashed into a single commit, and commited as such onto master.
+This means that all commits on the branch will be squashed into a single commit, and committed as such onto master.
 
 * The PR name can generally follow the commit name (e.g. `feat(core): Set custom transaction source for event processors`)
 * Make sure to rebase the branch on `master` before squashing it
diff --git a/MIGRATION.md b/MIGRATION.md
index 6dc1886f7174..7f626efe7e23 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -100,7 +100,7 @@ Sentry.init({
 
 ## Replay options changed (since 7.35.0) - #6645
 
-Some options for replay have been depracted in favor of new APIs.
+Some options for replay have been deprecated in favor of new APIs.
 See [Replay Migration docs](./packages/replay/MIGRATION.md#upgrading-replay-from-7340-to-7350) for details.
 
 ## Renaming of Next.js wrapper methods (since 7.31.0) - #6790
@@ -162,7 +162,7 @@ Running the new SDK version on Node.js v6 is therefore highly discouraged.
 
 ## Removal of `@sentry/minimal`
 
-The `@sentry/minimal` package was deleted and it's functionality was moved to `@sentry/hub`. All exports from `@sentry/minimal` should be avaliable in `@sentry/hub` other than `_callOnClient` function which was removed.
+The `@sentry/minimal` package was deleted and it's functionality was moved to `@sentry/hub`. All exports from `@sentry/minimal` should be available in `@sentry/hub` other than `_callOnClient` function which was removed.
 
 ```ts
 // New in v7:
@@ -184,7 +184,7 @@ import {
 
 ## Explicit Client Options
 
-In v7, we've updated the `Client` to have options seperate from the options passed into `Sentry.init`. This means that constructing a client now requires 3 options: `integrations`, `transport` and `stackParser`. These can be customized as you see fit.
+In v7, we've updated the `Client` to have options separate from the options passed into `Sentry.init`. This means that constructing a client now requires 3 options: `integrations`, `transport` and `stackParser`. These can be customized as you see fit.
 
 ```ts
 import { BrowserClient, defaultStackParser, defaultIntegrations, makeFetchTransport } from '@sentry/browser';
@@ -764,7 +764,7 @@ this case is the `event_id`, in case the event will not be sent because of filte
 In `4.x` we had both `close` and `flush` on the `Client` draining the internal queue of events, helpful when you were
 using `@sentry/node` on a serverless infrastructure.
 
-Now `close` and `flush` work similar, with the difference that if you call `close` in addition to returing a `Promise`
+Now `close` and `flush` work similar, with the difference that if you call `close` in addition to returning a `Promise`
 that you can await it also **disables** the client so it will not send any future events.
 
 # Migrating from `raven-js` to `@sentry/browser`