From 352e7e3a0138715f844197624074e33d5599c67e Mon Sep 17 00:00:00 2001 From: Alex Dickson Date: Wed, 18 Aug 2021 02:16:22 -0700 Subject: [PATCH] Edit establishing-a-connection.mdx using inpage editor Summary: This diff has been automatically generated by the inpage editor. If you want to update this diff, go through the preview link that would be attached to the test plan. Please ensure you are editing the same page that was used to create this diff. Reviewed By: jknoxville Differential Revision: D30392627 fbshipit-source-id: b7040f0ccb338d78c92186bf3a910d9ffbeb8019 --- docs/extending/establishing-a-connection.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extending/establishing-a-connection.mdx b/docs/extending/establishing-a-connection.mdx index 864dcb1bf..58d299216 100644 --- a/docs/extending/establishing-a-connection.mdx +++ b/docs/extending/establishing-a-connection.mdx @@ -26,7 +26,7 @@ In order for the mobile app to know which certificates it can trust, it conducts This is achieved through the following steps: * Desktop app starts an insecure server on port 8089. * Mobile app connects to localhost:8089 and sends a Certificate Signing Request to the desktop app. -* Desktop app uses it's private key (this is generated once and stored in ~/.flipper) to sign a client certificate for the mobile app. +* Desktop app uses its private key (this is generated once and stored in ~/.flipper) to sign a client certificate for the mobile app. * Along with the Certificate Signing Request, mobile app also lets the desktop app know which certificate exchange medium to use. * If the chosen Certificate Exchange Medium is FS_ACCESS, the desktop uses ADB (for Android), or the mounted file system (for iOS simulators) to write the following files to the mobile app's private data partition * Server certificate that the mobile app can now trust.