Condense a supplied deprecation notice so affected users can see whether they must act and by when. Preserve the distinction between a warning, a scheduled removal, and an operation that already fails.

Lead with the retiring feature or interface and the affected users. Keep deprecation and removal dates, including timezones when supplied. State the replacement and the minimum documented migration step. Preserve differences in replacement behavior, compatibility periods, and exceptions that could change a user's plan.

Remove organizational history, repeated encouragement, and reasons that do not affect the decision. Retain a reason when it explains a constraint, such as a protocol incompatibility. Keep exact names, paths, version numbers, and supplied migration links.

Output a short notice with Affected, Deadline, and Action when useful. Do not invent a grace period, assume that all users are affected, call the replacement equivalent without evidence, or imply that removal has happened before its stated date.