add some note about logging configuration (#609)

* add some note about logging configuration

* use {note}

* Minor adjustments

---------

Co-authored-by: Hynek Schlawack <[email protected]>

docs/standard-library.md

@@ -144,6 +144,15 @@ The most straight-forward option is to configure standard library `logging` clos
 Since these are usually log entries from third parties that don't take advantage of *structlog*'s features, this is surprisingly often a perfectly adequate approach.
 
 For instance, if you log JSON in production, configure `logging` to use [*python-json-logger*] to make it print JSON too, and then tweak the configuration to match their outputs.
+You can also use {class}`~structlog.stdlib.ProcessorFormatter` as a formatter for `logging` to get the same output for both *structlog* and `logging` log entries -- see [below](processor-formatter) for an example.
+
+:::{note}
+If you want to use same file (for example, `sys.stdout` or `sys.stderr`) for both *structlog* and `logging.StreamHandler` output, you must use {class}`~structlog.WriteLogger` instead of {class}`~structlog.PrintLogger`.
+
+This is because {class}`~structlog.PrintLogger` uses `print(log, file=file, flush=True)` to write log, and `print` writes the `log` message and a newline ("\n") to the stream separately.
+This can cause interleaving of log entries from *structlog* and `logging` loggers.
+{class}`~structlog.WriteLogger` writes log entries atomically to the file (for example, `file.write(log+"\n")`).
+:::
 
 
 ### Rendering Within *structlog*