Some documentation edits

pkgs/racket-doc/scribblings/reference/port-lib.scrbl

@@ -30,7 +30,8 @@ on @racket[in] until it produces @racket[eof].
          string?]{
 
 Reads all characters from @racket[in] and returns them as a string.
-The input port is closed unless @racket[close?] is @racket[#f].
+If @racket[close?] is @racket[#t], then the input port is closed,
+otherwise, it is left open.
 
 @examples[#:eval port-eval
 (port->string (open-input-string "hello world"))

pkgs/racket-doc/scribblings/reference/subprocess.scrbl

@@ -112,7 +112,7 @@ explicitly closed, usually with @racket[close-input-port] or
 @racket[close-output-port].
 
 @margin-note{A @tech{file-stream port} for communicating with a
-subprocess is normally a pipe with a limited capacity. Beware of
+subprocess is normally a pipe with a limited buffer capacity. Beware of
 creating deadlock by serializing a write to a subprocess followed by a
 read, while the subprocess does the same, so that both processes end
 up blocking on a write because the other end must first read to make
@@ -167,6 +167,9 @@ Example:
 (subprocess-wait sp)
 ]
 
+@; PLACEHOLDER: maybe explain here that subprocess-wait should be called
+@; after all the I/O to ensure the process is in a position to terminate?
+
 @history[#:changed "6.11.0.1" @elem{Added the @racket[group] argument.}
          #:changed "7.4.0.5" @elem{Added waiting for a fifo without a reader
                                    as @racket[stdout] and/or @racket[stderr].}
@@ -429,6 +432,8 @@ function:
 (with-output-to-string (lambda () (system "date")))
 ]}
 
+@; PLACEHOLDER: add something explaining why system* is recommended instead
+@; (sorawee)
 
 @defproc*[([(system* [command path-string?]
                      [arg (or/c path? string-no-nuls? bytes-no-nuls?)] ...

pkgs/racket-doc/syntax/scribblings/parse/define.scrbl

@@ -51,6 +51,10 @@ Defines a macro named @racket[macro-id]; equivalent to:
   (syntax-parser parse-option ... clause ...))
 ]
 
+This form does not explicitly mention the syntax object being parsed,
+but as in the case of any use of @racket[syntax-parse], you can access
+it via @racket[this-syntax].
+
 @examples[#:eval the-eval
 (define-syntax-parser fn3
   [(fn3 x:id rhs:expr)

pkgs/racket-doc/syntax/scribblings/parse/parsing.scrbl

@@ -207,7 +207,9 @@ Suppresses the ``colon notation'' for annotated pattern variables.
 @defform[(syntax-parser parse-option ... clause ...+)]{
 
 Like @racket[syntax-parse], but produces a matching procedure. The
-procedure accepts a single argument, which should be a syntax object.
+procedure accepts a single argument, which should be a syntax
+object. The syntax object is accessible within the body of the form
+via @racket[this-syntax].
 }
 
 @defform[(define/syntax-parse syntax-pattern pattern-directive ... stx-expr)