fix: address release v2 review findings (#6708)

apps/docs/docs/management/api/index.mdx

@@ -115,6 +115,8 @@ The OpenAPI and MCP APIs include board management endpoints for common automatio
 
 Board layout responses identify each layout with a `mobile`, `base`, or `custom` role. Mobile and Base are protected. Layout-saving clients must preserve existing roles, keep Mobile at breakpoint `0`, keep Base as the highest breakpoint, and use unique custom breakpoints between them. The layout save operation returns the canonical saved layouts, including server-generated IDs for new custom layouts. A non-Base layout can be regenerated from Base with the protected reset operation.
 
+The internal `board.getManageOverview` tRPC query returns compact board previews limited to 12 layout rows by default. Callers may provide `previewRowLimit` from 1 through 48; `fullPreview: true` requests the server's 48-row maximum.
+
 Use the interactive API reference to inspect the exact request body for each endpoint under the `boards` and `settings` tags.
 
 ## Docker action payload migration

apps/docs/docs/management/settings/index.mdx

@@ -128,6 +128,26 @@ You can decide if app status is disabled on all boards.
 
 You can set the default color scheme for users without their own color scheme.
 
+## Branding
+
+Branding settings let administrators adapt Homarr to the identity and visual style of their installation. Changes apply across the application and authentication pages after you save the settings.
+
+### Identity
+
+- **Application name** replaces the default Homarr name in page titles and branded surfaces.
+- **Logo** is used in the header and other application branding.
+- **Favicon** controls the browser tab icon. When it is empty, Homarr falls back to the configured logo.
+
+### Colors and corners
+
+Choose the primary and secondary colors used by the theme. **Lock primary color** prevents users from overriding the configured primary color. **Default corner style** controls the global radius used by cards, controls, and other interface elements.
+
+### Sign-in page
+
+You can set a greeting and a background image for authentication pages. The overlay slider adjusts the contrast between the background and the sign-in content. The visibility controls independently show or hide the application name, logo, and greeting.
+
+Use an image URL that every user can load before signing in. A URL that requires an authenticated Homarr session will not work on the sign-in page.
+
 ## Culture
 
 ### Default language

apps/docs/docs/widgets/iframe/index.mdx

@@ -67,6 +67,8 @@ add_header Content-Security-Policy "frame-ancestors 'self' https://trusted-domai
 - **Wikipedia homepage:** https://en.wikipedia.org/wiki/Main_Page
 - **Any YouTube video or stream:** https://www.youtube.com/embed/dQw4w9WgXcQ?si=MWUbbG66UNTla_Ni
 
+Homarr passes the configured URL directly to the browser. The iframe sandbox and configured permissions still apply.
+
 ### Configuration
 
 <WidgetConfig configuration={iframeWidget.configuration} />