Django-floppyforms -> django-floppyforms.

jazzband · Mar 31, 2014 · f7fe8f6 · f7fe8f6
1 parent 08c669c
commit f7fe8f6
Show file tree

Hide file tree

Showing 5 changed files with 9 additions and 9 deletions.
diff --git a/README.rst b/README.rst
@@ -1,4 +1,4 @@
-Django-floppyforms
+django-floppyforms
 ==================
 
 .. image:: https://api.travis-ci.org/gregmuellegger/django-floppyforms.png

diff --git a/benchmark.py b/benchmark.py
@@ -36,7 +36,7 @@ def time(stmt):
 
 if __name__ == '__main__':
     print "Plain Django:", time(django)
-    print "Django-floppyforms:", time(flop)
+    print "django-floppyforms:", time(flop)
 
 INSTALLED_APPS = (
     'floppyforms'

diff --git a/docs/differences.rst b/docs/differences.rst
@@ -122,7 +122,7 @@ handled`__ for more details).
 
 __ https://docs.djangoproject.com/en/dev/ref/templates/api/#invalid-template-variables
 
-Django-floppyforms assumes in its predefined form layouts that
+django-floppyforms assumes in its predefined form layouts that
 all filters are applied. You can work around this by making your
 ``TEMPLATE_STRING_IF_INVALID`` evaluate to ``False`` but still keep its
 string representation. Here is an example how you could achieve this in your

diff --git a/docs/geodjango.rst b/docs/geodjango.rst
@@ -3,7 +3,7 @@ GeoDjango widgets
 
 .. image:: images/geomcollection.png
 
-Django-floppyforms provides fields and rich widgets for easy manipulation of
+django-floppyforms provides fields and rich widgets for easy manipulation of
 GEOS geometry fields. All geometry types are supported thanks to OpenLayers
 and a custom WKT parser/serializer implementing some Django-specific tweaks.
 
@@ -39,7 +39,7 @@ your project.
 Widget types
 ------------
 
-Django-floppyforms provides **base widgets** and **geometry-specific
+django-floppyforms provides **base widgets** and **geometry-specific
 widgets**:
 
 * **base widgets** are in charge of rendering a map from a specific map

diff --git a/docs/index.rst b/docs/index.rst
@@ -1,7 +1,7 @@
-Django-floppyforms
+django-floppyforms
 ==================
 
-Django-floppyforms is an application that gives you full control of the
+**django-floppyforms** is an application that gives you full control of the
 output of forms rendering. The forms API and features are exactly the same
 as Django's, the key difference is that fields and widgets are rendered in
 templates instead of using string interpolation, giving you full control of
@@ -178,7 +178,7 @@ does it affect performance? You can try with this little script:
         return t.timeit(number=1000)
 
     print "Plain django:", time(django)
-    print "Django-floppyforms:", time(flop)
+    print "django-floppyforms:", time(flop)
 
 The result varies if you're doing template caching or not. To put it simply,
 here is the average time for a single iteration on a MacBookPro @ 2.53GHz.
@@ -187,7 +187,7 @@ here is the average time for a single iteration on a MacBookPro @ 2.53GHz.
 Method             Time without template caching Time with template caching
 ================== ============================= ===========================
 Plain Django       1.63973999023 msec            1.6320669651 msec
-Django-floppyforms 9.05481505394 msec            3.0161819458 msec
+django-floppyforms 9.05481505394 msec            3.0161819458 msec
 ================== ============================= ===========================
 
 Even with template caching, the rendering time is doubled. However the impact