(WIP) Express relay docs

Author: aditya520

pages/express-relay/how-express-relay-works/auction.mdx

@@ -16,4 +16,4 @@ The revenue from the auction is shared amongst relevant stakeholders in the Expr
 - the protocol that generated the relevant opportunity
 - the relayer, which handled running the off-chain components of the system
 
-The contract enforces the exact revenue splits in the Express Relay and is subject to change based on governance decisions.
+The Express Relay contract enforces the exact revenue splits and is subject to change based on governance decisions.

pages/express-relay/how-express-relay-works/permissioning.mdx

@@ -1,19 +1,25 @@
 # Permissionin ID
 
-`permissionId` is a `bytes` object that represents the unique identifying information of a position within the protocol. `permissionId` allows the system to distinguish between bids competing on different opportunities and thereby run more scoped and efficient auctions.
+`permissionId` is a `bytes` object that represents the unique identifying information of a position within the protocol. `PermissionId` allows the system to distinguish between bids competing on different opportunities and thereby run more scoped and efficient auctions.
 
-For some protocols, each borrower has a unique position, so the borrower address uniquely identifies a position. For other protocols, each borrower might have multiple positions, distinguished by the address of the collateral asset or by a uint256 id number. In those cases, the set of information that uniquely identifies a position would include multiple fields.
+Each borrower has a unique position for some protocols, so the borrower address uniquely identifies a position. 
+Whereas in some protocols, each borrower might have multiple positions, distinguished by the address of the collateral asset or by a `uint256` ID number. 
+In those cases, the information set that uniquely identifies a position would include multiple fields.
 
-`permissionId` is the concatenation of all these fields in bytes format. To concatenate these fields together, you can call `abi.encode()`. For example, if a protocol featured a unique position per borrower, then it could form `permissionId` as
+`permissionId` is the concatenation of all these fields in bytes format. You can call `abi.encode(){:solidity}` to concatenate these fields together. 
 
-```
+For example, if a protocol featured a unique position per borrower, then it could form `permissionId` as
+
+```solidity
 bytes memory permissionId = abi.encode(borrowerAddress);
 ```
 
-On the other hand, if a protocol allowed a borrower to open as many new positions as they wanted, denoted by an identifier `uint256 positionId`, then it could form permissionId as
 
-```
+On the other hand, if a protocol allowed a borrower to open as many new positions as they wanted, denoted by an identifier `uint256 positionId{:solidity}`, then it could form `permissionId` as
+
+```solidity
 bytes memory permissionId = abi.encode(borrowerAddress, positionId);
 ```
 
-The `permissionId` is used in the `ExpressRelay` contract to toggle permissions for interacting with the protocol. This toggling is checked within the protocol's code to ensure that the current transaction is within the context of Express Relay, so that recaptured value can be returned to the protocol.
+The Express Relay contract uses the `permissionId` to toggle permissions for interacting with the protocol. 
+This toggling is checked within the protocol's code to ensure that the current transaction is within the context of Express Relay so that the recaptured value can be returned to the protocol.