Merge branch 'main' into patch-1

Author: aetter

README.md

@@ -2,7 +2,7 @@
 
 This repository holds source code for the creator documentation at [create.roblox.com/docs](https://create.roblox.com/docs).
 
-**Note**: Currently, the repository has guides, tutorials, educational content, and the Engine API reference. Code samples are coming soon.
+**Note**: Currently, the repository has guides, tutorials, educational content, and a read-only version of the Engine API reference.
 
 If you're unfamiliar with the GitHub contribution process, see [About pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) and the following video.
 
@@ -77,14 +77,14 @@ The Roblox documentation has three main document types:
 
   Guides benefit massively from practical, real-world use cases, images, code snippets, and diagrams. Most task-based content should include a numbered list.
 
-- API reference docs in `.yaml` files in [content/en-us/reference](./content/en-us/reference)
-
-  APIs are entirely reference content and should use functional descriptions, linking to guides where appropriate. More than other content types, reference content should be terse and direct; summaries for properties, methods, events, and callbacks don't need to be full sentences.
-
 - Tutorials in `.md` files in [content/en-us/tutorials](./content/en-us/tutorials)
 
   Compared to task-based guides, tutorials are more self-contained and take you from _nothing_ to _something_. This focus on creating something specific means they're typically much more prescriptive than guides. Tutorials often touch multiple features and concepts at the same time, demonstrating the connections between tools and strategies.
 
+- API reference docs in `.yaml` files in [content/en-us/reference](./content/en-us/reference)
+
+  We provide these files so that you can view the source and use them in your own projects, but we **no longer** accept pull requests on the reference `.yaml` files.
+
 If your contribution doesn't fit within these categories or covers a particularly narrow subject, it might not be a good fit for the documentation. Consider posting it to the [Roblox developer forum](https://devforum.roblox.com/c/resources/71).
 
 ## Contribution Basics

content/en-us/assets/feeds/lighting_terrain.webp

@@ -204,7 +204,7 @@ Note that changing `Class.ParticleEmitter.Speed|Speed` does not affect active pa
 
 ### Rate
 
-The `Class.ParticleEmitter.Rate|Rate` property sets the number of particles that emit per second. A single particle emitter can create up to 500 particles per second. For best performance, keep the particle rate as low as possible and experiment with [size](#size) and [other properties](#other-properties) to achieve the desired visual effect.
+The `Class.ParticleEmitter.Rate|Rate` property sets the number of particles that emit per second. A single particle emitter can create up to 400 particles per second (100 per second on mobile). For best performance, keep the particle rate as low as possible and experiment with [size](#size) and [other properties](#other-properties) to achieve the desired visual effect.
 
 <Alert severity="warning">
 Particle count can impact performance due to overdraw, especially when particles are overlapping. The more layers of transparent effects on screen, the more costly it is on the GPU.

content/en-us/assets/feeds/rewarded_ads.webp

@@ -178,15 +178,7 @@ The following are common input binds that will help players immediately feel fam
 
 Many gamepad controllers have motors built in to provide haptic feedback. Adding rumbles and vibrations can greatly enhance a player's experience and provide subtle feedback beyond visuals or audio.
 
-Roblox supports haptics for the following devices:
-
-- Android and iOS phones supporting haptics including most iPhone, Pixel, and
-	Samsung Galaxy devices
-- PlayStation gamepads
-- Xbox gamepads
-- Quest Touch controller
-
-Haptic feedback is managed through `Class.HapticEffect` instances which can be set to a specific `Class.HapticEffect.Type|Type` such as `Enum.HapticEffectType|GameplayCollision` or `Enum.HapticEffectType|UIClick`.
+Roblox supports haptics for PlayStation gamepads, Xbox gamepads, and the Quest Touch controller. Haptic feedback is managed through `Class.HapticEffect` instances which can be set to a specific `Class.HapticEffect.Type|Type` such as `Enum.HapticEffectType|GameplayCollision` or `Enum.HapticEffectType|UIClick`.
 
 Once a `Class.HapticEffect` is in place, you can initiate it through the `Class.HapticEffect:Play()|Play()` method, for instance: