[Pkg-javascript-commits] [backbone] 13/28: some Markdown snuck in.

[Jonas Smedegaard]

This is an automated email from the git hooks/post-receive script.

js pushed a commit to tag 0.5.3
in repository backbone.

commit f399b0469176148805687db08ef80e97f71a3d33
Author: Jeremy Ashkenas <jashkenas at gmail.com>
Date:   Fri Jul 29 10:06:25 2011 -0400

    some Markdown snuck in.
---
 index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index dfb4927..bc09bce 100644
--- a/index.html
+++ b/index.html
@@ -2447,7 +2447,7 @@ var model = localBackbone.Model.extend(...);
     <p>
       <b>References between Models and Views</b> can be handled several ways. 
       Some people like to have direct pointers, where views correspond 1:1 with
-      models (`model.view` and `view.model`). Others prefer to have intermediate 
+      models (<tt>model.view</tt> and <tt>view.model</tt>). Others prefer to have intermediate 
       "controller" objects that orchestrate the creation and organization of 
       views into a hierarchy. Others still prefer the evented approach, and always
       fire events instead of calling methods directly. All of these style work well.
@@ -2457,7 +2457,7 @@ var model = localBackbone.Model.extend(...);
       <b>Batch operations</b> on Models are common, but often best handled differently
       depending on your server-side setup. Some folks don't mind making individual
       Ajax requests. Others create explicit resources for RESTful batch operations: 
-      `/notes/batch/destroy?ids=1,2,3,4`. Others tunnel REST over JSON, with the 
+      <tt>/notes/batch/destroy?ids=1,2,3,4</tt>. Others tunnel REST over JSON, with the 
       creation of "changeset" requests:
     </p>
     

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-javascript/backbone.git