From ed67ce527d8109140fbd79b8b7df2e774a62a489 Mon Sep 17 00:00:00 2001 From: John Knox Date: Mon, 13 Aug 2018 03:53:03 -0700 Subject: [PATCH] Docs corrections in establishing-a-connection (#220) Summary: The title gets taken from the header, so is duplicated. Pull Request resolved: https://github.com/facebook/flipper/pull/220 Reviewed By: passy Differential Revision: D9244730 Pulled By: jknoxville fbshipit-source-id: d4701cb4af6f551a35cfa02c9ff43aef495f1da0 --- docs/establishing-a-connection.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/establishing-a-connection.md b/docs/establishing-a-connection.md index 09864d6c2..d905de0e4 100644 --- a/docs/establishing-a-connection.md +++ b/docs/establishing-a-connection.md @@ -4,8 +4,6 @@ title: Establishing a connection sidebar_label: Establishing a connection --- -# Establishing a Connection - Below is an outline of how a connection is established between an app with with our SDK integrated, and the desktop app. This all goes on behind the scenes inside the mobile SDK, so users shouldn't need to worry about it. ## Transport Protocol @@ -20,7 +18,7 @@ Any mobile app with the Flipper SDK installed will continually attempt to connec ## Certificate Exchange To avoid mobile apps from connecting to untrusted ports on localhost, they will only connect to servers that have a valid, trusted TLS certificate. -In order for the mobile app to know which certificates it can trust, it conducts a certificate exchange with the desktop app before making it can make its first secure connection. +In order for the mobile app to know which certificates it can trust, it conducts a certificate exchange with the desktop app before it can make its first secure connection. This is achieved through the following steps: * Desktop app starts an insecure server on port 8089.