Edit docs for environment

[nickmcintyre]

Addresses #6483

Changes:
I edited the inline docs for the rest of the functions in the "Environment" group to bring them more in line with the style guide.

@dkessner, @MsQCompSci, @davepagurek, @limzykenneth, @Qianqianye, @ChihYungChang, @teragramgius, @tuminzee, @Zarkv, @robin-haxx, @Gaurav-1306 I'd love to incorporate any feedback you may have! Here's a staging version of the edits in this pull request.

PR Checklist

• npm run lint passes
• [Inline documentation] is included / updated

[MsQCompSci]

Some helpful things for newer users:

• All code examples clearly show where code should be written (within draw, or setup , etc)
• Comments in all code examples that describes what specific lines of code do
• Differentiating examples for the same function via comments (how are they different)

[nickmcintyre]

Great suggestions @MsQCompSci, I added setup(), draw(), and plenty of comments.

@Qianqianye @limzykenneth @davepagurek if these changes look good to you, please go ahead and merge them.

[davepagurek]

Looks great! Found one more typo, and one last bit that we may or may not want to change, depends what we think is most useful for people.

[davepagurek]

Do you think we should mention somewhere in the docs what p5 constants this can be? Although examples that print the version are simpler with code, I assume the most common way this will be used is by checking if webglVersion === WEBGL2 or something like that. While === 'webgl2' also works, it's probably a little less error prone to use the constant.

[davepagurek]

I think this one is just a property and not a function:

Suggested change

	* `displayHeight()` is useful for running full-screen programs.
	* `displayHeight` is useful for running full-screen programs.

[nickmcintyre]

Good catches and suggestions @davepagurek – just incorporated them.

[davepagurek]

The changes look good, thanks!