diff options
| author | Min ho Kim <minho42@gmail.com> | 2019-07-27 01:11:04 +1000 |
|---|---|---|
| committer | Min ho Kim <minho42@gmail.com> | 2019-07-27 01:11:04 +1000 |
| commit | a85a83b631ac6ff8653a9c35cd089c7889753ea3 (patch) | |
| tree | 0321399b4b04efdc1f6031af25d8c056fd4724d9 /docs/narr/advanced-features.rst | |
| parent | d32e4775e6da03720a9d3b239efeec956101e954 (diff) | |
| download | pyramid-a85a83b631ac6ff8653a9c35cd089c7889753ea3.tar.gz pyramid-a85a83b631ac6ff8653a9c35cd089c7889753ea3.tar.bz2 pyramid-a85a83b631ac6ff8653a9c35cd089c7889753ea3.zip | |
Fix typos
Diffstat (limited to 'docs/narr/advanced-features.rst')
| -rw-r--r-- | docs/narr/advanced-features.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/narr/advanced-features.rst b/docs/narr/advanced-features.rst index b169aad95..b24208bc4 100644 --- a/docs/narr/advanced-features.rst +++ b/docs/narr/advanced-features.rst @@ -84,7 +84,7 @@ Speaking of the :app:`Pyramid` structured :meth:`~pyramid.config.Configurator.in If you need, you can extend or override the configuration of an existing application by including its configuration in your own and then modifying it. -For example, if you want to reuse an existing application that already has a bunch of routes, you can just use the ``include`` statement with a ``route_prefix``. All the routes of that application will be availabe, prefixed as you requested: +For example, if you want to reuse an existing application that already has a bunch of routes, you can just use the ``include`` statement with a ``route_prefix``. All the routes of that application will be available, prefixed as you requested: .. code-block:: python :linenos: @@ -115,7 +115,7 @@ In addition, the system that handles authentication and authorization is flexibl Build Trees of Resources ------------------------ -:app:`Pyramid` supports :term:`traversal`, a way of mapping URLs to a concrete :term:`resource tree`. If your application naturally consists of an arbitrary heirarchy of different types of content (like a CMS or a Document Management System), traversal is for you. If you have a requirement for a highly granular security model ("Jane can edit documents in *this* folder, but not *that* one"), traversal can be a powerful approach. +:app:`Pyramid` supports :term:`traversal`, a way of mapping URLs to a concrete :term:`resource tree`. If your application naturally consists of an arbitrary hierarchy of different types of content (like a CMS or a Document Management System), traversal is for you. If you have a requirement for a highly granular security model ("Jane can edit documents in *this* folder, but not *that* one"), traversal can be a powerful approach. .. seealso:: |