Revert of Blimp: add support for SSL connections.

blimp/docs/running.md

Index: blimp/docs/running.md
diff --git a/blimp/docs/running.md b/blimp/docs/running.md
index 8accd3ee93290bbe5b39b48948c8242b50662bd3..a32b4366a27b2f2dd16c01f05dc01269e5e7d934 100644
--- a/blimp/docs/running.md
+++ b/blimp/docs/running.md
@@ -21,15 +21,10 @@
 ./build/android/adb_blimp_command_line --your-flag-here
 ```
 
-To have the client connect to a custom engine use the `--engine-ip`,
-`--engine-port`, and `--engine-transport` flags. The possible valid
-values for `--engine-transport` are 'tcp' and 'ssl'.
-An example valid endpoint would be
-`--engine-ip=127.0.0.1 --engine-port=1234 --engine-transport=tcp`.
-
-SSL-encrypted connections take an additional flag
-`--engine-cert-path` which specifies a path to a PEM-encoded certificate
-file (e.g. `--engine-cert-path=/path/to/file.pem`.)
+To have the client connect to a custom engine use the `--blimplet-endpoint`
+flag.  This takes values in the form of scheme:ip:port.  The possible valid
+schemes are 'tcp', 'quic', and 'ssl'.  An example valid endpoint would be
+`--blimplet-endpoint=tcp:127.0.0.1:25467`.
 
 To see your current command line, run `adb_blimp_command_line` without any
 arguments.