use initial-caps version of Dexterity and Archetypes names by convention (per @zupo)

This commit is contained in:
cewing 2013-10-09 12:44:59 -07:00 committed by Nejc Zupan
parent dbcd69c887
commit af5b91b0e9
2 changed files with 3 additions and 3 deletions

View File

@ -26,8 +26,8 @@ portal object, it will serve nicely:
portal = api.portal.get()
Create your new content item using the :meth:`api.content.create` method. The
type argument will decide which content type will be created. Both dexterity
and archetype content types are supported.
type argument will decide which content type will be created. Both Dexterity
and Archetypes content types are supported.
.. code-block:: python

View File

@ -297,7 +297,7 @@ Declaring dependencies
All direct dependencies should be declared in ``install_requires`` or
``extras_require`` sections in ``setup.py``. Dependencies, which are not needed for
a production environment (like "develop" or "test" dependencies) or are
optional (like "archetypes" or "dexterity" flavors of the same package) should
optional (like "Archetypes" or "Dexterity" flavors of the same package) should
go in ``extras_require``. Remember to document how to enable specific features
(and think of using ``zcml:condition`` statements, if you have such optional
features).