docs(features): Save sits last in the toolbar, panes switch with tabs

features/connection-window.mdx

@@ -15,9 +15,9 @@ Eight controls, laid out by pane: the sidebar toggle over the sidebar, the conne
 | Connection | The engine's glyph and the connection's name. Click for the [connection switcher](/connections#switch-connections-and-databases) (`Ctrl+Cmd+C`) |
 | Database | The database this window is browsing. Click for the list (`Cmd+K`) |
 | Refresh | Reloads what the tab is showing (`Cmd+R`) |
-| Save Changes | Commits the tab's staged changes (`Cmd+S`) |
 | Actions | The rest of the commands for this tab and this connection |
 | Safe Mode | A padlock carrying the current [level](/features/safe-mode), open for **Silent** and closed for **Read-Only** |
+| Save Changes | Commits the tab's staged changes (`Cmd+S`), in a section of its own |
 | Inspector | Opens and closes the [trailing pane](#the-trailing-pane) (`Cmd+Option+I`) |
 
 Two of them change their name. The database control follows the engine's own word: **Schema** on [Oracle](/databases/oracle), **Catalog** on [Trino](/databases/trino), **Keyspace** on [Cassandra](/databases/cassandra). The commit control follows the tab: **Create Table** on a new table's tab, **Apply Changes** on [Users & Roles](/features/users-roles), **Save Changes** everywhere else.

features/table-structure.mdx

@@ -254,7 +254,7 @@ Lists partitions and parts from `system.parts`. **Optimize** merges parts; **Dro
 
 ## Creating a new table
 
-Click **+** at the foot of the sidebar and choose **New Table…**, or choose **Database > New Table…**. The tab holds a **Table Name** field, a **Comment** field on engines that store table comments (with Engine, Charset, and Collation pickers on MySQL and MariaDB), the same three editing grids, and a **SQL Preview** tab carrying the live statements it will run. **Create Table** (`Cmd+Enter` or `Cmd+S`) executes it and opens the new table. Where the engine cannot roll DDL back, as on MySQL, a statement that fails after `CREATE TABLE` leaves the table created: it opens on its Structure tab with the error, so finish the change there.
+Click **+** at the foot of the sidebar and choose **New Table…**, or choose **Database > New Table…**. The tab holds a **Table Name** field, a **Comment** field on engines that store table comments (with Engine, Charset, and Collation pickers on MySQL and MariaDB), the same three editing grids as tabs, each with its own **+** and **−** at its foot, and a **SQL Preview** tab carrying the live statements it will run. **Create Table** (`Cmd+Enter` or `Cmd+S`) executes it and opens the new table. Where the engine cannot roll DDL back, as on MySQL, a statement that fails after `CREATE TABLE` leaves the table created: it opens on its Structure tab with the error, so finish the change there.
 
 On the **Foreign Keys** grid, **Columns**, **Ref Table**, and **Ref Columns** open menus of the new table's own columns, the database's tables, and the referenced table's columns. Each menu ends in **Custom…** for a name the list does not carry, and picking a second entry in a comma-separated cell appends to it.
 

features/users-roles.mdx

@@ -46,7 +46,7 @@ Toggling a checkbox stages a change, marked on the account, the object, and the
 
 ## Account attributes
 
-The **Privileges / Attributes** switch opens a form for the account itself: whether it can log in, role attributes such as `SUPERUSER` or `CREATEDB` on PostgreSQL, role membership (**Member of**, with **Edit…** for a checklist), and the connection limit. These stage and apply with everything else.
+The **Attributes** tab opens a form for the account itself: whether it can log in, role attributes such as `SUPERUSER` or `CREATEDB` on PostgreSQL, role membership (**Member of**, with **Edit…** for a checklist), and the connection limit. These stage and apply with everything else.
 
 On SQL Server, **Can log in** enables or disables the login; on Oracle it unlocks or locks the account. A role there never logs in, so the switch is off for roles.