Move feature comparison table to the customize overview (#414)

* Move feature comparison table to the customize overview

The "Choosing the right feature" table lived on the context parameter
guide, where it compared context against customization features. Move
it to the customize overview, split custom instructions into its own
column, and add translation memories. The context guide now links to
the table instead.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* Put the context parameter last in the comparison table

Lead with the customization features since this is their overview page,
and introduce the context parameter as the non-customization extra
rather than framing the section around it.

* Reword the comparison table intro

* Drop redundant link location from the context guide

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: shirgoldbird

docs/customize/overview.mdx

@@ -23,6 +23,20 @@ Glossaries, style rules, custom instructions, and translation memories work with
 Glossaries and style rules are unique to each of DeepL's global data centers and are not shared between them. Clients using [regional endpoints](/docs/getting-started/regional-endpoints) can't access glossaries or style rules created in the UI at this time.
 </Warning>
 
+## Choosing the right feature
+
+Here's when to use each customization feature for the best results. The [`context` parameter](/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter) can also be used to improve translations of ambiguous or short text.
+
+| Use case | Glossaries | Style rules | Custom instructions | Translation memories | Context parameter |
+| :---- | :----: | :----: | :----: | :----: | :----: |
+| **Consistent domain-specific terminology** | ✅ | ❌ | ❌ | ❌ | ❌ |
+| **Brand and product names** | ✅ | ❌ | ❌ | ❌ | ❌ |
+| **Formatting conventions (dates, numbers, punctuation)** | ❌ | ✅ | ❌ | ❌ | ❌ |
+| **Tone and phrasing** | ❌ | ❌ | ✅ | ❌ | ❌ |
+| **Reusing previously approved translations** | ❌ | ❌ | ❌ | ✅ | ❌ |
+| **Ambiguous words or short snippets** | ❌ | ❌ | ❌ | ❌ | ✅ |
+| **Consistent gender or name spelling** | ❌ | ❌ | ❌ | ❌ | ✅ |
+
 ## Feature guides
 
 <CardGroup cols={2}>

docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter.mdx

@@ -7,7 +7,7 @@ public: true
 **This guide shows you:**
 - When to use `context` (and when not to)
 - How to use `context` to resolve ambiguous words, genders, or transliterations
-- How to choose between `context`, Glossaries, and Style Rules
+- Where to find a comparison of `context` with DeepL's customization features
 
 ---
 
@@ -225,19 +225,9 @@ curl -X POST 'https://api.deepl.com/v2/translate' \
 
 ---
 
-## Choosing the right feature for your needs
+## Choosing the right feature
 
-Different DeepL features solve different problems. Use this table to decide which best suits your use case.
-
-| Use Case | Context Parameter | Glossaries | Style Rules |
-|----------|:----------------:|:----------:|:-----------:|
-| **Ambiguous words** | ✅ | ❌ | ❌ |
-| **Consistent gender or spelling** | ✅ | ❌ | ❌ |
-| **Consistent domain-specific terminology** | ❌ | ✅ | ❌ |
-| **Brand names** | ❌ | ✅ | ❌ |
-| **Tone and style** | ❌ | ❌ | ✅ |
-| **Formatting rules** | ❌ | ❌ | ✅ |
-| **Translation instructions** | ❌ | ❌ | ✅ |
+The `context` parameter is one of several ways to influence translation output. For a comparison of `context` with glossaries, style rules, custom instructions, and translation memories, see [Choosing the right feature](/docs/customize/overview#choosing-the-right-feature).
 
 ---