Fixed inline code rendering issue in curveVertex

[DenisovichDev]

Hello, this is my first PR here!

I noticed some inline code issues that might have popped up because of some porting issues from the old website. This is what it looked like:

Here's what it looks like now:

These were some special cases in the reference where it wasn't a code snippet but a multiline inline codes.

[davepagurek]

Thanks @DenisovichDev! The reference gets updated every release from the contents in the p5.js repo, so I think we'll need to update the source there to not get turned back into multiple lines. I fixed a similar issue in the p5.js repo here https://github.com/processing/p5.js/pull/7089/files, does that method also apply to these functions?

Within this repo, I think rather than having inline code blocks separated by newlines, we might want to just group everything into one code block. That ends up looking like this: https://github.com/processing/p5.js-website/pull/407/files#diff-a9f22d63312d5dcf8286875d13c5ca83ee171d6bb92a2a21b8c50b7090771010R55

[DenisovichDev]

Thanks for the reply! I suppose that would fix it. So, shall I make a pull request changing the docstring in the p5.js repo?

And for this repo, I'll make the changes that you mentioned then, by grouping it with the <pre> tags

[davepagurek]

Sounds good, thanks so much!

[DenisovichDev]

While editing the reference from p5.js repo I noticed a similar issue in normal() as well, so I have made the changes and added it here

[davepagurek]

Thanks for all the fixes @DenisovichDev!