Merge branch 'master' of https://github.com/getsentry/sentry-docs

* 'master' of https://github.com/getsentry/sentry-docs: (22 commits)
  Fix incorrectly placed comma (#14592)
  fix(devservices): Typo in devservices docs (#14636)
  ref(ourlogs): Add log size limit (#14635)
  Document undocumented php prefix option (#14634)
  getsentry/relay@7958273
  Unreal Engine: Update plugin docs (#14624)
  feat: Update min js sdk version for logging and update console logging snippet (#14614)
  feat: [Unreal] Add transaction and span set_data documentation (#14599)
  feat(js): Add `ignoreSpans` documentation to Options page (#14572)
  fix(js/browser): Amend user IP + `sendDefaultPii` change to v10 migration guide (#14609)
  fix: Fix broken AI banner due to invalid syntax (#14627)
  feat(partners)add-enablement-docs (#14095)
  Fix image path issue & add test coverage for new lightbox (#14616)
  feat(seer): update GHE setup to work with seer (#14617)
  fix(replay): Document searchable properties `screen` and alias `screens` (#14603)
  Update image handling (#14564)
  Update using-hooks.mdx (#14605)
  Godot: Document `disabled-in-editor-play` option (#14438)
  fix(Docs) redirect and deprecate old metrics pages (#14602)
  fix(relay): Update projects.mdx (#14606)
  ...

Author: codyde

app/globals.css

@@ -177,6 +177,6 @@ body {
 
 .onboarding-step .step-heading::before,
 .onboarding-step h2::before {
-  content: "Step " counter(onboarding-step) ": ";
+  content: 'Step ' counter(onboarding-step) ': ';
   font-weight: inherit;
 }

develop-docs/development-infrastructure/devservices.mdx

@@ -111,7 +111,7 @@ def example () -> None
 
 3. Bring a process to the foreground for debugging
 ``` sh
-devservices foreground taskbroker
+devservices foreground taskworker
 ```
 
 

develop-docs/frontend/using-hooks.mdx

@@ -35,7 +35,7 @@ callback.
 
 ### Using context
 
-The `useContext` hook provides a simpler implemtation option to share state and
+The `useContext` hook provides a simpler implementation option to share state and
 behavior compared to our previous uses of Reflux. When you need to create new
 sources of shared state, consider using context and `useContext` instead of Reflux.
 Additionally the [wormhole state management

develop-docs/sdk/data-model/envelopes.mdx

@@ -345,7 +345,7 @@ These limits are subject to future change and defined currently as:
 - *100MB* for a full envelope after decompression
 - *100MB* for all attachments combined
 - *100MB* for each attachment item
-- *1MB* for event (errors and transactions), span, and metric (statsd, buckets, meta) items.
+- *1MB* for event (errors and transactions), span, log, and metric (statsd, buckets, meta) items.
 - *100KB* for monitor check-in items
 - *50MB* for profile items
 - *10MB* for compressed replay item

docs/concepts/data-management/event-grouping/fingerprint-rules.mdx

@@ -8,7 +8,7 @@ description: "Learn about fingerprint rules, matchers for fingerprinting, how to
 
 Fingerprint rules (previously known as _server-side fingerprinting_) are configured with a config similar to [stack trace rules](../stack-trace-rules/), but the syntax is slightly different. The matchers are the same, but instead of flipping flags, a fingerprint is assigned and it overrides the default grouping entirely. Assigning a fingerprint can also refine the default grouping rather than overriding it, if the fingerprint includes the value `{{ default }}`.
 
-These rules can be configured on a per-project basis in **[Project] > Settings > Issue Grouping > Fingerprint Rules**. This setting has input fields where you can write custom fingerprinting rules. To update a rule:
+These rules can be configured on a per-project basis in **Project Settings > Issue Grouping > Fingerprint Rules**. This setting has input fields where you can write custom fingerprinting rules. To update a rule:
 
 1. Identify the match logic for grouping issues together.
 1. Set the match logic and the fingerprint for it.

docs/concepts/data-management/event-grouping/stack-trace-rules.mdx

@@ -8,7 +8,7 @@ description: "Learn how to use stack trace rules to group incoming events based
 
 Stack trace rules improve issue tracking by ensuring accurate grouping and better classification of stack frames as in-app or system. This helps focus on relevant code, reduces noise, and minimizes false positives. By tailoring rules to your project, you can streamline debugging and maintain consistency across teams or multiple applications.
 
-When you set stack trace rules (previously known as _grouping enhancements_) for grouping in Sentry, they influence the data that's fed into the grouping algorithm. These rules can be configured on a per-project basis by going to your project settings and then clicking on "Issue Grouping".
+When you set stack trace rules (previously known as _grouping enhancements_) for grouping in Sentry, they influence the data that's fed into the grouping algorithm. These rules can be configured on a per-project basis in **Project Settings > Issue Grouping > Stack Trace Rules**.
 
 Here are a few things to note about stack trace rules:
 

docs/concepts/search/searchable-properties/session-replay.mdx

@@ -22,7 +22,7 @@ Replay activity is calculated based on the number of errors, the number of ui ev
 
 ### `browser.name`
 
-Name of the users' web browser. For example, `Chrome`, `Firefox`, or `Safari`
+Name of the users' web browser. For example, `Chrome`, `Firefox`, or `Safari`.
 
 - **Type:** string
 
@@ -34,13 +34,13 @@ The version string of the browser.
 
 ### `click.alt`
 
-The `alt` of an element that was clicked. For example, `"a good dog"` would match the element `<img src="/lassie.jpeg" alt="a good dog" />`
+The `alt` of an element that was clicked. For example, `"a good dog"` would match the element `<img src="/lassie.jpeg" alt="a good dog" />`.
 
 - **Type:** string
 
 ### `click.class`
 
-The `class` of an element that was clicked. No leading `.` is necessary. For example, `btn-primary` would match the element `<a class="btn btn-primary">Save</a>`
+The `class` of an element that was clicked. No leading `.` is necessary. For example, `btn-primary` would match the element `<a class="btn btn-primary">Save</a>`.
 
 - **Type:** string
 
@@ -54,19 +54,19 @@ Note: This property requires that your project have [React component name captur
 
 ### `click.id`
 
-The `id` of an element that was clicked. No leading `#` is necessary. For example, `reset-password` would match the element `<a id="reset-password">Reset</a>`
+The `id` of an element that was clicked. No leading `#` is necessary. For example, `reset-password` would match the element `<a id="reset-password">Reset</a>`.
 
 - **Type:** string
 
 ### `click.label`
 
-The `aria-label` of an element that was clicked. For example, `Expand` would match the element `<button aria-label="Expand"><img src="/icons/expand.png"/></button>`
+The `aria-label` of an element that was clicked. For example, `Expand` would match the element `<button aria-label="Expand"><img src="/icons/expand.png"/></button>`.
 
 - **Type:** string
 
 ### `click.role`
 
-The `role` of an element that was clicked. For example, `button` would match both `<button>Save</button>` and `<a role="button">Submit</a>`
+The `role` of an element that was clicked. For example, `button` would match both `<button>Save</button>` and `<a role="button">Submit</a>`.
 
 - **Type:** string
 
@@ -78,25 +78,25 @@ An element identified using a subset of CSS selector syntax. For example, `#sect
 
 ### `click.tag`
 
-The tag name of an element that was clicked. For example, `input` would match `<input name="username" />`
+The tag name of an element that was clicked. For example, `input` would match `<input name="username" />`.
 
 - **Type:** string
 
 ### `click.testid`
 
-The `data-testid` or `data-test-id` of an element that was clicked. For example, `user-name` would match the element `<a data-testid="user-name">User Name</a>`
+The `data-testid` or `data-test-id` of an element that was clicked. For example, `user-name` would match the element `<a data-testid="user-name">User Name</a>`.
 
 - **Type:** string
 
 ### `click.textContent`
 
-The immediate `textContent` of an element that was clicked. For example, `Save` would match `<button>Save</button>` but wouldn't match `<button><h1>Save</h1></button>`
+The immediate `textContent` of an element that was clicked. For example, `Save` would match `<button>Save</button>` but wouldn't match `<button><h1>Save</h1></button>`.
 
 - **Type:** string
 
 ### `click.title`
 
-The `title` of an element that was clicked. For example, `Save this comment` would match the element `<a title="Save this comment" class="btn btn-primary">Save</a>`
+The `title` of an element that was clicked. For example, `Save this comment` would match the element `<a title="Save this comment" class="btn btn-primary">Save</a>`.
 
 - **Type:** string
 
@@ -144,7 +144,7 @@ Similar to the `click.selector` search property, but only queries on [dead click
 
 ### `device.brand`
 
-Brand of the device
+Brand of the device.
 
 - **Type:** string
 
@@ -162,7 +162,7 @@ Internal hardware revision to identify the device exactly.
 
 ### `device.name`
 
-Details of the device
+Details of the device.
 
 - **Type:** string
 
@@ -204,7 +204,7 @@ Severity of the event (such as: fatal, error, warning). Always set to info for t
 
 ### `os.name`
 
-The name of the operating system. For example, `Windows`, `Mac OS X`, or `Linux`
+The name of the operating system. For example, `Windows`, `Mac OS X`, or `Linux`.
 
 - **Type:** string
 
@@ -244,6 +244,11 @@ The reason a replay was triggered. For example, `session` when `replaysSessionSa
 
 - **Type:** string
 
+### `screen`
+
+A specific Screen or View that the user visited during the replay. You can also search for multiple Screens at once using `screens` and passing in an array of strings.
+Alias: `url`
+
 ### `sdk.name`
 
 Name of the Sentry SDK that sent the event.
@@ -272,6 +277,7 @@ A trace represents the record of the entire operation you want to measure or tra
 ### `url`
 
 A specific URL that the user visited during the replay. You can also search for multiple URLs at once using `urls` and passing in an array of strings.
+Alias: `screen`
 
 - **Type:** string
 
@@ -301,7 +307,7 @@ Full name of the country of the user's geolocation.
 
 ### `user.geo.subdivision`
 
-Full name of the subdivision of the user's geolocation. (For example, state, province, etc.)
+Full name of the subdivision of the user's geolocation. (For example, state, province, etc.).
 
 - **Type:** string
 

docs/organization/integrations/source-code-mgmt/github/index.mdx

@@ -138,11 +138,11 @@ Occasionally, Sentry will request additional permissions to your GitHub account
       </tr>
       <tr>
         <th>Pull Requests </th>
-        <td>Read-only </td>
+        <td>Read & Write </td>
       </tr>
       <tr>
         <th>Repository Contents </th>
-        <td>Read-only </td>
+        <td>Read & Write </td>
       </tr>
       <tr>
         <th>Single File </th>