Edit & Typos (ERC-1328) (#1371)

* fix typo author header

* Update eip-1328.md

* change sessionId capitalization

EIPS/eip-1328.md

@@ -1,7 +1,7 @@
 ---
 eip: 1328
 title: WalletConnect Standard URI Format
-authors: ligi <ligi@ligi.de>, Pedro Gomes <pedrouid@protonmail.com>
+author: ligi <ligi@ligi.de>, Pedro Gomes <pedrouid@protonmail.com>
 type: Standards Track
 category: ERC
 status: Draft
@@ -24,8 +24,8 @@ This standard defines how the data to connect some application and a wallet can
 
 Function call URIs follow the ERC-831 URI format, with the following parameters:
 
-    request       = "ethereum" ":" [ "wc-" ]sessionID [ "@" version ][ "?" parameters ]
-    sessionID     = STRING
+    request       = "ethereum" ":" [ "wc-" ]sessionId [ "@" version ][ "?" parameters ]
+    sessionId     = STRING
     version       = 1*DIGIT
     parameters    = parameter *( "&" parameter )
     parameter     = key "=" value
@@ -36,6 +36,12 @@ Function call URIs follow the ERC-831 URI format, with the following parameters:
 
 Required parameters are dependent on the WalletConnect standard version which currently is specified to only include mobile-to-desktop connection sessions which only require `name` which describes the dapp name, `bridge` which includes the bridge URL, `symKey` which includes the symmetric key in base64.
 
+### Example
+
+```
+ethereum:wc-8a5e5bdc-a0e4-4702-ba63-8f1a5655744f@1?name=DappExample&bridge=https://bridge.example.com&symKey=KzpSTk1pezg5eTJRNmhWJmoxdFo6UDk2WlhaOyQ5N0U=
+```
+
 ## Rationale
 
 The need for this ERC stems from the discussion to move away from JSON format used in current beta version of the WalletConnect standard which makes for very inneficient parsing of the intent of the QR code, making it easier to create better QR code parsers APIs for Wallets to implement for other compatible EIPs using the ERC-831 URI format for Ethereum. Also by using a URI instead of a JSON inside the QR-Code the Android Intent system can be leveraged.