diff options
| author | Casey Duncan <casey.duncan@gmail.com> | 2010-12-31 14:01:39 -0700 |
|---|---|---|
| committer | Casey Duncan <casey.duncan@gmail.com> | 2010-12-31 14:01:39 -0700 |
| commit | 597a6d7a6cca0865e114359010d3e15f5fb036b1 (patch) | |
| tree | 620d55dd9bf7b574d09c72344697cd34786eabe2 /docs | |
| parent | 26bb68f8f351ce8481ee066b5108274320794c58 (diff) | |
| download | pyramid-597a6d7a6cca0865e114359010d3e15f5fb036b1.tar.gz pyramid-597a6d7a6cca0865e114359010d3e15f5fb036b1.tar.bz2 pyramid-597a6d7a6cca0865e114359010d3e15f5fb036b1.zip | |
be more gender-neutral
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/narr/muchadoabouttraversal.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/narr/muchadoabouttraversal.rst b/docs/narr/muchadoabouttraversal.rst index 13d279a42..fcefb9811 100644 --- a/docs/narr/muchadoabouttraversal.rst +++ b/docs/narr/muchadoabouttraversal.rst @@ -151,7 +151,7 @@ what are these nested dictionary things? Where do these objects, these Well, since :app:`Pyramid` is not a highly opinionated framework, there is no restriction on how a resource is implemented; the developer can do -whatever he wants. One common pattern is to persist all of the +whatever they want. One common pattern is to persist all of the resources, including the root, in a database. The root object stores the ids of all of its subresources, and provides a ``__getitem__`` implementation that fetches them. So ``get_root()`` fetches the unique |