From 4697c166ed73da1ac4ff043893a6690d23acd792 Mon Sep 17 00:00:00 2001
From: Todd Fredrich <tfredrich@gmail.com>
Date: Fri, 18 May 2012 14:13:24 -0600
Subject: [PATCH] Corrected previous heading.

---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 4169105..1e512f8 100644
--- a/index.html
+++ b/index.html
@@ -37,7 +37,7 @@
 		<div class="container">
 			<!-- Main hero unit for a primary marketing message or call to action -->
 			<div class="hero-unit">
-				<h1>Learn REST: A REST Tutorial</h1>
+				<h1>Learn REST: A RESTful Tutorial</h1>
 				<p>Building restful web services, like other programming skills is <strong>part art, part science</strong>. As the Internet industry progresses, creating a REST API becomes more concrete, with emerging best practices. As RESTful Web services don't follow a prescribed standard except for HTTP, it's important to build your RESTful API in accordance with industry best practices to ease development and simplify client adoption.</p>
 				<p>Presently, there aren't a lot of REST API guides to help the lonely developer. <a href="http://www.restapitutorial.com">RestApiTutorial.com</a> is dedicated to tracking REST API best practices and making resources available to enable quick reference and self education for the development crafts-person.  We'll discuss both the art and science of creating REST Web services.</p>
 				<p>Jump in with <a href="restquicktips.html">REST API Quick Tips</a>, a few overarching concepts (based on <a href="http://37signals.com/svn/posts/3018-api-design-for-humans" target="_blank">this post</a> from <a href="http://www.37signals.com" rel="nofollow" target="_blank">37 Signals</a>) created to get you started on the right track.</p>