aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorTom Christie2012-11-05 17:03:22 +0000
committerTom Christie2012-11-05 17:03:22 +0000
commit455a8cedcf5aa1f265ae95d4f3bff359d51910c0 (patch)
tree63fd2b5abe12fbb8a4b7d5bf253b37f44cca3e64 /docs
parent9746abdf72738b85ea0d428db2f936e87de0fe55 (diff)
downloaddjango-rest-framework-455a8cedcf5aa1f265ae95d4f3bff359d51910c0.tar.bz2
Tweaks
Diffstat (limited to 'docs')
-rw-r--r--docs/api-guide/fields.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/api-guide/fields.md b/docs/api-guide/fields.md
index fe621335..411f7944 100644
--- a/docs/api-guide/fields.md
+++ b/docs/api-guide/fields.md
@@ -239,7 +239,7 @@ Then an example output format for a Bookmark instance would be:
`PrimaryKeyRelatedField` and `ManyPrimaryKeyRelatedField` will represent the target of the relationship using it's primary key.
-Be default these fields read-write, although you can change this behaviour using the `read_only` flag.
+By default these fields are read-write, although you can change this behaviour using the `read_only` flag.
**Arguments**:
@@ -249,18 +249,18 @@ Be default these fields read-write, although you can change this behaviour using
`SlugRelatedField` and `ManySlugRelatedField` will represent the target of the relationship using a unique slug.
-Be default these fields read-write, although you can change this behaviour using the `read_only` flag.
+By default these fields read-write, although you can change this behaviour using the `read_only` flag.
**Arguments**:
-* `slug_field` - The field on the target that should used as the representation. This should be a field that uniquely identifies any given instance. For example, `username`.
+* `slug_field` - The field on the target that should be used to represent it. This should be a field that uniquely identifies any given instance. For example, `username`.
* `queryset` - By default `ModelSerializer` classes will use the default queryset for the relationship. `Serializer` classes must either set a queryset explicitly, or set `read_only=True`.
## HyperlinkedRelatedField / ManyHyperlinkedRelatedField
`HyperlinkedRelatedField` and `ManyHyperlinkedRelatedField` will represent the target of the relationship using a hyperlink.
-Be default, `HyperlinkedRelatedField` is read-write, although you can change this behaviour using the `read_only` flag.
+By default, `HyperlinkedRelatedField` is read-write, although you can change this behaviour using the `read_only` flag.
**Arguments**: