fix upload video demo

README.md

@@ -7,9 +7,9 @@ Built on top of the [Hypercore protocol](https://hypercore-protocol.org/) with e
 
 ## Demos
 <p align="center">
-  <img alt="Uploading Files" src="assets/upload-demo.gif" width="45%">
-&nbsp; &nbsp; &nbsp; &nbsp;
-  <img alt="Downloading Files" src="assets/download-demo.gif" width="45%">
+  <img alt="Uploading Files" src="assets/upload-demo.gif" width="50%">
+&nbsp; &nbsp;
+  <img alt="Downloading Files" src="assets/download-demo.gif" width="50%">
 </p>
 
 ## Installation
@@ -40,7 +40,9 @@ $ portal join [sessionID]
 Portal relies on a publish-subscribe event model to drive its render and update cycles. File tree structure and individual file statuses are stored in a trie structure known as the Registry. On the host side, there is a local Registry that listens to file changes on the host machine and broadcasts them to an append-only [Hypercore](https://hypercore-protocol.org/protocol/#hypercore) that is used as an event log. A drive syncing hook listens for changes in the local registry and streams file changes from disk to a [Hyperdrive](https://hypercore-protocol.org/protocol/#hyperdrive). On the client side, a remote Registry listens for changes in the event log and replicates changes locally. A drive download hook listens for changes in the remote registry and streams file changes from the Hyperdrive to the local disk.
 
 ### Connection
-Portals are identified by unique* (1/1.1579x10^77 chance of collision) 32-byte keys. When a client 'joins' a portal, `portal` looks up the session key using [Hyperswarm](https://hypercore-protocol.org/protocol/#hyperswarm) and establishes a connection to the host using UDP holepunching.
+Portals are identified by unique* 32-byte keys. When a client 'joins' a portal, `portal` looks up the session key using [Hyperswarm](https://hypercore-protocol.org/protocol/#hyperswarm) and establishes a connection to the host using UDP holepunching.
+
+*8.63x10<sup>-78</sup> chance of collision
 
 ### How is this different from Dat?
 Might seem similar to another similar project built on top of the Hypercore protocol called [Dat](https://github.com/datproject/dat) but there are a few key differences.