diff options
| author | Chris McDonough <chrism@agendaless.com> | 2009-07-03 01:41:04 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@agendaless.com> | 2009-07-03 01:41:04 +0000 |
| commit | 7bc20e11b5ed7314e5aaed000242d4d5950fc775 (patch) | |
| tree | 6cb253ea95617ca4f24aa365f145ec2f81bf53fc /docs/narr/extending.rst | |
| parent | c43c358c7ec7d352fd4792b993e4609cbab37dba (diff) | |
| download | pyramid-7bc20e11b5ed7314e5aaed000242d4d5950fc775.tar.gz pyramid-7bc20e11b5ed7314e5aaed000242d4d5950fc775.tar.bz2 pyramid-7bc20e11b5ed7314e5aaed000242d4d5950fc775.zip | |
General editing walkthrough.
Diffstat (limited to 'docs/narr/extending.rst')
| -rw-r--r-- | docs/narr/extending.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/narr/extending.rst b/docs/narr/extending.rst index cbfaeda6a..128e75b26 100644 --- a/docs/narr/extending.rst +++ b/docs/narr/extending.rst @@ -39,10 +39,10 @@ declarations out of the decorators and into :term:`ZCML`. Once this is done, you should be able to extend or modify the application like any other. -To extend or change the behavior of an existing application, the only -hard-and-fast rule is that you need to write some :term:`ZCML`, and -perhaps some implementations of the types of things you'd like to -override (such as views), which is referred to within that ZCML. +To extend or change the behavior of an existing application, you will +need to write some :term:`ZCML`, and perhaps some implementations of +the types of things you'd like to override (such as views), which are +referred to within that ZCML. The general pattern for extending an application looks something like this: |
