aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--railties/guides/source/api_app.textile2
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/api_app.textile b/railties/guides/source/api_app.textile
index 6a7f8ecabe..d51fcb2d58 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.