Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exchange trac with GitHub, unify wording #197

Merged
merged 1 commit into from
Mar 17, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/plipreview.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Expectations
============
A good PLIP review takes about 4 hours so please plan accordingly.
When you are done,
if you have access to core please commit the review to the plips folder and reference the PLIP in your commit message.
if you have access to core please commit the review to the PLIPSs folder and reference the PLIP in your commit message.
If you do not have access,
please attach your review to the PLIP ticket itself.

Expand All @@ -17,7 +17,7 @@ Setting up the environment
Follow the instructions on :ref:`setup-development-environment`.
You will need to checkout the branch to which the PLIP is assigned.
Instead of running the buildout with the default buildout file,
you will run the config specific to that plip::
you will run the config specific to that PLIP::

> ./bin/buildout -c plips/plipXXXX.cfg

Expand Down Expand Up @@ -71,7 +71,7 @@ Documentation Issues
sufficient?
* Is the change itself properly documented?

Please report bugs/issues in Trac as you would for any Plone bug.
Please report bugs/issues on GitHub as you would for any Plone bug.
Reference the PLIP in the bug,
assign to its implementer,
and add a tag for the PLIP in the form of plip-xxx.
Expand Down