Document telepresence sshfs problems on macOS

README.md

@@ -87,6 +87,9 @@ You need to do this once for every development machine you're using
   volumes from the kubernetes cluster, in particular the one with the service
   account token (credentials for calling the kubernetes api), to let the
   dashboard interact with the cluster.
+  - MacOS users may have to do a little extra work to get a working current
+    sshfs: see [telepresence
+    docs](https://www.getambassador.io/docs/telepresence-oss/latest/troubleshooting#volume-mounts-are-not-working-on-macos).
 * Download and install the telepresence binary on your development machine:
   https://www.getambassador.io/docs/telepresence-oss/latest/install
 
@@ -141,7 +144,7 @@ natively and the backend in docker at the same time, or vice versa.
   could work around this by using a fully qualified domain name for the
   database service -- which doesn't agree with the goal of making the stackspin
   namespace variable -- or using the service env vars, but we're hoping that
-  telepresence with fix this in time.
+  telepresence will fix this in time.
 * Telepresence intercepts traffic to a pod, but the original pod is still
   running. In case of the backend, this is sometimes problematic, for example
   when you're adding database migrations which the original pod then doesn't