Typos & Minor Edits Mega-thread

On the ‘UseJumpPower’ property, it says the same thing twice.

  1. The second sentence of the Translator documentation starts with a lowercase letter.

  2. Multiple places in the UIStroke documentation, text is surrounded by “**” instead of a <b> tag (here, here, and here).

  3. The properties table in the Lighting documentation has a “`” mistakenly.

  4. The properties table in the Lighting documentation ends a sentence with “. .” instead of a single period.

  5. Several code samples in the Lighting documentation (one, two, three, and four, five, six, and seven, eight, nine, and ten) say minutesAfterMidnight = minutesAfterMidnight + 1 when they could be shortened to minutesAfterMidnight += 1.

  6. At the bottom of the MarketPlaceService | ProcessReceipt documentation, there is a red line for seemingly no reason.

1 Like

This link on the BindableEvent page redirects to a heading that doesn’t exist. It should redirect to
https://create.roblox.com/docs/en-us/scripting/events/custom#argument-limitations.

Under BasePart’s IsGrounded section
“that has an Basepart.Anchored part”; the article “an” should be exchanged for “a”


Edit: also “(eg an BasePart.Anchored part)” should ideally be “(e.g. a BasePart.Anchored part)”

Typo!

“whilse” should be “whilst”.

1 Like

Another mistake: “Subsequent attempts are likely the fail”.

Another mistake: “Attatchment”

This one is a nitpick… there’s a loose period after the last image.

Not sure if this is intended.

This should be “An emote animation”


Two nitpicks. There is a exclamation mark and a period, and an inconsistency because “enum” is not uppercase, when in all the other articles it is.

image

This one’s pretty obvious.

image

Not sure if this is considered a mistake, but I’m still trying to figure out why it’s camelCased?

Not a complete sentence.

This is pretty weird and hard to read, I’d call it a mistake.

I’d call this a mistake. “Player can also control character with mouse and keyboard.” lacks an article for Player and preferably a possessive article for “mouse”.

There is a space after a period.

This one is odd, considering it doesn’t talk about :SetCoreGuiEnabled() in any of the other enums, but specifically that one.

There is a grammar error under the roadmap:

Should be:

An engine which can support any type of experience

We’re focused on ensuring that our engine can help you achieve your goals regardless of your ambition.

1 Like

@ramdoys @ProgrammerOnCoffee @Rainbow_Derp @pyxfluff thanks for flagging all these!

4 Likes

This instruction on how to navigate to a certain dashboard is outdated. The highlighted text should be changed to “Under the MONITORING dropdown”.

“Contribute your Luau scripts for AI training can help enhance Luau-focused AI tools in Studio.”
Contribute → Contributing

1 Like

minor edits:

In the “Part , Size” section (Part | Documentation - Roblox Creator Hub)
“collision detection” lead to a not working link

(prod.docsiteassets.roblox.com/workspace/collisions.md)

Thanks for flagging this. The instruction now matches the latest dashboard UI.

@Sylently Thank you for flagging, this has been fixed!

@Lucatacos2213 Thank you for flagging! I need to look more into this, but I’m hoping to have an update for you soon.

  • Two images (here and here) have the wrong caption.

  • There’s a run-on sentence here.

Thank you for flagging, the image captions are now up-to-date!

Status | Documentation - Roblox Creator Hub
The word Deprecated is spelled wrong

Hi @0Tenth,
Thanks for the note. This typo has been fixed:

IgnisRBX

AnimationClip quotes in KeyframeSequenceProvider | Documentation - Roblox Creator Hub is not formatted correctly. It should ‘AnimationClip’ or AnimationClip not 'AnimationClip’s.

image

There is no space between client and It inhttps://create.roblox.com/docs/reference/engine/classes/GoogleAnalyticsConfiguration
image

Step 2 from this link makes no sense Immersive Ads | Documentation - Roblox Creator Hub. Parts do not have a Face property, I believe it is referring to AdGui but it does not make it clear especially since it has not even been created before this step. Ideally, step 2 would be under step 4.