From 5cece57c93aff28010defece05085cff903fb9d2 Mon Sep 17 00:00:00 2001
From: Michael Lavrisha <michael.lavrisha@gmail.com>
Date: Sun, 24 Jul 2011 16:36:23 -0600
Subject: Simpler brief explanation of Rails and REST

---
 railties/guides/source/getting_started.textile | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

(limited to 'railties/guides/source/getting_started.textile')

diff --git a/railties/guides/source/getting_started.textile b/railties/guides/source/getting_started.textile
index a9994a2602..3a1a0fe64a 100644
--- a/railties/guides/source/getting_started.textile
+++ b/railties/guides/source/getting_started.textile
@@ -198,9 +198,8 @@ For example, the following HTTP request:
 <tt>DELETE /photos/17</tt>
 
 refers to a photo resource with an ID of 17 and indicates an action to be taken
-upon it: deletion. REST is a natural style for the architecture of web applications,
-and Rails hooks into this shielding you from many of the RESTful complexities and
-browser quirks.
+upon it: deletion. REST is a natural web application architecture which Rails
+abstracts, shielding you from RESTful complexities and browser quirks.
 
 If you'd like more details on REST as an architectural style, these resources
 are more approachable than Fielding's thesis:
-- 
cgit v1.2.3

