mirror of
https://github.com/django/django.git
synced 2025-08-04 02:48:35 +00:00
Fixed 32956 -- Lowercased spelling of "web" and "web framework" where appropriate.
This commit is contained in:
parent
acde917456
commit
1024b5e74a
113 changed files with 265 additions and 267 deletions
|
@ -334,7 +334,7 @@ Manager methods
|
|||
|
||||
In practice, you probably won't need to use
|
||||
:class:`~django.contrib.auth.models.AnonymousUser` objects on your own, but
|
||||
they're used by Web requests, as explained in the next section.
|
||||
they're used by web requests, as explained in the next section.
|
||||
|
||||
``Permission`` model
|
||||
====================
|
||||
|
|
|
@ -87,7 +87,7 @@ Finally, there is the :func:`fromfile` factory method which returns a
|
|||
.. admonition:: My logs are filled with GEOS-related errors
|
||||
|
||||
You find many ``TypeError`` or ``AttributeError`` exceptions filling your
|
||||
Web server's log files. This generally means that you are creating GEOS
|
||||
web server's log files. This generally means that you are creating GEOS
|
||||
objects at the top level of some of your Python modules. Then, due to a race
|
||||
condition in the garbage collector, your module is garbage collected before
|
||||
the GEOS object. To prevent this, create :class:`GEOSGeometry` objects
|
||||
|
|
|
@ -5,8 +5,8 @@ GeoDjango
|
|||
.. module:: django.contrib.gis
|
||||
:synopsis: Geographic Information System (GIS) extensions for Django
|
||||
|
||||
GeoDjango intends to be a world-class geographic Web framework. Its goal is to
|
||||
make it as easy as possible to build GIS Web applications and harness the power
|
||||
GeoDjango intends to be a world-class geographic web framework. Its goal is to
|
||||
make it as easy as possible to build GIS web applications and harness the power
|
||||
of spatially enabled data.
|
||||
|
||||
.. toctree::
|
||||
|
|
|
@ -123,7 +123,7 @@ corresponds to the projection system that will be used to interpret the data
|
|||
in the spatial database. [#fnsrid]_ Projection systems give the context to the
|
||||
coordinates that specify a location. Although the details of `geodesy`__ are
|
||||
beyond the scope of this documentation, the general problem is that the earth
|
||||
is spherical and representations of the earth (e.g., paper maps, Web maps)
|
||||
is spherical and representations of the earth (e.g., paper maps, web maps)
|
||||
are not.
|
||||
|
||||
Most people are familiar with using latitude and longitude to reference a
|
||||
|
|
|
@ -6,8 +6,8 @@ Introduction
|
|||
============
|
||||
|
||||
GeoDjango is an included contrib module for Django that turns it into a
|
||||
world-class geographic Web framework. GeoDjango strives to make it as simple
|
||||
as possible to create geographic Web applications, like location-based services.
|
||||
world-class geographic web framework. GeoDjango strives to make it as simple
|
||||
as possible to create geographic web applications, like location-based services.
|
||||
Its features include:
|
||||
|
||||
* Django model fields for `OGC`_ geometries and raster data.
|
||||
|
|
|
@ -6,7 +6,7 @@ GeoDjango Utilities
|
|||
:synopsis: GeoDjango's collection of utilities.
|
||||
|
||||
The :mod:`django.contrib.gis.utils` module contains various utilities that are
|
||||
useful in creating geospatial Web applications.
|
||||
useful in creating geospatial web applications.
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
Django aims to follow Python's :ref:`"batteries included" philosophy
|
||||
<tut-batteries-included>`. It ships with a variety of extra, optional tools
|
||||
that solve common Web-development problems.
|
||||
that solve common web development problems.
|
||||
|
||||
This code lives in ``django/contrib`` in the Django distribution. This document
|
||||
gives a rundown of the packages in ``contrib``, along with any dependencies
|
||||
|
|
|
@ -79,7 +79,7 @@ a :class:`~django.contrib.sitemaps.Sitemap` class (e.g.,
|
|||
A :class:`~django.contrib.sitemaps.Sitemap` class is a Python class that
|
||||
represents a "section" of entries in your sitemap. For example, one
|
||||
:class:`~django.contrib.sitemaps.Sitemap` class could represent all the entries
|
||||
of your Weblog, while another could represent all of the events in your events
|
||||
of your blog, while another could represent all of the events in your events
|
||||
calendar.
|
||||
|
||||
In the simplest case, all these sections get lumped together into one
|
||||
|
|
|
@ -174,7 +174,7 @@ Getting the current domain for display
|
|||
|
||||
LJWorld.com and Lawrence.com both have email alert functionality, which lets
|
||||
readers sign up to get notifications when news happens. It's pretty basic: A
|
||||
reader signs up on a Web form and immediately gets an email saying,
|
||||
reader signs up on a web form and immediately gets an email saying,
|
||||
"Thanks for your subscription."
|
||||
|
||||
It'd be inefficient and redundant to implement this sign up processing code
|
||||
|
|
|
@ -13,7 +13,7 @@ To create any syndication feed, all you have to do is write a short
|
|||
Python class. You can create as many feeds as you want.
|
||||
|
||||
Django also comes with a lower-level feed-generating API. Use this if
|
||||
you want to generate feeds outside of a Web context, or in some other
|
||||
you want to generate feeds outside of a web context, or in some other
|
||||
lower-level way.
|
||||
|
||||
.. _RSS: https://developer.mozilla.org/en-US/docs/Glossary/RSS
|
||||
|
@ -1014,7 +1014,7 @@ For example, to create an Atom 1.0 feed and print it to standard output::
|
|||
>>> from django.utils import feedgenerator
|
||||
>>> from datetime import datetime
|
||||
>>> f = feedgenerator.Atom1Feed(
|
||||
... title="My Weblog",
|
||||
... title="My Blog",
|
||||
... link="https://www.example.com/",
|
||||
... description="In which I write about what I ate today.",
|
||||
... language="en",
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue