diff --git a/content/en-us/production/localization/automatic-translations.md b/content/en-us/production/localization/automatic-translations.md index 293804671..578f992c8 100644 --- a/content/en-us/production/localization/automatic-translations.md +++ b/content/en-us/production/localization/automatic-translations.md @@ -27,22 +27,22 @@ To enable Automatic Text Capture: The Localization Settings section highlighting the toggle for Capture text from Experience UI while users play. -ATC adds text strings to the localization table within 1-2 minutes of encountering the text in the experience. If you do not want ATC to collect a certain text string, such as a name or unique text entry, disable the `Class.GuiBase2d.AutoLocalize|AutoLocalize` property of the text object. +ATC adds text strings to the localization table within 1–2 minutes of encountering the text in the experience. If you do not want ATC to collect a certain text string, such as a name or unique text entry, disable the `Class.GuiBase2d.AutoLocalize|AutoLocalize` property of the text object. ATC can not capture some experience objects. These objects may require special handling with localization scripts. The current exemptions are: ### Text Capture in Studio -There may be situations in which you need to immediately capture strings to your translation table. In these cases, you can use the text capture tool in Studio to capture strings while playtesting. These strings will be added to the localization table within 1-2 minutes of encountering them. +There may be situations in which you need to immediately capture strings to your translation table. In these cases, you can use the text capture tool in Studio to capture strings while playtesting. These strings will be added to the localization table within 1–2 minutes of encountering them. To enable text capture in Studio: @@ -92,7 +92,7 @@ You can track your automatic translation quota usage on your experience's locali The Localization Languages section depicting the Automatic Translation Quotas at the top of the page, including the date of the monthly quota renewal. -Quotas are calculated on a **per-character** and **per-language basis**. For example, translating the source string "hello" into all 15 automatic translation-supported languages will count as 5 x 15 = 75 characters towards your quota. +Quotas are calculated on a **per-character** and **per-language basis**. For example, translating the source string "hello" into all 15 automatic translation-supported languages will count as 5×15 (75) characters towards your quota. ### Automatic Translation Updates @@ -150,6 +150,9 @@ Roblox supports automatic translation between the languages listed below. Curren Korean + + Polish + Portuguese @@ -165,9 +168,6 @@ Roblox supports automatic translation between the languages listed below. Curren Turkish - - Polish - Vietnamese diff --git a/content/en-us/reference/engine/classes/DataStoreService.yaml b/content/en-us/reference/engine/classes/DataStoreService.yaml index 456198d3b..27e159ae2 100644 --- a/content/en-us/reference/engine/classes/DataStoreService.yaml +++ b/content/en-us/reference/engine/classes/DataStoreService.yaml @@ -188,7 +188,7 @@ methods: given prefix. - name: pageSize type: int - default: 0 + default: 32 summary: | **(Optional)** Number of items to be returned in each page. By default is 32. diff --git a/content/en-us/reference/engine/classes/OrderedDataStore.yaml b/content/en-us/reference/engine/classes/OrderedDataStore.yaml index 346840d2f..ae7953c69 100644 --- a/content/en-us/reference/engine/classes/OrderedDataStore.yaml +++ b/content/en-us/reference/engine/classes/OrderedDataStore.yaml @@ -41,8 +41,8 @@ methods: **minValue**/**maxValue** are optional parameters which filter the results. - See [Data Stores](../../../cloud-services/data-stores) for request limits - and descriptions of the error codes. + See [Data Stores](../../../cloud-services/data-stores/index.md) for + request limits and descriptions of the error codes. code_samples: parameters: - name: ascending diff --git a/content/en-us/reference/engine/classes/Terrain.yaml b/content/en-us/reference/engine/classes/Terrain.yaml index 2aaf272e0..3d0bdb840 100644 --- a/content/en-us/reference/engine/classes/Terrain.yaml +++ b/content/en-us/reference/engine/classes/Terrain.yaml @@ -475,7 +475,7 @@ methods: type: CFrame default: summary: | - The cframe (position and orientation) of the terrain block. + The position and orientation of the terrain block. - name: size type: Vector3 default: @@ -513,7 +513,7 @@ methods: type: CFrame default: summary: | - The CFrame (position and orientation) of the terrain cylinder. + The position and orientation of the terrain cylinder. - name: height type: float default: diff --git a/content/en-us/tutorials/fundamentals/coding-5/intro-to-dictionaries.md b/content/en-us/tutorials/fundamentals/coding-5/intro-to-dictionaries.md index 25f250b9c..d6ed1453a 100644 --- a/content/en-us/tutorials/fundamentals/coding-5/intro-to-dictionaries.md +++ b/content/en-us/tutorials/fundamentals/coding-5/intro-to-dictionaries.md @@ -5,7 +5,7 @@ next: /tutorials/fundamentals/coding-5/pairs-and-ipairs prev: /tutorials/fundamentals/coding-5/making-changes-to-arrays --- -Dictionaries are tables that associate names or "\*keys\*\*" with a value instead of an index. +Dictionaries are tables that associate names or **keys** with a value instead of an index. Example: @@ -16,11 +16,11 @@ local pet = { } ``` -Use dictionaries when you need to label values, not just list them in order as an array does —practice using dictionaries in this tutorial by manipulating values associated with a player. +Use dictionaries when you need to label values, not just list them in order as an array does. Practice using dictionaries in this tutorial by manipulating values associated with a player. ## Dictionary Syntax -Like arrays, dictionaries are assigned to a variable with curly brackets`{}`. **Key value pairs** are stored on separate lines followed by a comma. Keys and values can be any data type, including strings, numbers, and variable names. +Like arrays, dictionaries are assigned to a variable with curly brackets `{}`. **Key-value pairs** are stored on separate lines followed by a comma. Keys and values can be any data type, including strings, numbers, and variable names. ```lua local playerNames = { @@ -87,8 +87,9 @@ One everyday use of dictionaries is organizing player or character information. ### Using Dictionary Values There are two ways to access dictionary values: -`tableName["keyName"]` -- Note the quotations -`tableName.keyName` + +- `tableName["keyName"]` (importantly, note the quotations) +- `tableName.keyName` ```lua local enemy = { @@ -100,7 +101,7 @@ print("The villain " .. enemy["Name"] .. " approaches!") print("The villain " .. enemy.Name .. " approaches!") ``` -Which style to use usually depends on the purpose of the table. For tables holding a collection of values like a list of players in a server, coders will usually use tableName["keyName"]. For a dictionary used to describe an object, coders are more likely to use tableName.keyName. +Which style to use usually depends on the purpose of the table. For tables holding a collection of values like a list of players in a server, coders will usually use `tableName["keyName"]`. For a dictionary used to describe an object, coders are more likely to use `tableName.keyName`. ## Changing a Dictionary Value @@ -158,7 +159,7 @@ Dictionaries can interact with pre-existing variables declared in other parts of end ``` -4. Insert name into the `playerPoints` dictionary as a key, and set the value, the player's points, to 0. +4. Insert `name` into the `playerPoints` dictionary as a key, and set the value, the player's points, to 0. ```lua local function setPoints(newPlayer) @@ -169,10 +170,10 @@ Dictionaries can interact with pre-existing variables declared in other parts of ``` - Since `name` was created as a variable, it can be accessed with the actual variable name. If `name` had been simply a key name, it would need to be accessed the same as other strings, playerPoints["name"] + Since `name` was created as a variable, it can be accessed with the actual variable name. If `name` were a key name, it would need to be accessed the same as other strings: `playerPoints["name"]`. -5. Use `name` to print the name of the player and playerPoints[name] to print the value of the key matching the variable. +5. Use `name` to print the name of the player and `playerPoints[name]` to print the value of the key matching the variable. ```lua local function setPoints(newPlayer) @@ -183,7 +184,7 @@ Dictionaries can interact with pre-existing variables declared in other parts of end ``` -6. Run the project and look into the output editor. +6. Run the project and observe the output. ```lua title="Finished script" local Players = game:GetService("Players") @@ -208,7 +209,7 @@ Below are some challenges that apply to using dictionaries in different ways. Se - Create a trap part that does damage over time to a player. Once a player touches the trap, damage them, wait, then allow them to be damaged again. - Create a function that checks which of two players has the most points by accessing a dictionary. -- Create a cipher, a system of swapping one word for another to create a "secret" code, for example, how the letter "A" can be swapped with "G", or how the word apple can be swapped for the word orange. +- Create a cipher, a system of swapping one string for another to create a "secret" code. For example, the letter "A" can be swapped with "G," or the word "apple" can be swapped with "orange." ## Dictionaries and pairs() @@ -257,7 +258,7 @@ Dictionaries are tables that use key-value pairs instead of indexed values. Dict All keys within a dictionary should use the same data type, but the values can mix data types without issue. -The style of how a dictionary is accessed can convey the purpose of a dictionary. A dictionary of enemy properties will likely be accessed with the dot operator, while a list of names will likely use tableName[keyName]. +The way in which a dictionary is accessed can convey its purpose. A dictionary of enemy properties will likely be accessed with the dot operator, while a list of names will likely use `tableName[keyName]`. When using brackets, be careful; key names created within the table must be treated as strings: `tableName["keyName"]`. However, when referencing objects like parts, the quotations are not needed: `tableName[keyName]`.