diff --git a/content/courses/onchain-development/intro-to-anchor-frontend.md b/content/courses/onchain-development/intro-to-anchor-frontend.md
index 7d2a419bb..ecbe269e3 100644
--- a/content/courses/onchain-development/intro-to-anchor-frontend.md
+++ b/content/courses/onchain-development/intro-to-anchor-frontend.md
@@ -196,7 +196,7 @@ import idl from "./idl.json";
 
 You would _ideally_ also require types for the IDL which would make it easier to
 interact with the program. The types can be found at `/target/types` folder
-after you have build your program. Here are the types for the above IDL which
+after you have built your program. Here are the types for the above IDL which
 when you notice has the exact same structure as the IDL but are just as type
 helper.
 
diff --git a/docs/advanced/confirmation.md b/docs/advanced/confirmation.md
index 02cc91ad5..eb698b009 100644
--- a/docs/advanced/confirmation.md
+++ b/docs/advanced/confirmation.md
@@ -341,7 +341,7 @@ of the cluster state with one of the following methods:
 1. Fetch your RPC node's highest processed slot by using the
    [`getSlot`](/docs/rpc/http/getSlot.mdx) RPC API with the `processed`
    commitment level and then call the
-   [`getMaxShredInsertSlot](/docs/rpc/http/getMaxShredInsertSlot.mdx) RPC API to
+   [`getMaxShredInsertSlot`](/docs/rpc/http/getMaxShredInsertSlot.mdx) RPC API to
    get the highest slot that your RPC node has received a “shred” of a block
    for. If the difference between these responses is very large, the cluster is
    producing blocks far ahead of what the RPC node has processed.