Update README following publication of report

README.md

@@ -3,7 +3,7 @@ publishing a software release under a proprietary license initially,
 then later (usually in a planned fashion) publishing that release's
 source code under an open source license.
 
-While delayed open source publication been somewhat rare, there are
+While delayed open source publication has been somewhat rare, there are
 some examples of it across the history of open source -- in fact, some
 of the examples (e.g., Aladdin Ghostscript) predate the coining of the
 term "open source".  To the best of our knowledge, when software
@@ -12,31 +12,31 @@ way.  For example, when release N goes out under a proprietary
 license, release N-1 is then (re)published under an open source
 license.
 
-This repository is a collection of research, and eventually a
-whitepaper, about various examples of DOSP and show how they are alike
-or different.  We will also analyze the effects (if any) of this
-practice generally on open source as a field.  Our purpose is to
-provide accurate historical description and objective analysis; our
-work here represents no position on the desirability or undesirability
-of delayed open source publication.
+This repository is a collection of research, and a resultant
+[whitepaper](https://opensource.org/delayed-open-source-publication),
+about various examples of DOSP and show how they are alike or
+different.  We also analyze the effects (if any) of this practice
+generally on open source as a field.  Our purpose is to provide
+accurate historical description and objective analysis; our work here
+represents no position on the desirability or undesirability of
+delayed open source publication.
 
-This research is supported by the [Open Source Initiative
-(OSI)](https://opensource.org/).
+This research was supported by the [Open Source Initiative
+(OSI)](https://opensource.org/).  The report is now completed and
+published at
+[opensource.org/delayed-open-source-publication](https://opensource.org/delayed-open-source-publication).
 
-## Terminology
-
-We are not necessarily settled on the term "delayed open source
-publication".  If you can suggest a better term for the phenomenon,
-please let us know.
-
-## Contributing
+## Contacting us
 
 You can email us at `dosp-research {_AT_} opensource.org` or [file a
 ticket](https://code.librehq.com/ots/dosp-research/-/issues/new) to
-contact us.
+contact us.  While we occasionally indulge in light maintenance and
+error correction in the LaTeX source, that's infrequent and done
+entirely at our discretion.  We may prepare an updated second edition
+some day; if you're interested in being involved in that, please let
+us know.
+
+## Building the whitepaper PDF from LaTeX source
 
-To build the whitepaper from LaTeX source, you will need to use [OTS
-DocTools](https://code.librehq.com/ots/ots-doctools).  ***Note that
-the whitepaper is still a work in progress.  Please do not cite the
-draft nor quote from it in public forums yet.***  We'll remove
-this notice when the paper is ready for publication.
+To build the whitepaper from LaTeX source, use [OTS
+DocTools](https://code.librehq.com/ots/ots-doctools).