openstack
/
openstack-manuals
Code Issues Proposed changes

Fix typos 

Trivial fix
speciality -> specialty
can't -> cannot
it's -> it is
These changes are in accordance to the
contributor-guide which guides to use standard
U.S. English and to avoid using contractions

Change-Id: Icf5616cbe012f166630befab796377ec9b3b9d5e
This commit is contained in:
Nisha Yadav 2017-06-10 00:22:30 +05:30
parent ea55880fc0
commit 688ae19624
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/contributor-guide/source/blueprints-and-specs.rst
View File

@ -12,7 +12,7 @@ The Documentation team uses specifications in the `docs-specs repository
changes. Approved specifications are published at `Documentation Program
Specifications <https://specs.openstack.org/openstack/docs-specs>`_.
For tracking purposes, a blueprint is created for each specification. It is
also good practice to contact the speciality team for the book you want to
also good practice to contact the specialty team for the book you want to
change to discuss your changes before starting work.
Use blueprints and specifications:

6
doc/contributor-guide/source/release/taskdetail.rst
View File

@ -24,8 +24,8 @@ As soon as pre-release packages are available, you can start testing. Testers
should look at the current draft version of the document, and attempt to
run each command on the pre-release package. If you are able to run the
instructions in the book successfully, then place a green tick in the
matrix, noting which version you tested against. If a command can't be run,
and it's confirmed to be a bug in the documentation, add a note in the
matrix, noting which version you tested against. If a command cannot be run,
and it is confirmed to be a bug in the documentation, add a note in the
`Issues` section, so that the book can be updated.
.. note::
@ -56,7 +56,7 @@ However, we do need to write release notes for our documentation. Release
notes should be added as major changes occur throughout the release, however
this is often overlooked - both by authors and reviewers - and thus a final
review is needed to check that all major changes are in. Contact each
Speciality Team lead, listed at :doc:`../team-structure`, and ask them for
Specialty Team lead, listed at :doc:`../team-structure`, and ask them for
the notes for the books they look after. The source repository for release
notes is `openstack-manuals/releasenotes/source/RELEASENAME` and they are
published to