update

Author: sentrivana

develop-docs/sdk/platform-specifics/python-sdk/backporting.mdx

@@ -1,12 +1,12 @@
 ---
 title: Backporting
 description: How to backport to an earlier major.
-sidebar_order: 20
+sidebar_order: 10
 ---
 
 The last normal 1.x release was [1.45.0](https://github.com/getsentry/sentry-python/releases/tag/1.45.0) in April 2024. Development on 1.x has stopped — we are not backporting any features or bugfixes outside of security fixes.
 
-If there is a security issue in the SDK severe enough that it needs a backport to 1.x (see for example [1.45.1](https://github.com/getsentry/sentry-python/releases/tag/1.45.1)):
+If there is a security issue in the SDK severe enough (use your judgement) that it needs a backport to 1.x (see for example [1.45.1](https://github.com/getsentry/sentry-python/releases/tag/1.45.1)):
 
 - Checkout the `1.x` branch
 - Port the fix into the `1.x` branch

develop-docs/sdk/platform-specifics/python-sdk/ci.mdx

@@ -1,11 +1,9 @@
 ---
 title: CI
-description: How our CI files are generated and general caveats.
-sidebar_order: 30
+description: Our test setup and how our CI files are generated.
+sidebar_order: 20
 ---
 
-## Our Test Setup
-
 The GitHub workflow files for testing specific integration groups (like AI, Web Frameworks, Databases, etc.) are generated by [this script](https://github.com/getsentry/sentry-python/blob/master/scripts/split-tox-gh-actions/split-tox-gh-actions.py). Essentially, the script scans our `tox.ini` and generates the group test CI YAML files in `.github/workflows`.
 
 There are multiple components to this:
@@ -22,4 +20,4 @@ The AWS Lambda test suite will fail by default on new PRs. If you are an externa
 
 Sensitive test suites (currently only AWS Lambda) require maintainer review to ensure that tests do not compromise our secrets. This review must be repeated after any code revisions.
 
-Before running sensitive test suites, maintainers need to carefully check the PR. Then they will apply the Trigger: tests using secrets label. The label will be removed after any code changes to enforce our policy requiring maintainers to review all code revisions before running sensitive tests.
+Before running sensitive test suites, maintainers need to carefully check the PR. Then they will apply the `Trigger: tests using secrets` label. The label will be removed after any code changes to enforce our policy requiring maintainers to review all code revisions before running sensitive tests.

develop-docs/sdk/platform-specifics/python-sdk/feature-branches.mdx

@@ -1,7 +1,7 @@
 ---
-title: Feature branches
-description: How-to for syncing feature branches.
-sidebar_order: 40
+title: Feature Branches
+description: How-to for syncing long-running feature branches.
+sidebar_order: 30
 ---
 
 Sometimes we have long-running feature branches that can't be merged into `master` yet because they contain breaking changes (e.g. `sentry-sdk-2.0`, `potel-base`). They have to be kept in sync with `master` though.

…atform-specifics/python-sdk/api-docs.mdx …ifics/python-sdk/generating-api-docs.mdxdevelop-docs/sdk/platform-specifics/python-sdk/api-docs.mdx renamed to develop-docs/sdk/platform-specifics/python-sdk/generating-api-docs.mdx develop-docs/sdk/platform-specifics/python-sdk/api-docs.mdx renamed to develop-docs/sdk/platform-specifics/python-sdk/generating-api-docs.mdx

@@ -1,7 +1,7 @@
 ---
-title: Generating API docs
-description: How to deal with Sphinx issues.
-sidebar_order: 10
+title: Generating API Docs
+description: How to deal with issues generating our API docs.
+sidebar_order: 40
 ---
 
 ## Problem