Fixed 32956 -- Lowercased spelling of "web" and "web framework" where appropriate.

1 files changed, 2 insertions, 2 deletions

diff --git a/docs/topics/db/optimization.txt b/docs/topics/db/optimization.txt
index 180cd60a46..c9a0396b89 100644
--- a/docs/topics/db/optimization.txt
+++ b/docs/topics/db/optimization.txt
@@ -81,7 +81,7 @@ Understand cached attributes
 
 As well as caching of the whole ``QuerySet``, there is caching of the result of
 attributes on ORM objects. In general, attributes that are not callable will be
-cached. For example, assuming the :ref:`example Weblog models
+cached. For example, assuming the :ref:`example blog models
 <queryset-model-example>`::
 
   >>> entry = Entry.objects.get(id=1)
@@ -164,7 +164,7 @@ First, the query will be quicker because of the underlying database index.
 Also, the query could run much slower if multiple objects match the lookup;
 having a unique constraint on the column guarantees this will never happen.
 
-So using the :ref:`example Weblog models <queryset-model-example>`::
+So using the :ref:`example blog models <queryset-model-example>`::
 
   >>> entry = Entry.objects.get(id=10)