Fix a formatting issue with markdown / HTML and correct incorrect link #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update privacy-policy.md because there was a minor formatting inconsistency in my previous typo fixing commit
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While reading the policy I noticed there was an issue where Markdown styling inside of a div for a summary was not being rendered on the website and also on Github. This PR fixes the issue by using HTML styling within said div.
Additionally, it corrects what I presume to be an incorrect link as the summary of Section 12 (Changes and Updates) references this Github repository as the place to view a history of the document but the actual section body references the privacy policy on desmos.com (desmos.com/privacy) which does not have a way to view past revisions. I corrected the link to point to the Github repo as the summary does.
I did not update the last updated date as I was not sure if a minor formatting fix counted as a significant modification, but if Desmos thinks it should be incremented that is fine.