For #64.
Problem
docs/user-guide/client-management/downgrading-a-plan.md references 4 distinct concepts across two recycled images.
docs/user-guide/client-management/downgrading-a-plan.md
L16 
L20 
L26 
L38 
Captures required
Setup: a customer subscribed to a higher-tier plan with a lower-tier plan available in the same plan group. From the customer subsite, initiate a downgrade; do not finalise it so the pending change state is visible.
| # |
Doc line |
Capture target |
New filename |
| 1 |
L16 |
Customer account page Your Membership card with Change button (share filename with upgrading-a-plan.md issue) |
static/img/account-page/membership-change-button.png |
| 2 |
L20 |
Downgrade plan-options page on the customer side |
static/img/account-page/downgrade-picker.png |
| 3 |
L26 |
Account page showing the pending membership change banner |
static/img/account-page/pending-change.png |
| 4 |
L38 |
Network Admin → Settings → Sites: Post-limit-exceeded behaviour options |
static/img/config/settings-sites-post-limit.png |
Capture at 1280×800, crop to the relevant card. < 200 KB.
Doc edit
Update every line in docs/user-guide/client-management/downgrading-a-plan.md to its new path and refine alt text.
Done when
For #64.
Problem
docs/user-guide/client-management/downgrading-a-plan.mdreferences 4 distinct concepts across two recycled images.Captures required
Setup: a customer subscribed to a higher-tier plan with a lower-tier plan available in the same plan group. From the customer subsite, initiate a downgrade; do not finalise it so the pending change state is visible.
upgrading-a-plan.mdissue)static/img/account-page/membership-change-button.pngstatic/img/account-page/downgrade-picker.pngstatic/img/account-page/pending-change.pngstatic/img/config/settings-sites-post-limit.pngCapture at 1280×800, crop to the relevant card. < 200 KB.
Doc edit
Update every line in
docs/user-guide/client-management/downgrading-a-plan.mdto its new path and refine alt text.Done when
docs/user-guide/client-management/downgrading-a-plan.mdupdated.Resolvesfor this issue andRef #64.