Typos & Minor Edits Mega-thread

There is an unintentional space before the period in this documentation about SoundService:

5 Likes

All of the highlighted typos / possible errors in this post are from the Player object documentation page, as of February 8th, 2023.

For reference, any text that is bold within the “Recommended Edits” portion of each section indicates where something was changed from the original text.


Section #1 - Player object description

In the first sentence of the description of the Player object, a word is missing between “object” and “a”.

Recommended Edit:

A player object is a client that is currently connected.



In the third paragraph, the word “service” is missing after the hyperlink to the Players documentation page. Adding the word “service” for clarification would make it easier to understand and would keep it consistent with the 2 other sentences where the service is referenced on its own.

Recommended Edit:

There are several similar methods in the Players service for working with Player objects.





Section #2 - Player.AutoJumpEnabled property description

In the second sentence of the second paragraph, An apostrophe is missing after the word “Character”, which would be needed to show that it’s talking about an individual Character’s Humanoid.

Recommended Edit:

Then, this property determines the value of the Humanoid.AutoJumpEnabled property of the Player.Character’s Humanoid on spawn.





Section #3 - Player.CharacterAppearanceId property description

In the first sentence of the description, the hyperlink to the Character section of the page wasn’t added and its code block was not closed off at the correct spot. This also caused the hyperlinks to the Player object and Player.UserId property to be incorrectly formatted in the second sentence.

Recommended Edit:

This property determines the user ID of the account whose character appearance is used for a player’s Character. By default, this property is the Player's Player.UserId, which uses the player’s avatar as they have created it on the Roblox website.





Section #4 - Player.DevComputerCameraMode property description

At the end of the first sentence, the word “device” is repeated two times. I have two recommended changes to this depending on what the intended meaning is:

Recommended Edit

The DevComputerCameraMode property determines the manner in which a player moves their camera when using a device with a mouse-and-keyboard.


If that would affect the meaning of existing content too much, then this would be a more reasonable change:

Alternative Recommended Edit

The DevComputerCameraMode property determines the manner in which a player moves their camera when using a mouse-and-keyboard device.





Section #5 - Player.DevComputerMovementMode property description

The same potential typo from Section #4 happens at the end of the first sentence in the Player.DevComputerMovementMode property section, where the word “device” is repeated two times.

Once again, I have two recommended changes to this depending on what the intended meaning is:

Recommended Edit

The DevComputerMovementMode property determines the manner in which a player moves their character when using a device with a mouse-and-keyboard.


If that would affect the meaning of existing content too much, then this would be a more reasonable change:

Alternative Recommended Edit

The DevComputerMovementMode property determines the manner in which a player moves their character when using a mouse-and-keyboard device.





Section #6 - Player.DevEnableMouseLock property description

In the second sentence of the second paragraph, the word “the” is missing between “and character”.

Recommended Edit

Moving the mouse will orbit the camera around the player’s character, and the character will face the same direction as the camera.





Section #7 - Player.DisplayName property description

There are three separate errors in this section, all of which are related to hyperlinks.

  1. In the first bullet point of the description, a hyperlink to Player.Name is included but navigating to it does not bring you to a description of the property, as no dedicated section documenting the Player.Name property currently exists on the page.

  2. In the second bullet point of the description, both LoadCharacter and the first mention of DisplayName (which is referring to a property of the Humanoid object) were wrapped in a codeblock but without hyperlinks, even though documentation exists for both of those.

Recommended Edit

Characters generated with LoadCharacter or by the Roblox engine will have their Humanoid’s DisplayName property assigned to the Player’s DisplayName property.





Section #8 - Player.TeamColor property description

Toward the end of the second paragraph, there was an extra letter “s” added to the word “team”.

Recommended Edit

Setting this property often leads to repetition of the same BrickColor value for a certain team across many scripts; this is something you want to avoid when adhering to the don’t-repeat-yourself principle.





Section #9 - Player:GetJoinData method description

Several of the descriptions in the Player.GetJoinData section could have hyperlinks to referenced properties / relevant guides for improved accessibility.

Recommended Edits

(For the description of “SourceGameId”)

The DataModel.GameId of the experience the Player teleported from.

(For the description of “SourcePlaceId”)

The DataModel.PlaceId of the place the Player teleported from. Only present if the player teleports to the current place and a server calls the teleport function.

(For the description of “Members”)

An array containing the UserId numbers of the users teleported alongside the Player. Only present if the player teleported as part of a group.


(For the second image, at the end of the “GetJoinData and TeleportData” sub-section)

As this data is transmitted by the client, it can still potentially be abused by an exploiter. Sensitive data such as player currency should be transmitted via a secure solution like Memory Stores.


(For the third image directly above, in the “LaunchData” sub-section, “roblox” should be capitalized to “Roblox”)

You can also make sure that this link works for users without Roblox downloaded on their mobile devices…





Section #10 - Player:SetSuperSafeChat() method description

In the second sentence of the description, an unnecessary apostrophe was added to the word “players”. In the sentence that follows that, the word “enable” was written in the incorrect tense (it should be “enable”, not “enabled”).

Recommended Edit

SuperSafeChat is a chat mode where players cannot see unfiltered messages.

For example, entering the following command in the command prompt would enable SuperSafeChat for the player named polarpanda16, as long as that player is in the game:





Section #11 - Player:GetFriendsOnline method description

The hyperlink to the DisplayName documentation section was formatted incorrectly. This can be found within the table that lists the expected values to be returned from the Player:GetFriendsOnline method, specifically in the description for the “DisplayName” argument (the third from the top).

Recommended Edit

The Player.DisplayName of the friend.





Section #12 - Player:IsFriendsWith method description

In the second sentence, “userId” is wrapped in a codeblock with the incorrect capitalization and no hyperlink to the Player.UserId property it’s referring to. The incorrect capitalization is also included in the “Parameters” section directly below the description.

Recommended Edit

This function caches results so multiple calls of the function on the same player with the same UserId may not yield the most up-to-date result. This does not happen when used in a LocalScript.





Section #13 - Player:LoadCharacter method description

In the last sentence of the third paragraph, the word “script” is not plural nor is there a hyperlink to its documentation page.

Recommended Edit

Also, this function can be used in Scripts, while LoadCharacterBlocking cannot.

Alternative Recommended Edit

Also, this function can be used in a Script, while LoadCharacterBlocking cannot.





Section #14 - Player.CharacterAdded Event Description

In the third paragraph of the description, the deprecated Hat object was referenced as an example clothing item, whereas the equivalent and currently-used Accessory object would be more relevant to include. Additionally, a grammatical error exists at the same part of the sentence: "Hats and Shirts, and Pants…"

Recommended Edit

Note that the Humanoid and its default body parts (head, torso, and limbs) will exist when this event fires, but clothing items like Accessories, Shirts, and Pants may take a few seconds to be added to the character.





Section #15 - Player.CharacterAppearanceLoaded Event Description

The first sentence of the second paragraph has a grammatical error: “Player.Character's generally have…”

Later on in the sentence, the Accoutrement object is mentioned as a example object that can modify the Character’s appearance. However, similar to the example from Section #14, the equivalent and currently-used Accessory object would be more relevant to include.

Then, in the first sentence of the third paragraph, “Characters” is missing an apostrophe to properly describe the relationship between the Character and its appearance; the description is currently using the plural form of the word “Character”.

Recommended Edits

Note

In the first recommended edit, a comma was added after “appearance”. I tried to make it bold (to indicate it was an addition / change) but it isn’t formatted correctly while next to another letter**,** like what was demonstrated just there (unless it works by the time you’re reading this).

A Player.Character generally has a range of objects modifying its appearance, including Accessories, Shirts, Pants and CharacterMeshes.

One use for this event, is to remove and save aspects of a Character's appearance to be used later.





Section #16 - Player.CharacterRemoving Event Description

The last sentence of the second paragraph is missing the word “to” between “like print”.

Recommended Edit

For instance, if you would like to print a message every time a player spawns and dies:





Section #17 - Player.Chatted event description

At the end of the third sentence within the “Chat Commands” section, there’s an extra space added between the closing parentheses and the period.

Recommended Edit

To check for a prefix in a string, use string.sub() on the message to check a substring of the message: string.sub(message, 1, 6) == "/heal " (note the inclusion of the space).





Section #18 - Player.Idled event description

In the first sentence of the first paragraph, the reference to the Player object isn’t capitalized (but it should be).

In the last sentence of the fourth paragraph, the word “considering” was written in an incorrect tense.

Recommended Edits

This event is usually fired two minutes after the game engine classifies the Player as idle.

If you would like to track when this disconnect occurs, consider using Players.PlayerRemoving alongside this event.





Section #19 - Player.SimulationRadiusChanged event description

In the second sentence of the “What is the SimulationRadius” sub-section, the singular possessive word of Player's was used instead of the more applicable, plural possessive word of Players', as the description specified multiple players and not an individual one.

Important Note

Recommended Edit

In cases where a BasePart or assembly is within multiple players’ SimulationRadiuses, the closest player is chosen.





Hope that this ends up being useful! Maybe I’ll continue proofreading various pages throughout the Roblox Creator Documentation in the future since it was pretty interesting; got to learn about the nuances of some features that I hadn’t been aware of beforehand.

9 Likes

Great callouts, thank you! The typos you mentioned are now fixed.

3 Likes

Thank you very much for all of these edits! I’m working on them right now and they should go live soon.

4 Likes

Great catch, I will fix this right now!

2 Likes

Once clicking on the article where it tells about the ColorShift_Top, it contained a typo regarding Lighting.ColorShift_Bottom as repeating the word “Lighting” one more time:

It was fixed a year ago, but you are not able to get to the article mentioning the ColorShift_Bottom (I know that I should have reported that in the same topic, but it was closed), and yes only have the last parts of the URL link changed.

Issue Area: Lighting | Roblox Creator Documentation

(@TooManyOveralls ^)

2 Likes

Good eye, I’ll fix this right now. You should see the change very soon.

3 Likes

In this article, the word “unpredictable” is misspelled as “unpredicatable”

m

3 Likes

Not sure if this is intentional, but the reference to HapticService:SetMotor isn’t highlighted in blue or clickable.

3 Likes

Under “Requesting Area Streaming”

the code game uses . to call a function instead of :

local function teleportPlayer(player, teleportTarget)
	-- Request streaming around target location
	player.RequestStreamAroundAsync(teleportTarget)
       -- This results in a error: Expected ':' not '.' calling member function RequestStreamAroundAsync 

Should be

local function teleportPlayer(player, teleportTarget)
	-- Request streaming around target location
	player:RequestStreamAroundAsync(teleportTarget)
2 Likes

You can add translations Products such as Badges and Passes…

Should be
“You can add translations for Products such as Badges and Passes…”


Just a heads up, @Map1eMoose:


Code sample errors are among the things not meant to be posted in this thread

1 Like

Minor edit:

On AnalyticsService’s documentation, it states “… take a look at this DevForum post” with no links to it.
image
AnalyticsService | Roblox Creator Documentation

1 Like

MicroProfiler is constantly running, analyizing the render time for every frame. To see useful data, you need to pause MircoProfiler and analyze render information on a frame-by-frame basis. Press Ctrl+P to pause the MicroProfiler.

Typo alert!

1 Like

@ProBaturay @Dysche @Map1eMoose @SeargentAUS @Den_vers

Thank you for catching these! All fixes are going to go live very soon.

6 Likes

Thank you for this report! AnalyticsService is deprecated, I’d recommend using the Analytics Dashboard :slight_smile:

Don’t know if this belongs here since it’s not a grammar issue but rather a single word being copy + pasted from the wrong function, while it does change the meaning of the sentence, common sense would make any developer doubt this behaviour

https://create.roblox.com/docs/reference/engine/classes/AvatarEditorService#PromptRenameOutfit

PromptRenameOutfit says the following:

Prompts the Players.LocalPlayer to delete the given outfit. Does not yield. The result can be retrieved by listening to the AvatarEditorService.PromptRenameOutfitCompleted event.

This function states that it deletes the outfit like PromptDeleteOutfit but this is not true, it should be changed to the following:

Prompts the Players.LocalPlayer to rename the given outfit. Does not yield. The result can be retrieved by listening to the AvatarEditorService.PromptRenameOutfitCompleted event.

1 Like

Alright 2 minor things:

1 Like

miss-placing backticks/backquotes in the IK controls page


(right above the Offset property)

2 Likes

It took me 4 hours to find all of the issues below and 2 hours to format the post. The list shows the categories almost in this order:

1) Repeated words
2) Misspelled words
3) Other grammar issues

All of the issues were found under the Guides title. There are many more mistakes I could not put here. Links will redirect you to the typos or text that should be edited.


Issue #1

The phrase “of detail” is repeated.

Link


Issue #2

The word “or” is repeated.

Link


Issue #3

The word “with” is repeated.

Link


Issue #4

The word “from” is repeated.

Link


Issue #5

The word “to” is repeated.

Link


Issue #6

The word “that” is repeated.

Link


Issue #7

The word “tab” is repeated. That word should be merged with Script, which both navigate to Script Tab.

Link


Issue #8

The phrase “in the Variables tab” is repeated.

Link


Issue #9

The word “a” is repeated.

Link


Issue #10

The word “includes” is repeated.

Link


Issue #11

The phrase “use the” is repeated.

Link


Issue #12

The word “asynchronous” is misspelled as “asyncronous”.

Link


Issue #13

The word “Asynchronously” is misspelled as “Asyncronously”.

Link


Issue #14

The word “Analyzing” is misspelled as “analyizing”.

Link


Issue #15

The phrase “quality-of-life” is misspelled as “quality-of-live”.

Link


Issue #16

The word “encompasses” is misspelled as “emcompasses”.

Link


Issue #17

The first letter of the word “Venn” is not capitalized.

Link


Issue #18

The word “maximum” is misspelled as “maxiumum”.

image18_1

image18_2

Link1
Link2


Issue #19

There’s a conflict in the text. It should be updated as “duplicate keyframes


Issue #20

There should be an apostrophe at the end of the word “wizards”.

image20

Link


Issue #21

The word “there” should be at the end of the sentence for clarification.

Link


Issue #22

Incorrect verb form.

image22

Link


Issue #23

Incorrect verb form.

Link


Issue #24

Incorrect verb form.

image24

Link


Issue #25

Incorrect verb form.

Link


Issue #26

Incorrect verb form.

Link


Issue #27

Incorrect verb form.

Link


Issue #28

Incorrect verb form.

Link


Issue #29

Incorrect verb form.

Link


Issue #30

Incorrect verb form.

Link


Issue #31

Incorrect verb form.

Link


Issue #32

Incorrect verb form.

Link


Issue #33

Incorrect verb form.

Link


Issue #34

Incorrect verb form.
Warning: The message in the text below is emitted through particular functions. It may not be changed depending on the return message.

image34

Link


Issue #35

Incorrect verb form.

Link


Issue #36

Incorrect verb form.

Link


Issue #37

Incorrect verb form.

Link


Issue #38

Incorrect verb form.

Link


Issue #39

Incorrect verb form.

Link


Issue #40

Incorrect verb form.

Link


Issue #41

Incorrect verb form.

Link


Issue #42

Incorrect verb form.

image42

Link


Issue #43

Incorrect verb form.

Link


Issue #44

Incorrect verb form.

Link


Issue #45

Incorrect verb form.

Link


Issue #46

Incorrect noun form.

Link


Issue #47

The word “monetize” should be corrected to “monetizing”.

Link


Issue #48

Incorrect verb form.

Link


Issue #49

The phrase “to discriminate” should be corrected to “discriminating”.

Link


Issue #50

The word “disable” should be corrected to “to disable”.

Link


Issue #51

The word “prioritizing” should be corrected to “prioritize”.

Link


Issue #52

The phrase “to use tools do” should be corrected to “to use tools to do”.

Link


Issue #53

The word “belong” should be corrected to “belonging”.

Link


Issue #54

The word “throttling” should be corrected to “throttles”.

Link


Issue #55

The phrase “allow includes” should be corrected to “allows”.

Link


Issue #56

The phrase “or to” should be corrected to “or”.

image56

Link


Issue #57

The word “update” should be corrected to “updating”.

image57

Link


Issue #58

The phrase “a more frames” should be corrected to “more frames”.

Link


Issue #59

Unnecessary verb “is”.

Link


Issue #60

Unnecessary adjective “individual”.

Link


Issue #61

The phrase “tile to deselect” is redundant.

Link


Issue #62

The possessive affix seems redundant.

Link


Issue #63

Incorrect verb form.

Link


Issue #64

Missing verb.

Link


Issue #65

Missing preposition. It should be corrected to “There are also functionalities on each dashboard to help”

Link


6 Likes

Page link: Highlight | Roblox Creator Documentation

IMPORTANT: As a performance limit, Studio only displays 31 simultaneous Highlight instances on the client at a time. If you exceed this limit, the additional instances are silently ignored. While a disabled Highlight doesn’t display, it still takes one of the 31 available Highlight slots. If you plan to permanently disable a Highlight instance, it’s best to delete the highlight rather than disable it.

For low-end devices, Studio uses a fallback version that doesn’t have high performance overheads. This version doesn’t have the outline effect; instead, it creates an interior fill with a checker pattern to emulate the FillTransparency property.

The documentation incorrectly refers to the Roblox game-client as “Studio”, it should instead be edited to the following:

IMPORTANT: As a performance limit, Studio and the client only display 31 simultaneous Highlight instances at a time. If you exceed this limit, the additional instances are silently ignored. While a disabled Highlight doesn’t display, it still takes one of the 31 available Highlight slots. If you plan to permanently disable a Highlight instance, it’s best to delete the highlight rather than disable it.

For low-end devices, the client uses a fallback version that doesn’t have high performance overheads. This version doesn’t have the outline effect; instead, it creates an interior fill with a checker pattern to emulate the FillTransparency property.

Also, the image below the text needs to be made bigger as at it’s current resolution the effect it is trying to display cannot be seen.