From a12305a2e8a13cb8a8b6af0ceb51a62f15fcb0cb Mon Sep 17 00:00:00 2001 From: Ghouse Mohamed Date: Wed, 23 Feb 2022 04:16:04 +0530 Subject: [PATCH] Fixes controller name highlight in guide --- guides/source/layouts_and_rendering.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/source/layouts_and_rendering.md b/guides/source/layouts_and_rendering.md index 01a3566a0e..85482f75ce 100644 --- a/guides/source/layouts_and_rendering.md +++ b/guides/source/layouts_and_rendering.md @@ -157,7 +157,7 @@ render template: "products/show" The above two ways of rendering (rendering the template of another action in the same controller, and rendering the template of another action in a different controller) are actually variants of the same operation. -In fact, in the BooksController class, inside of the update action where we want to render the edit template if the book does not update successfully, all of the following render calls would all render the `edit.html.erb` template in the `views/books` directory: +In fact, in the `BooksController` class, inside of the update action where we want to render the edit template if the book does not update successfully, all of the following render calls would all render the `edit.html.erb` template in the `views/books` directory: ```ruby render :edit