docs: remove duplicate multimodal page and normalize em/en-dashes (#6112)

docs/core-concepts/memory-operations/add.mdx

@@ -11,17 +11,17 @@ Adding memory is how Mem0 captures useful details from a conversation so your ag
 
 ## Key terms
 
-- **Messages** – The ordered list of user/assistant turns you send to `add`.
-- **Infer** – Controls whether Mem0 extracts structured memories (`infer=True`, default) or stores raw messages.
-- **Metadata** – Optional filters (e.g., `{"category": "movie_recommendations"}`) that improve retrieval later.
-- **User / Session identifiers** – `user_id`, `agent_id`, `app_id`, or `run_id` that scope the memory for future searches.
+- **Messages**: The ordered list of user/assistant turns you send to `add`.
+- **Infer**: Controls whether Mem0 extracts structured memories (`infer=True`, default) or stores raw messages.
+- **Metadata**: Optional filters (e.g., `{"category": "movie_recommendations"}`) that improve retrieval later.
+- **User / Session identifiers**: `user_id`, `agent_id`, `app_id`, or `run_id` that scope the memory for future searches.
 
 ## How does it work?
 
 Mem0 offers two flows:
 
-- **Mem0 Platform** – Fully managed API with dashboard and scaling.
-- **Mem0 Open Source** – Local SDK that you run in your own environment.
+- **Mem0 Platform**: Fully managed API with dashboard and scaling.
+- **Mem0 Open Source**: Local SDK that you run in your own environment.
 
 Both flows take the same payload and add memories through an additive pipeline.
 

docs/core-concepts/memory-operations/delete.mdx

@@ -18,10 +18,10 @@ Deleting memories is how you honor compliance requests, undo bad data, or clean
 
 ## Key terms
 
-- **memory_id** – Unique ID returned by `add`/`search` identifying the record to delete.
-- **batch_delete** – API call that removes up to 1000 memories in one request.
-- **delete_all** – Filter-based deletion by user, agent, run, or metadata.
-- **immutable** – Flagged memories that cannot be updated; delete + re-add instead.
+- **memory_id**: Unique ID returned by `add`/`search` identifying the record to delete.
+- **batch_delete**: API call that removes up to 1000 memories in one request.
+- **delete_all**: Filter-based deletion by user, agent, run, or metadata.
+- **immutable**: Flagged memories that cannot be updated; delete + re-add instead.
 
 ## How the delete flow works
 

docs/core-concepts/memory-operations/search.mdx

@@ -11,10 +11,10 @@ Mem0's search operation lets agents ask natural-language questions and get back
 
 ## Key terms
 
-- **Query** – Natural-language question or statement you pass to `search`.
-- **Filters** – JSON logic (AND/OR, comparison operators) that narrows results by user, categories, dates, etc.
-- **top_k / threshold** – Controls how many memories return and the minimum similarity score.
-- **Rerank** – Optional second pass that boosts precision when a reranker is configured.
+- **Query**: Natural-language question or statement you pass to `search`.
+- **Filters**: JSON logic (AND/OR, comparison operators) that narrows results by user, categories, dates, etc.
+- **top_k / threshold**: Controls how many memories return and the minimum similarity score.
+- **Rerank**: Optional second pass that boosts precision when a reranker is configured.
 
 ## Architecture
 

docs/core-concepts/memory-operations/update.mdx

@@ -11,12 +11,12 @@ Mem0’s update operation lets you fix or enrich an existing memory without dele
 
 ## Key terms
 
-- **memory_id** – Unique identifier returned by `add` or `search` results.
-- **text** / **data** – New content that replaces the stored memory value.
-- **metadata** – Optional key-value pairs you update alongside the text.
-- **timestamp** – Unix epoch (int/float) or ISO 8601 string to override the memory's timestamp.
-- **batch_update** – Platform API that edits multiple memories in a single request.
-- **immutable** – Flagged memories that must be deleted and re-added instead of updated.
+- **memory_id**: Unique identifier returned by `add` or `search` results.
+- **text** / **data**: New content that replaces the stored memory value.
+- **metadata**: Optional key-value pairs you update alongside the text.
+- **timestamp**: Unix epoch (int/float) or ISO 8601 string to override the memory's timestamp.
+- **batch_update**: Platform API that edits multiple memories in a single request.
+- **immutable**: Flagged memories that must be deleted and re-added instead of updated.
 
 ## How the update flow works