diff --git a/guides/1)getting_started/2)key_features.md b/guides/1)getting_started/2)key_features.md
index 461798582a..a92c63e09f 100644
--- a/guides/1)getting_started/2)key_features.md
+++ b/guides/1)getting_started/2)key_features.md
@@ -15,7 +15,7 @@ You can load a large dataset into the examples to browse and interact with the d
 
 You wish to pass custom error messages to the user. To do so, raise a `gr.Error("custom message")` to display an error message. If you try to divide by zero in the the calculator demo above, a popup modal will display the custom error message.
 
-## Decriptive Content
+## Descriptive Content
 
 In the previous example, you may have noticed the `title=` and `description=` keyword arguments in the `Interface` constructor that helps users understand your app.
 
diff --git a/guides/3)building_with_blocks/1)blocks_and_event_listeners.md b/guides/3)building_with_blocks/1)blocks_and_event_listeners.md
index dd6afecce3..e09aadb5a7 100644
--- a/guides/3)building_with_blocks/1)blocks_and_event_listeners.md
+++ b/guides/3)building_with_blocks/1)blocks_and_event_listeners.md
@@ -10,7 +10,7 @@ $code_hello_blocks
 $demo_hello_blocks
 
 - First, note the `with gr.Blocks() as demo:` clause. The Blocks app code will be contained within this clause.
-- Next come the Components. These are the same Components used in `Interface`. However, instead of being being passed to some constructor, Components are automatically added to the Blocks as they are created within the `with` clause.
+- Next come the Components. These are the same Components used in `Interface`. However, instead of being passed to some constructor, Components are automatically added to the Blocks as they are created within the `with` clause.
 - Finally, the `click()` event listener. Event listeners define the data flows within the app. In the example above, the listener ties the two Textboxes together. The Textbox `name` acts as the input and Textbox `output` acts as the output to the `greet` method. This dataflow is triggered when the Button `greet_btn` is clicked. Like an Interface, an event listener can take multiple inputs or outputs.
 
 ## Event Listeners and Interactivity
diff --git a/guides/3)building_with_blocks/2)controlling_layout.md b/guides/3)building_with_blocks/2)controlling_layout.md
index 0814b3562f..2e294aa6cf 100644
--- a/guides/3)building_with_blocks/2)controlling_layout.md
+++ b/guides/3)building_with_blocks/2)controlling_layout.md
@@ -54,7 +54,7 @@ $demo_blocks_form
 
 ## Defining and Rendering Components Separately
 
-In some cases, you might want to define components before you actually render them in your UI. For instance, you might want to show an examples section using `gr.Examples` above the corresponding `gr.Textbox` input. Since `gr.Examples` requires as a parameter the input component object, you will need to first define the input component, but then render it later, after you have definted the `gr.Examples` object.
+In some cases, you might want to define components before you actually render them in your UI. For instance, you might want to show an examples section using `gr.Examples` above the corresponding `gr.Textbox` input. Since `gr.Examples` requires as a parameter the input component object, you will need to first define the input component, but then render it later, after you have defined the `gr.Examples` object.
 
 The solution to this is to define the `gr.Textbox` outside of the `gr.Blocks()` scope and use the component's `.render()` method wherever you'd like it placed in the UI.