Fixed issues reported in PR comments.
@@ -55,39 +55,39 @@ The primary motivation is to create a simple, human-readable, and scalable way t
Deep links are the URIs with hierarchical components sequence. We can use this sequence to pass and handle data in a standardized and predictable way. To do that, we need to pass three components to the target client:
-#### Scheme
+### Scheme
The scheme is used to address the client, which will handle the data from the command and data component. In the Tari Aurora project, we're using `tari` scheme to open the wallet app and handle provided data.
-#### Command
-The command and path string is used to pass information about the action that should be performed by the client. The handler can use this info to determine which parser/decoder should be used to serialize data and what the app suppose to do with the data afterwards.
+### Command
+The command is path string used to pass information about the action that should be performed by the client. The handler can use this info to determine which parser/decoder should be used to deserialize data and what the app suppose to do with the data afterwards.
To support multiple domains/networks the first path component should contain a name of corresponded domain/network. The app before handle the data should first check that active account is pointed to the right domain/network and show the error is there a missmatch.
For simple actions, the command can be defined as a single phrase. For more complex actions, the command should be defined as a multi-path where the second path component should be the name of the action group.
-**Examples**:
+#### Examples:
Simple Actions:
-```
+```ignore
mainnet/user_profile
testnet/login
```
Complex Actions:
-```
-mainnet/payment/send
+```ignore
+mainnet/payments/send
testnet/payments/request
```
-#### Data
-The data component is an optional string of key-value pairs used by the parser/decoder to serialize the data, which the client will later use to handle the action. The data component should be formatted in the same way as a URL query. The sub-component should have a `?` prefix, the key-value pairs should be separated by `&`, and every key should be separated from the value by `=` character.
+### Data
+The data component is an optional string of key-value pairs used by the parser/decoder to deserialize the data, which the client will later use to handle the action. The data component should be formatted in the same way as a URL query. The sub-component should have a `?` prefix, the key-value pairs should be separated by `&`, and every key should be separated from the value by `=` character.
-#### The Structure
+### The Structure
Combining all three components, they will form a deep link with a structure presented below:
-```
+```ignore
{scheme}://{command}?{data}
```
-**Examples**:
-```
+#### Examples:
+```ignore
tari://mainnet/profile
tari://mainnet/profile/username
-tari://testnet/payment/send?amount=1.23&pubKey=01234556789abcde
+tari://testnet/payments/send?amount=1.23&pubKey=01234556789abcde
```
\ No newline at end of file
