openerp-doc team mailing list archive
-
openerp-doc team
-
Mailing list archive
-
Message #00287
doc.openerp.com: success when building v6.0 doc.
The documentation was built successfully.
------------------------------------------------------------
revno: 1159
committer: John Bradshaw <john@xxxxxxxxxxxxxxxx>
branch nick: 6.0
timestamp: Sun 2011-06-19 23:09:30 +0100
message:
[IMP] Grammar
- Gathering data was very time and money consuming in the past, but with today?s modern computer systems
+ Previously gathering data was costly and time consuming, but with modern computer systems
- Our goal of OpenObject BI is to provide python based BI Solution that can
+ Our goal of OpenObject BI is to provide Python based BI solution that can :
- #. Can access any type of database to make Schema and Cube.
+ #. Access any type of database to make Schema and Cube.
------------------------------------------------------------
revno: 1158
committer: John Bradshaw <john@xxxxxxxxxxxxxxxx>
branch nick: 6.0
timestamp: Sun 2011-06-19 22:45:53 +0100
message:
[IMP] Grammar coding_guidelines_framework.rst
-Give your variables a meaningful name all the time.
+Always give your variables a meaningful name.
------------------------------------------------------------
revno: 1157
committer: John Bradshaw <john@xxxxxxxxxxxxxxxx>
branch nick: 6.0
timestamp: Sun 2011-06-19 22:27:14 +0100
message:
[IMP] Grammar
- This list is populated incrementally as part of the
code review process done by the OpenERP Quality Team.
+ This list is populated incrementally by the OpenERP
Quality Team as part of the code review process.
------------------------------------------------------------
revno: 1156
committer: John Bradshaw <john@xxxxxxxxxxxxxxxx>
branch nick: 6.0
timestamp: Sun 2011-06-19 22:12:52 +0100
message:
[IMP] Grammar and readability
15_guidelines/index.rst
1. must absolutely read it -> must absolutely read it
2. in order to participate actively in maintaining a high level -> in order to maintain the high level
3. to periodically come refresh their -> to periodically refresh their
4. everyone is of course invited to refer -> everyone is invited to refer
5. missing in the list -> missing from the list
------------------------------------------------------------
revno: 1155
committer: John Bradshaw <john@xxxxxxxxxxxxxxxx>
branch nick: 6.0
timestamp: Fri 2011-06-17 16:55:54 +0100
message:
[IMP] Grammar
communication canal -> communication channel
according mailing list -> associated mailing list
------------------------------------------------------------
revno: 1154
committer: John Bradshaw <john@xxxxxxxxxxxxxxxx>
branch nick: 6.0
timestamp: Fri 2011-06-17 15:57:44 +0100
message:
[IMP] 11_bug_tracker.rst
Remove reference to now-closed Launchpad bug 438116.
Closure confirmed with Olivier Dony (OpenERP)
------------------------------------------------------------
revno: 1153
committer: John Bradshaw <john@xxxxxxxxxxxxxxxx>
branch nick: 6.0
timestamp: Fri 2011-06-17 15:45:13 +0100
message:
[IMP] Readability 09_documentation_translation.rst
1. sections will hopefully keep their -> sections should keep their
2. understand the section in its context -> understand the section in context
3. When you will get the documentation -> When you get the documentation
------------------------------------------------------------
revno: 1152
committer: John Bradshaw <john@xxxxxxxxxxxxxxxx>
branch nick: 6.0
timestamp: Fri 2011-06-17 14:37:18 +0100
message:
[IMP] Grammar 07_improving_translations.rst
is greatly recommended -> is strongly recommended
------------------------------------------------------------
revno: 1151
committer: John Bradshaw <john@xxxxxxxxxxxxxxxx>
branch nick: 6.0
timestamp: Fri 2011-06-17 13:55:34 +0100
message:
[IMP] Grammar translations.rst
and is outline in the -> and is outlinedin the
------------------------------------------------------------
revno: 1150
committer: John Bradshaw <john@xxxxxxxxxxxxxxxx>
branch nick: 6.0
timestamp: Fri 2011-06-17 13:51:39 +0100
message:
[IMP] Grammar 08_documentation_process.rst
1. Remove partial sentence "As to motivate people to write quality documentation,"
2. Everyone can be an author -> Anyone can be an author
3. provide a very good documentation -> provide very good documentation
4. to pay every contributor -> to pay each contributor
5. This section describe how -> This section describes how
6. Valid until the employee work for Tiny -> Valid while the employee works for Tiny
7. We have contract with several editors -> We have contracts with several editors