From e2048583c1d21399efa1cabb80bb332b313a1023 Mon Sep 17 00:00:00 2001 From: Filipe Moreira Date: Mon, 5 Mar 2012 16:28:11 +0100 Subject: Small typo fix --- railties/guides/source/api_app.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'railties/guides') diff --git a/railties/guides/source/api_app.textile b/railties/guides/source/api_app.textile index 622e049da5..69e6592aed 100644 --- a/railties/guides/source/api_app.textile +++ b/railties/guides/source/api_app.textile @@ -27,7 +27,7 @@ This guide covers building a Rails application that serves JSON resources to an h3. Why use Rails for JSON APIs? -The first question a lot of people have when thinking about building a JSON API using Rails is: "isn't using Rails to spit out some JSON overkill? Shouldn't I just use something like Siantra?" +The first question a lot of people have when thinking about building a JSON API using Rails is: "isn't using Rails to spit out some JSON overkill? Shouldn't I just use something like Sinatra?" For very simple APIs, this may be true. However, even in very HTML-heavy applications, most of an application's logic is actually outside of the view layer. -- cgit v1.2.3