diff --git a/docs/resources/server/recipes/custom.md b/docs/resources/server/recipes/custom.md
index ea5e67da..81c34daf 100644
--- a/docs/resources/server/recipes/custom.md
+++ b/docs/resources/server/recipes/custom.md
@@ -70,7 +70,7 @@ public class RightClickBlockRecipe implements Recipe<RightClickBlockInput> {
     }
 
     // When true, will prevent the recipe from being synced within the recipe book or awarded on use/unlock.
-    // This should only be true if the recipe shouldn't appear in a recipe book, such as extended a map.
+    // This should only be true if the recipe shouldn't appear in a recipe book, such as map extending.
     // Although this recipe takes in an input state, it could still be used in a custom recipe book using
     //   the methods below.
     @Override
diff --git a/docs/resources/server/recipes/index.md b/docs/resources/server/recipes/index.md
index db2a11f4..c349d6f4 100644
--- a/docs/resources/server/recipes/index.md
+++ b/docs/resources/server/recipes/index.md
@@ -39,7 +39,7 @@ A full list of types provided by Minecraft can be found in the [Built-In Recipe
 
 ## Using Recipes
 
-Recipes are loaded, stored and obtained via the `RecipeManager` class, which is in turn obtained via `ServerLevel#recipeAccess` or - if you don't have a `ServerLevel` available - `ServerLifecycleHooks.getCurrentServer()#getRecipeManager`. The server does not sync the recipes to the client by default, instead it only sends the `RecipePropertySet`s for restricting inputs on menu slots. Additionally, whenever a recipe is unlocked for the recipe book, its `RecipeDisplay`s via `RecipeDisplayEntry`s are sent to the client (excluding all recipes where `Recipe#isSpecial` returns true) As such, recipe logic should always run on the server.
+Recipes are loaded, stored and obtained via the `RecipeManager` class, which is in turn obtained via `ServerLevel#recipeAccess` or - if you don't have a `ServerLevel` available - `ServerLifecycleHooks.getCurrentServer()#getRecipeManager`. The server does not sync the recipes to the client by default, instead it only sends the `RecipePropertySet`s for restricting inputs on menu slots. Additionally, whenever a recipe is unlocked for the recipe book, its `RecipeDisplay`s and the corresponding `RecipeDisplayEntry`s are sent to the client (excluding all recipes where `Recipe#isSpecial` returns true) As such, recipe logic should always run on the server.
 
 The easiest way to get a recipe is by its resource key: