Syncing docs. (#943)

Small updates to sysdig man page/readme with recent changes.

README.md

@@ -90,7 +90,7 @@ Use a real name of a natural person who is an authorized representative of the c
 
 Sysdig Cloud
 ---
-Interested in a fully supported, fully distributed version of sysdig? Check out [Sysdig Cloud](https://sysdig.com/)!
+Interested in a fully supported, fully distributed version of sysdig? Check out [Sysdig Monitor](https://sysdig.com/product)!
 
 Open source sysdig is proudly supported by [Sysdig Inc](https://sysdig.com/company/).  
 

userspace/sysdig/man/sysdig.md

@@ -111,7 +111,7 @@ OPTIONS
   Make the given filter a display one. Setting this option causes the events to be filtered after being parsed by the state system. Events are normally filtered before being analyzed, which is more efficient, but can cause state (e.g. FD names) to be lost.
 
 **-D**, **--debug**
-  Capture events about sysdig itself and print additional logging on standard error.
+  Capture events about sysdig itself, display internal events in addition to system events, and print additional logging on standard error.
 
 **-E**, **--exclude-users**
   Don't create the user/group tables by querying the OS when sysdig starts. This also means that no user or group info will be written to the tracefile by the **-w** flag. The user/group tables are necessary to use filter fields like user.name or group.name. However, creating them can increase sysdig's startup time. Moreover, they contain information that could be privacy sensitive.
@@ -153,6 +153,9 @@ OPTIONS
 **-l**, **--list**
   List the fields that can be used for filtering and output formatting. Use -lv to get additional information for each field.
 
+**--list-markdown**
+  Like -l, but produces markdown output
+
 **-m** _url[,marathon-url]_, **--mesos-api=**_url[,marathon-url]_
   Enable Mesos support by connecting to the API server specified as argument (e.g. http://admin:[email protected]:5050). Mesos url is required. Marathon url is optional, defaulting to auto-follow - if Marathon API server is not provided, sysdig will attempt to retrieve (and subsequently follow, if it migrates) the location of Marathon API server from the Mesos master. Note that, with auto-follow, sysdig will likely receive a cluster internal IP address for Marathon API server, so running sysdig with Marathon auto-follow from a node that is not part of Mesos cluster may not work. Additionally, running sysdig with Mesos support on a node that has no containers managed by Mesos is of limited use because, although cluster metadata will be collected, there will be no Mesos/Marathon filtering capability. The API servers can also be specified via the environment variable SYSDIG_MESOS_API.