clarifying morepath page

mattmakai · mattmakai · commit d283f3adc4ec · 2015-01-02T16:23:09.000-05:00
diff --git a/all.html b/all.html
@@ -773,13 +773,13 @@ <h2>Morepath</h2>
 <h2>Why is Morepath an interesting web framework?</h2>
 <p>Simple <a href="http://en.wikipedia.org/wiki/Create,_read,_update_and_delete">CRUD web applications and APIs</a> 
 can be tedious to build when they are driven straight from data models without
-much logic between the model and the view. With the rise of front end 
-JavaScript frameworks many Python web frameworks are becoming 
+much logic between the model and the view. </p>
+<p>With the rise of front end JavaScript frameworks, many Python web frameworks 
+are first being used to build 
 <a href="/application-programming-interfaces.html">RESTful APIs</a> that return JSON
-instead of the framework's original purpose as generating HTML with a 
-templating system. Morepath appears to have been created with the RESTful API
-model in mind and cuts out the assumption that templates will definitely be
-used to generate the web user interface.</p>
+instead rendering HTML via a templating system. Morepath appears to have 
+been created with the RESTful API model approach in mind and cuts out the 
+assumption that templates will drive the user interface.</p>
 <h3>Morepath resources</h3>
 <ul>
 <li>
diff --git a/feeds/all.atom.xml b/feeds/all.atom.xml
@@ -1,2 +1,2 @@
 <?xml version="1.0" encoding="utf-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-01-02T16:20:07Z</updated></feed>
+<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-01-02T16:22:53Z</updated></feed>
diff --git a/morepath.html b/morepath.html
@@ -49,13 +49,13 @@ <h2>Morepath</h2>
 <h2>Why is Morepath an interesting web framework?</h2>
 <p>Simple <a href="http://en.wikipedia.org/wiki/Create,_read,_update_and_delete">CRUD web applications and APIs</a> 
 can be tedious to build when they are driven straight from data models without
-much logic between the model and the view. With the rise of front end 
-JavaScript frameworks many Python web frameworks are becoming 
+much logic between the model and the view. </p>
+<p>With the rise of front end JavaScript frameworks, many Python web frameworks 
+are first being used to build 
 <a href="/application-programming-interfaces.html">RESTful APIs</a> that return JSON
-instead of the framework's original purpose as generating HTML with a 
-templating system. Morepath appears to have been created with the RESTful API
-model in mind and cuts out the assumption that templates will definitely be
-used to generate the web user interface.</p>
+instead rendering HTML via a templating system. Morepath appears to have 
+been created with the RESTful API model approach in mind and cuts out the 
+assumption that templates will drive the user interface.</p>
 <h3>Morepath resources</h3>
 <ul>
 <li>
diff --git a/source/content/pages/02-web-frameworks/0206-morepath.markdown b/source/content/pages/02-web-frameworks/0206-morepath.markdown
@@ -30,13 +30,14 @@ by the developer.
 ## Why is Morepath an interesting web framework?
 Simple [CRUD web applications and APIs](http://en.wikipedia.org/wiki/Create,_read,_update_and_delete) 
 can be tedious to build when they are driven straight from data models without
-much logic between the model and the view. With the rise of front end 
-JavaScript frameworks many Python web frameworks are becoming 
+much logic between the model and the view. 
+
+With the rise of front end JavaScript frameworks, many Python web frameworks 
+are first being used to build 
 [RESTful APIs](/application-programming-interfaces.html) that return JSON
-instead of the framework's original purpose as generating HTML with a 
-templating system. Morepath appears to have been created with the RESTful API
-model in mind and cuts out the assumption that templates will definitely be
-used to generate the web user interface.
+instead rendering HTML via a templating system. Morepath appears to have 
+been created with the RESTful API model approach in mind and cuts out the 
+assumption that templates will drive the user interface.
 
 
 ### Morepath resources

Original file line number	Diff line number	Diff line change
`@@ -1,2 +1,2 @@`
`1`	`1`	`<?xml version="1.0" encoding="utf-8"?>`
`2`		`-<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-01-02T16:20:07Z</updated></feed>`
	`2`	`+<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-01-02T16:22:53Z</updated></feed>`