From 396576079e7e0b36f7ed0f9813954e2a6dfebb47 Mon Sep 17 00:00:00 2001
From: ravikiranh0 <60516768+ravikiranh0@users.noreply.github.com>
Date: Thu, 1 Oct 2020 13:17:11 +0530
Subject: [PATCH] Update README

---
 README | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README b/README
index a1db73c..ee6684b 100644
--- a/README
+++ b/README
@@ -5,7 +5,7 @@ needed to create database-backed web-applications according to the
 Model-View-Control pattern of separation. This pattern splits the view (also
 called the presentation) into "dumb" templates that are primarily responsible
 for inserting pre-built data in between HTML tags. The model contains the
-"smart" domain objects (such as Account, Product, Person, Post) that holds all
+"smart" domain objects (such as Account, Product, Person, Post) that hold all
 the business logic and knows how to persist themselves to a database. The
 controller handles the incoming requests (such as Save New Account, Update
 Product, Show Post) by manipulating the model and directing data to the view.
@@ -13,7 +13,7 @@ Product, Show Post) by manipulating the model and directing data to the view.
 In Rails, the model is handled by what's called an object-relational mapping
 layer entitled Active Record. This layer allows you to present the data from
 database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
+methods. You can read more about Active Record at
 link:files/vendor/rails/activerecord/README.html.
 
 The controller and view are handled by the Action Pack, which handles both