docs: typos fix in release notes (#3691)

* Update 0-30-1.mdx

* Update 0-30-0.mdx

* Update 0-29-0.mdx

docs/content/docs/updates/release-notes/0-29-0.mdx

@@ -6,7 +6,7 @@ description: Anchor - Release Notes 0.29.0
 Anchor keeps a
 [CHANGELOG](https://github.com/coral-xyz/anchor/blob/master/CHANGELOG.md) but
 it's not easy to make sense what has changed, what effect does the change have
-and how to migrate. This is where release notes comes in, an easy to digest and
+and how to migrate. This is where release notes come in, an easy to digest and
 actionable view for each release.
 
 ---

docs/content/docs/updates/release-notes/0-30-0.mdx

@@ -115,7 +115,7 @@ There are new account constraints for
   - `authority`
   - `program_id`
 
-**Note:** Above values are concatinated with `::` (similar to other Anchor
+**Note:** Above values are concatenated with `::` (similar to other Anchor
 constraints) and have `extensions` prefix e.g.
 `extensions::group_pointer::authority = <EXPR>`.
 
@@ -183,7 +183,7 @@ supports setting `--priority-fee` argument for the IDL commands. For example:
 anchor idl erase-authority --program-id <PROGRAM_ID> --priority-fee 9000
 ```
 
-When the `--priortiy-fee` argument is not specified, the median fee of the last
+When the `--priority-fee` argument is not specified, the median fee of the last
 150 confirmed slots is used.
 
 ### `--no-idl` flag on builds
@@ -245,7 +245,7 @@ get a warning if any of them don't match.
 ### Explicit `overflow-checks` flag
 
 [`overflow-checks`](https://doc.rust-lang.org/cargo/reference/profiles.html#overflow-checks)
-flag is implicitly disabled by default. Anchor workspaces that are crated with
+flag is implicitly disabled by default. Anchor workspaces that are created with
 `anchor init` have this flag enabled, however, Anchor doesn't do any checks for
 it after the initial workspace creation.
 

docs/content/docs/updates/release-notes/0-30-1.mdx

@@ -1,4 +1,4 @@
----
+   ---
 title: 0.30.1
 description: Anchor - Release Notes 0.30.1
 ---
@@ -134,7 +134,7 @@ To fix this problem, a new [crate](https://docs.rs/anchor-lang-idl-spec) that
 only includes the IDL spec has been introduced. The new crate's version will be
 used in the `idl.metadata.spec` field to differentiate between various IDLs.
 
-**NOTE:** This crate is accesible via the main IDL crate from
+**NOTE:** This crate is accessible via the main IDL crate from
 [`anchor_lang_idl::types`](https://docs.rs/anchor-lang-idl/0.1.1/anchor_lang_idl/types/index.html).
 
 ## CLI
@@ -209,7 +209,7 @@ macro can now be used with legacy IDLs (pre Anchor v0.30).
 This works great as long as the program can be described correctly with the
 legacy IDL spec. However, if a program uses non-default features such as zero
 copy, or `repr` modifications, the declaration of the program either won't
-compile, or will be invalid. There are two main solutions in this scenerio:
+compile, or will be invalid. There are two main solutions in this scenario:
 
 - Use the `idl convert` command, and manually fix the invalid parts
 - Generate the program's IDL by upgrading the program to Anchor v0.30