Skip to content

Premium page correct image placement#67

Closed
Kaiyumari15 wants to merge 3 commits into
MoonlightCapital:testingfrom
Kaiyumari15:premium-page-correct-image-placement
Closed

Premium page correct image placement#67
Kaiyumari15 wants to merge 3 commits into
MoonlightCapital:testingfrom
Kaiyumari15:premium-page-correct-image-placement

Conversation

@Kaiyumari15
Copy link
Copy Markdown
Contributor

Description

Please provide a summary of all the changes made in this pull request, along with some motivation and context.

Correcting image placement for the Premium Page as requested by @MoonlightCapital.

I've also included comments to suppress the markdownlint warning.

Checklist

  • Markdown formatting has been checked and renders correctly with no issue
  • All information provided in the pull request is accurate and up to date with MoonlightBot's functioning
  • All information provided is consistent with the already existing style of the rest of documentation (skip this if you're modifying the style as whole)
  • Reasonable efforts have been made to make the documentation readable to the end user
  • Reasonable effort has been put in proofreading the text for any spelling, typography or grammar errors
  • If this pull request features changes that have been made in beta versions, it is immediate to the end user to understand this

^ Hopefully...
Adding the line spacing caused the linting error. I disable it in the comments and reenable it again
Hopefully...
Also add comments to suppress the markdownlint warning about expecting a "1." for the ordered list after the spacing line for image placement
@MoonlightCapital
Copy link
Copy Markdown
Owner

This is superseded and the correct formatting that the page needed to display the images inline with the list has been corrected in #68

@Kaiyumari15 Sorry but it does not take three months to make fixes like this and abandon the PR midway. I understand you had things to navigate elsewhere, but leaving this here with dubious mergeability and only updating me on it when I asked for it instead of passing it down for someone to take over and have it fixed quickly. Please hand things over to someone else next time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants