blog: typo fix

website/src/_posts/2019-10-1.5.md

@@ -117,7 +117,7 @@ Once these new providers been tested for a while, we'll release them as 1.0 and
 
 ## Revoke Companion’s Provider access on logout
 
-Up until now, when users clicked “logout” after using a remote Provider, such as Google Drive or Dropbox, Uppy would destroy the access token. But on the Provider’s side, Uppy was still allowed access. Should the user click “Connect to Google Dtive” again, no extra confirmation was required.
+Up until now, when users clicked “logout” after using a remote Provider, such as Google Drive or Dropbox, Uppy would destroy the access token. But on the Provider’s side, Uppy was still allowed access. Should the user click “Connect to Google Drive” again, no extra confirmation was required.
 
 After a discussion in [#1563](https://github.com/transloadit/uppy/issues/1563), we are expanding the logout process. Now when users logout from Google Drive, Instagram, etc, in Uppy, Companion will destroy the token as before, but additionally attempt to revoke the access from the corresponding Provider. In the event that the Provider doesn’t support access revoke via it’s API, Uppy will display a helpful message about how users can revoke the permissions manually.