[ http://issues.apache.org/jira/browse/DERBY-1398?page=all ]

Rick Hillegas updated DERBY-1398:
---------------------------------

    Attachment: bug1398_miscDoc_01.diff

Attaching bug1398_miscDoc_01.diff, corrections to the miscellaneous 
copy-editting issues listed here. Touches the following files:

M      src\workingwithderby\cwwdsummary.dita
M      src\adminguide\cadminov38650.dita
M      src\adminguide\cadminappsclientdiffs.dita
M      src\adminguide\tadminapps811302.dita
M      src\adminguide\cadminapps811478.dita
M      src\devguide\cdevspecial49460.dita
M      src\devguide\tdevupgradesoft.dita
M      src\devguide\cdevdvlp14839.dita
M      src\devguide\cdevspecial13670.dita
M      src\ref\crefmpref23947.dita
M      src\ref\rrefjdbc96386.dita
M      src\ref\crefjavbclobnot.dita
M      src\getstart\cgsinstallingderby.dita

I've built the these changes into the html versions of the Working With Derby 
Guide, Admin Guide, Developer's Guide, Reference Guide, and Getting Started 
Guide. They look good.

> Miscellaneous copy-editting problems in the user guides
> -------------------------------------------------------
>
>          Key: DERBY-1398
>          URL: http://issues.apache.org/jira/browse/DERBY-1398
>      Project: Derby
>         Type: Bug

>   Components: Documentation
>     Versions: 10.2.0.0
>     Reporter: Rick Hillegas
>     Assignee: Rick Hillegas
>      Fix For: 10.2.0.0
>  Attachments: bug1398_miscDoc_01.diff
>
> We should clean up these copy-editting problems:
> Admin Guide
>   Update Copyrights in all docs
>   Part One...About this guide and the Network Server documentation
>     "and and" -> "and"
>   Part One...Accessing the Network Server by using the network client driver
>     retrieveMessageText: Is this synchronization cruft:
>       "...or when starting new units of work.
>   Part One...XA and the Network Server
>     We should say that the Derby Network Client is an example
>       of a compliant DRDA client which you can use for distributed
>       transactions.
>   Part One...Using the Derby ij tool with the Network Server
>     Do you really need the DRIVER command? Doesn't ij figure this
>       out by itself?
>   Part One...Differences between the embedded client and the network client 
> driver
>     These differences between network and embedded clients may need
>       revisiting:
>     * There are no localized error messages for the network client.
>     * The network client driver fully materializes LOBS when retrieving a row.
>     * To use an encrypted user id and password, you need to have the IBM's 
> Java Cryptography Extension (JCE) Version 1.2.1 or later.
> Developer's Guide
>   Upgrade
>     Soft Upgrade
>       Soft upgrade allows you TO ...
>   Application development overview
>     last sentence "to serve AS..."
>   Derby server-side programming
>     Programming trigger actions
>       Examples of trigger actions
>         insert space between "the" and "flight_history"
>       Triggers and exceptions
>         "before to the statement" -> "before the statement"
> Getting Started Guide
>   Installing and working with Derby
>     Installing Derby
>       "This downloads page includes provides" ->
>       "This downloads page provides"
> Reference Guide
>   About this guide
>     How this guide is organized
>       "Information about Derby's implementation of the JDBC interface include"
>         ->
>       "Information about Derby's implementation of the JDBC interface, 
> including"
>   JDBC Reference
>     java.sql.Blob and java.sql.Clob
>       I don't know what the following phrase means: "SQL extension over SQL"
>       Notes
>         "on the same column so could result"
>         ->
>         "on the same column could result"
> Working With Derby Guide
>   What next with Derby
>     "as your next step in leaning about"
>     ->
>     "as your next step in learning about"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to