CG: Release work: Clarify location of robots.txt (issue 10759043)

[markpolesky]

Reviewers: ,

Message:
Hey everyone,

just making sure I'm complying with the new patch policies.  Shall I use
`git cl' for every little patch like this?

- Mark

Description:
CG: Release work: Clarify location of robots.txt

Also tidy up some nearby text.

Please review this at https://codereview.appspot.com/10759043/

Affected files:
  M Documentation/contributor/release-work.itexi


Index: Documentation/contributor/release-work.itexi
diff --git a/Documentation/contributor/release-work.itexi  
b/Documentation/contributor/release-work.itexi
index  
5dbc3082540a000a12acbdffc72198b85b31c420..d87b600827124662a4b345535a810494c0dbe81d  
100644
--- a/Documentation/contributor/release-work.itexi
+++ b/Documentation/contributor/release-work.itexi
@@ -351,25 +351,26 @@ Website:

 @itemize
 @item
+
 make a link from the old unstable to the next stable in
-lilypond.org's /doc/ dir.  Keep all previous unstable->stable doc
-symlinks.
+lilypond.org's @file{/doc/} dir.  Keep all previous unstable->stable
+doc symlinks.

 Also, make the old docs self-contained -- if there's a redirect in
-/doc/v2.12/Documentation/index.html , replace it with the
-index.html.old-2.12 files.
address@hidden/doc/v2.12/Documentation/index.html} , replace it with the
address@hidden files.

 The post-2.13 docs will need another way of handling the
 self-containment.  It won't be hard to whip up a python script
-that changes the link to ../../../../manuals.html to
-../website/manuals.html , but it's still a 30-minute task that
+that changes the link to @file{../../../../manuals.html} to
address@hidden/website/manuals.html}, but it's still a 30-minute task that
 needs to be done before 2.16.

 @item
-doc auto redirects  to v2.LATEST-STABLE
+doc auto redirects to @code{v2.LATEST-STABLE}

 @item
-add these two lines to http://www.lilypond.org/robots.txt:
+add these two lines to @file{Documentation/web/server/robots.txt}:

 @example
 Disallow: /doc/v2.PREVIOUS-STABLE/