#30 updates

<!--- Provide a general summary of your changes in the Title above --> <!--- Please do remember to follow the contributing guidelines --> ## Description <!--- Why is this change required? What problem does it solve? --> <!--- Describe your changes in detail here to communicate to the maintainers why this pull request should be accepted --> <!--- Describe your technology stack here if not a documentation update --> <!--- Tasklist format is recommended for all pull requests and is required for all draft pull requests. You can couple your description with the tasklist --> <!--- If it fixes an open issue, please link to the issue here in the last line. --> ## How Has This Been Tested <!--- Please describe in detail how you tested your changes locally --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- For example, markdown files should pass markdownlint locally according to the rules --> <!--- See how your change affects other areas of the code, etc. --> ## Screenshots(optional) <!--- If Screenshots is not necessary or not available in this pull request, you can delete this section --> <!--- Changes including html and css are required to have screenshots --> ## Types of changes <!--- What types of changes does your code introduce? --> <!--- Only left the line that best describes this pull request --> - Bug fix (non-breaking change which fixes an issue) - New feature (non-breaking change which adds functionality) - Documentation (non-breaking change which updates documentation) - Breaking change (fix or feature that would cause existing functionality to change) - Code style (formatting, renaming) - Refactoring (no functional changes, no api changes) - Other (please describe here): ## Checklist <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] Code follows the code style of this project. - [ ] Changes follow the **CONTRIBUTING** guidelines. - [ ] Update necessary documentation accordingly. - [ ] Lint and tests pass locally with the changes. - [ ] Check issues and pull requests first. You don't want to duplicate effort. ## Other information