Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Commit f2f5d86

Browse files
Standardize spelling to American English (only in .md files)
1 parent e045dc4 commit f2f5d86

14 files changed

+27
-27
lines changed

‎docs/api-guide/fields.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,7 @@ The `allow_null` option is also available for string fields, although its usage
180180

181181
## EmailField
182182

183-
A text representation, validates the text to be a valid e-mail address.
183+
A text representation, validates the text to be a valid email address.
184184

185185
Corresponds to `django.db.models.fields.EmailField`
186186

‎docs/api-guide/responses.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ source:
1111
1212
REST framework supports HTTP content negotiation by providing a `Response` class which allows you to return content that can be rendered into multiple content types, depending on the client request.
1313

14-
The `Response` class subclasses Django's `SimpleTemplateResponse`. `Response` objects are initialised with data, which should consist of native Python primitives. REST framework then uses standard HTTP content negotiation to determine how it should render the final response content.
14+
The `Response` class subclasses Django's `SimpleTemplateResponse`. `Response` objects are initialized with data, which should consist of native Python primitives. REST framework then uses standard HTTP content negotiation to determine how it should render the final response content.
1515

1616
There's no requirement for you to use the `Response` class, you can also return regular `HttpResponse` or `StreamingHttpResponse` objects from your views if required. Using the `Response` class simply provides a nicer interface for returning content-negotiated Web API responses, that can be rendered to multiple formats.
1717

‎docs/api-guide/serializers.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ When deserializing data, you always need to call `is_valid()` before attempting
155155
serializer.is_valid()
156156
# False
157157
serializer.errors
158-
# {'email': ['Enter a valid e-mail address.'], 'created': ['This field is required.']}
158+
# {'email': ['Enter a valid email address.'], 'created': ['This field is required.']}
159159

160160
Each key in the dictionary will be the field name, and the values will be lists of strings of any error messages corresponding to that field. The `non_field_errors` key may also be present, and will list any general validation errors. The name of the `non_field_errors` key may be customized using the `NON_FIELD_ERRORS_KEY` REST framework setting.
161161

@@ -298,7 +298,7 @@ When dealing with nested representations that support deserializing the data, an
298298
serializer.is_valid()
299299
# False
300300
serializer.errors
301-
# {'user': {'email': ['Enter a valid e-mail address.']}, 'created': ['This field is required.']}
301+
# {'user': {'email': ['Enter a valid email address.']}, 'created': ['This field is required.']}
302302

303303
Similarly, the `.validated_data` property will include nested data structures.
304304

‎docs/api-guide/validators.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,7 +175,7 @@ If you want the date field to be entirely hidden from the user, then use `Hidden
175175
Validators that are applied across multiple fields in the serializer can sometimes require a field input that should not be provided by the API client, but that *is* available as input to the validator.
176176
For this purposes use `HiddenField`. This field will be present in `validated_data` but *will not* be used in the serializer output representation.
177177

178-
**Note:** Using a `read_only=True` field is excluded from writable fields so it won't use a `default=...` argument. Look [3.8 announcement](https://www.django-rest-framework.org/community/3.8-announcement/#altered-the-behaviour-of-read_only-plus-default-on-field).
178+
**Note:** Using a `read_only=True` field is excluded from writable fields so it won't use a `default=...` argument. Look [3.8 announcement](https://www.django-rest-framework.org/community/3.8-announcement/#altered-the-behavior-of-read_only-plus-default-on-field).
179179

180180
REST framework includes a couple of defaults that may be useful in this context.
181181

‎docs/community/3.0-announcement.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -632,7 +632,7 @@ The `MultipleChoiceField` class has been added. This field acts like `ChoiceFiel
632632

633633
The `from_native(self, value)` and `to_native(self, data)` method names have been replaced with the more obviously named `to_internal_value(self, data)` and `to_representation(self, value)`.
634634

635-
The `field_from_native()` and `field_to_native()` methods are removed. Previously you could use these methods if you wanted to customise the behavior in a way that did not simply lookup the field value from the object. For example...
635+
The `field_from_native()` and `field_to_native()` methods are removed. Previously you could use these methods if you wanted to customize the behavior in a way that did not simply lookup the field value from the object. For example...
636636

637637
def field_to_native(self, obj, field_name):
638638
"""A custom read-only field that returns the class name."""

‎docs/community/3.12-announcement.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ See [the schema documentation](https://www.django-rest-framework.org/api-guide/s
5050
## Customizing the operation ID.
5151

5252
REST framework automatically determines operation IDs to use in OpenAPI
53-
schemas. The latest version provides more control for overriding the behaviour
53+
schemas. The latest version provides more control for overriding the behavior
5454
used to generate the operation IDs.
5555

5656
See [the schema documentation](https://www.django-rest-framework.org/api-guide/schemas/#operationid) for more information.

‎docs/community/3.13-announcement.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,6 @@ They must now use the more explicit keyword argument style...
5050
aliases = serializers.ListField(child=serializers.CharField())
5151
```
5252

53-
This change has been made because using positional arguments here *does not* result in the expected behaviour.
53+
This change has been made because using positional arguments here *does not* result in the expected behavior.
5454

5555
See Pull Request [#7632](https://github.com/encode/django-rest-framework/pull/7632) for more details.

‎docs/community/3.15-announcement.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,12 +39,12 @@ By default the URLs created by `SimpleRouter` use regular expressions. This beha
3939

4040
Dependency on pytz has been removed and deprecation warnings have been added, Django will provide ZoneInfo instances as long as USE_DEPRECATED_PYTZ is not enabled. More info on the migration can be found [in this guide](https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html).
4141

42-
## Align `SearchFilter` behaviour to `django.contrib.admin` search
42+
## Align `SearchFilter` behavior to `django.contrib.admin` search
4343

4444
Searches now may contain _quoted phrases_ with spaces, each phrase is considered as a single search term, and it will raise a validation error if any null-character is provided in search. See the [Filtering API guide](../api-guide/filtering.md) for more information.
4545

4646
## Other fixes and improvements
4747

48-
There are a number of fixes and minor improvements in this release, ranging from documentation, internal infrastructure (typing, testing, requirements, deprecation, etc.), security and overall behaviour.
48+
There are a number of fixes and minor improvements in this release, ranging from documentation, internal infrastructure (typing, testing, requirements, deprecation, etc.), security and overall behavior.
4949

5050
See the [release notes](release-notes.md) page for a complete listing.

‎docs/community/3.16-announcement.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,14 @@ The current minimum versions of Django is now 4.2 and Python 3.9.
2929

3030
## Django LoginRequiredMiddleware
3131

32-
The new `LoginRequiredMiddleware` introduced by Django 5.1 can now be used alongside Django REST Framework, however it is not honored for API views as an equivalent behaviour can be configured via `DEFAULT_AUTHENTICATION_CLASSES`. See [our dedicated section](../api-guide/authentication.md#django-51-loginrequiredmiddleware) in the docs for more information.
32+
The new `LoginRequiredMiddleware` introduced by Django 5.1 can now be used alongside Django REST Framework, however it is not honored for API views as an equivalent behavior can be configured via `DEFAULT_AUTHENTICATION_CLASSES`. See [our dedicated section](../api-guide/authentication.md#django-51-loginrequiredmiddleware) in the docs for more information.
3333

3434
## Improved support for UniqueConstraint
3535

3636
The generation of validators for [UniqueConstraint](https://docs.djangoproject.com/en/stable/ref/models/constraints/#uniqueconstraint) has been improved to support better nullable fields and constraints with conditions.
3737

3838
## Other fixes and improvements
3939

40-
There are a number of fixes and minor improvements in this release, ranging from documentation, internal infrastructure (typing, testing, requirements, deprecation, etc.), security and overall behaviour.
40+
There are a number of fixes and minor improvements in this release, ranging from documentation, internal infrastructure (typing, testing, requirements, deprecation, etc.), security and overall behavior.
4141

4242
See the [release notes](release-notes.md) page for a complete listing.

‎docs/community/3.5-announcement.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ a dynamic client library to interact with your API.
8181

8282
Finally, we're also now exposing the schema generation as a
8383
[publicly documented API][schema-generation-api], allowing you to more easily
84-
override the behaviour.
84+
override the behavior.
8585

8686
## Requests test client
8787

@@ -204,18 +204,18 @@ The `'pk'` identifier in schema paths is now mapped onto the actually model fiel
204204
name by default. This will typically be `'id'`.
205205

206206
This gives a better external representation for schemas, with less implementation
207-
detail being exposed. It also reflects the behaviour of using a ModelSerializer
207+
detail being exposed. It also reflects the behavior of using a ModelSerializer
208208
class with `fields = '__all__'`.
209209

210-
You can revert to the previous behaviour by setting `'SCHEMA_COERCE_PATH_PK': False`
210+
You can revert to the previous behavior by setting `'SCHEMA_COERCE_PATH_PK': False`
211211
in the REST framework settings.
212212

213213
### Schema action name representations
214214

215215
The internal `retrieve()` and `destroy()` method names are now coerced to an
216216
external representation of `read` and `delete`.
217217

218-
You can revert to the previous behaviour by setting `'SCHEMA_COERCE_METHOD_NAMES': {}`
218+
You can revert to the previous behavior by setting `'SCHEMA_COERCE_METHOD_NAMES': {}`
219219
in the REST framework settings.
220220

221221
### DjangoFilterBackend

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /