commit-IssueArticle.css, there is a typo. #9 #35
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
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.
Pull Request Description: Fix Typo in Article.css (#9)
Dear Reviewers,
I hope this message finds you well. I am submitting this pull request to address a minor typographical error identified in the Article.css file. Specifically, in line 58, there exists an inconsistency where the 'line-height' property is set to '25p' instead of the intended '25px'.
This typo may seem trivial, but ensuring code consistency and accuracy is crucial for maintaining code quality and readability. By rectifying this error, we ensure that future developers working on this codebase can accurately interpret and maintain the styling of articles within our project.
To rectify this issue, I have simply amended the value of the 'line-height property' to '25px', aligning it with the established conventions and ensuring conformity with best practices.
I have thoroughly tested this change locally to ensure that it does not introduce any unintended side effects or disruptions to existing functionality. Additionally, I have ensured that the code remains consistent with the surrounding style and adheres to the project's coding guidelines.
Thank you for considering this pull request. I welcome any feedback or suggestions for further improvement. Your time and attention to this matter are greatly appreciated.
Warm regards,
Kartikeydheer Srivastava
[Kartikey1306]