modify some misspellings
Change-Id: I5ae626be2a2db6b56dd73328748e7d13006f6961
This commit is contained in:
parent
1f6bd25257
commit
ea29aa4b71
|
@ -127,7 +127,7 @@ Implementation
|
|||
Work Items
|
||||
----------
|
||||
|
||||
#. Create a seperate wiki page to keep all the related details on the
|
||||
#. Create a separate wiki page to keep all the related details on the
|
||||
project.
|
||||
|
||||
#. Work out the detailed and well-structured table of contents (on wiki).
|
||||
|
|
|
@ -59,7 +59,7 @@ PDF build support in Sphinx configurations.
|
|||
Alternatives
|
||||
------------
|
||||
|
||||
* Building PDFs seperately (without using current Sphinx build scripts)
|
||||
* Building PDFs separately (without using current Sphinx build scripts)
|
||||
can be an alternative. However, this result will decrease the manageability
|
||||
of build scripts in documentation repositories.
|
||||
|
||||
|
|
|
@ -26,7 +26,7 @@ to expect the documentation team to maintain the administrator guide for all
|
|||
of these projects. We need to optimize the usage of the documentation teams
|
||||
resources.
|
||||
|
||||
Currently the administrator guide is in a seperate git repository from the
|
||||
Currently the administrator guide is in a separate git repository from the
|
||||
code and patches being proposed. This leads to an "out of site, out of mind"
|
||||
scenario where updates to the administrator guide are an afterthought if they
|
||||
get updated at all.
|
||||
|
|
Loading…
Reference in New Issue