Fixed #26438 -- Fixed multiple .objects typos in the docs.

Thanks Pablo Oubiña for the report.

docs/ref/models/options.txt

@@ -132,9 +132,9 @@ Django quotes column and table names behind the scenes.
 
             >>> bar = Bar.objects.get(pk=1)
             >>> # Using model name "bar" as lookup string is deprecated.
-            >>> Foo.object.get(bar=bar)
+            >>> Foo.objects.get(bar=bar)
             >>> # You should use default_related_name "bars".
-            >>> Foo.object.get(bars=bar)
+            >>> Foo.objects.get(bars=bar)
 
 ``get_latest_by``
 -----------------

docs/releases/1.10.txt

@@ -804,11 +804,11 @@ lookup name is deprecated. For example, since ``default_related_name`` is set
 in model ``Bar``, instead of using the model name ``bar`` as the lookup::
 
     >>> bar = Bar.objects.get(pk=1)
-    >>> Foo.object.get(bar=bar)
+    >>> Foo.objects.get(bar=bar)
 
 use the default_related_name ``bars``::
 
-    >>> Foo.object.get(bars=bar)
+    >>> Foo.objects.get(bars=bar)
 
 .. _search-lookup-replacement:
 

docs/topics/db/optimization.txt

@@ -161,7 +161,7 @@ So using the :ref:`example Weblog models <queryset-model-example>`::
 
 will be quicker than:
 
-  >>> entry = Entry.object.get(headline="News Item Title")
+  >>> entry = Entry.objects.get(headline="News Item Title")
 
 because ``id`` is indexed by the database and is guaranteed to be unique.