forked from tornadocash/classic-ui
41 lines
1.2 KiB
Markdown
41 lines
1.2 KiB
Markdown
|
## Explanation
|
||
|
|
||
|
<!--
|
||
|
Thanks for the pull request. Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes:
|
||
|
* What is the current state of things and why does it need to change?
|
||
|
* What is the solution your changes offer and how does it work?
|
||
|
Below is a template to give you some ideas. Feel free to use your own words!
|
||
|
Currently, ...
|
||
|
This is a problem because ...
|
||
|
In order to solve this problem, this pull request ...
|
||
|
-->
|
||
|
|
||
|
## More information
|
||
|
|
||
|
<!--
|
||
|
Are there any issues, [community forum](https://torn.community/) discussion, user stories, etc. reviewers should consult to understand this pull request better? For instance:
|
||
|
* Fixes #12345
|
||
|
* See: #67890
|
||
|
-->
|
||
|
|
||
|
## Screenshots/Screencaps
|
||
|
|
||
|
<!-- If you're making a change to the UI, make sure to capture a screenshot or a short video showing off your work! -->
|
||
|
|
||
|
### Before
|
||
|
|
||
|
<!-- How did the UI you changed look before your changes? Drag your file(s) below this line: -->
|
||
|
|
||
|
### After
|
||
|
|
||
|
<!-- How does it look now? Drag your file(s) below this line: -->
|
||
|
|
||
|
## Manual testing steps
|
||
|
|
||
|
<!--
|
||
|
How should reviewers and QA manually test your changes? For instance:
|
||
|
- Go to this screen
|
||
|
- Do this
|
||
|
- Then do this
|
||
|
-->
|