mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-04 19:08:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

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

Browse source
This commit is contained in:
David Smith 2021-07-23 07:48:16 +01:00 • committed by Mariusz Felisiak
parent acde917456
commit 1024b5e74a
113 changed files with 265 additions and 267 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/misc/design-philosophies.txt
View file

@ -20,7 +20,7 @@ A fundamental goal of Django's stack is `loose coupling and tight cohesion`_.
The various layers of the framework shouldn't "know" about each other unless
absolutely necessary.
For example, the template system knows nothing about Web requests, the database
For example, the template system knows nothing about web requests, the database
layer knows nothing about data display and the view system doesn't care which
template system a programmer uses.
@ -43,8 +43,8 @@ introspection.
Quick development
-----------------
The point of a Web framework in the 21st century is to make the tedious aspects
of Web development fast. Django should allow for incredibly quick Web
The point of a web framework in the 21st century is to make the tedious aspects
of web development fast. Django should allow for incredibly quick web
development.
.. _dry:
@ -173,7 +173,7 @@ Encourage best practices
The framework should make it just as easy (or even easier) for a developer to
design pretty URLs than ugly ones.
File extensions in Web-page URLs should be avoided.
File extensions in web-page URLs should be avoided.
Vignette-style commas in URLs deserve severe punishment.
@ -185,7 +185,7 @@ Definitive URLs
.. index:: urls; definitive
Technically, ``foo.com/bar`` and ``foo.com/bar/`` are two different URLs, and
search-engine robots (and some Web traffic-analyzing tools) would treat them as
search-engine robots (and some web traffic-analyzing tools) would treat them as
separate pages. Django should make an effort to "normalize" URLs so that
search-engine robots don't get confused.