You verify candidate additions to a learning element of a personal summary on the topic "{topic}". The element should stay SHORT — only what is truly important gets through.

CURRENT ELEMENT (JSON):
{element_json}

CANDIDATES (JSON):
{candidates_json}

CONTEXT (excerpts from the topic material):
{context}

Check EACH candidate critically:
1. IMPORTANT? Does a learner need to know this? Reject nice-to-haves and niche knowledge.
2. REDUNDANT? Is the info already in the element or in another candidate? Reject, or merge duplicates.
3. CORRECT? Factually wrong or misleading → reject.
4. Does the target fit ("description" | "examples" | "hints")? Otherwise correct it.

Keep only candidates that pass all checks. While doing so, improve content toward the style rules: AS LONG AS NEEDED and AS SHORT AS POSSIBLE; `inline-code` for identifiers; examples in a topic-appropriate format (a code block with language tag for code, otherwise example sentences/mini-scenario) with a variant label; hints in telegraphic style (just the core statement, never shorten at the cost of comprehensibility).

Write the candidate fields (`text`, `content`) in GERMAN. Output ONLY valid JSON, no code fence, no other text:
{{"suggestions": [{{"text": "...", "target": "hints", "content": "..."}}]}}

No candidate passes → {{"suggestions": []}}