arangodb
diff --git a/‎README.md‎
Lines changed: 19 additions & 0 deletions b/‎README.md‎
Lines changed: 19 additions & 0 deletions
diff --git a/‎site/content/amp/deployments/_index.md‎
Lines changed: 20 additions & 1 deletion b/‎site/content/amp/deployments/_index.md‎
Lines changed: 20 additions & 1 deletion
diff --git a/‎site/content/arangodb/3.10/develop/foxx-microservices/guides/authentication-and-sessions.md‎
Lines changed: 2 additions & 2 deletions b/‎site/content/arangodb/3.10/develop/foxx-microservices/guides/authentication-and-sessions.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎site/content/arangodb/3.10/index-and-search/indexing/index-utilization.md‎
Lines changed: 3 additions & 2 deletions b/‎site/content/arangodb/3.10/index-and-search/indexing/index-utilization.md‎
Lines changed: 3 additions & 2 deletions
@@ -429,6 +429,25 @@ Available attributes:
 - `class`: CSS classes to apply
 - `style`: CSS inline styles to apply
 
+#### Icons
+
+If a web interface uses icons, especially as buttons without labels, use
+the `icon` shortcode to inline an SVG file for a visual reference as
+demonstrated below:
+
+```markdown
+Select all nodes ({{< icon "select-all" >}}), then right-click.
+```
+
+Icons are supposed to supplement the text, i.e. not be embedded in sentences.
+They are hidden from screen readers.
+
+To add new icons to the toolchain, save them to `site/content/images/icons/`.
+They are referenced by file name (without extension) in the shortcode.
+
+SVG icon files should not define the attributes `width`, `height`, `aria-hidden`,
+and `focusable` on the `<svg>` tag.
+
 #### Keyboard shortcuts
 
 To document hotkeys and key combinations to press in a terminal or graphical
 
@@ -237,6 +237,11 @@ attached to your role. Read more about [roles and permissions](../security-and-a
    - Change the deployment name
    - Change the deployment description
 4. In the **Sizing** section, you can do the following:
+   
+   {{< tip >}}
+   Before changing deployment models, especially from **Single Server** to clustered configurations,
+   consider creating a backup of your data.
+   {{< /tip >}}
    - Change **OneShard** deployments into **Sharded** deployments. To do so,
      select **Sharded** in the **Model** dropdown list. You can select the
      number of nodes for your deployment. This can also be modified later on.
@@ -245,7 +250,12 @@ attached to your role. Read more about [roles and permissions](../security-and-a
      {{< /warning >}}
    - Change **Single Server** deployments into **OneShard** or **Sharded** deployments.
      {{< warning >}}
-     You cannot switch from **Sharded** or **OneShard** back to **Single Server**.
+     **Important considerations for Single Server upgrades:**
+     - You cannot switch from **Sharded** or **OneShard** back to **Single Server**.
+     - Changing **Single Server** deployments into **OneShard** or **Sharded** deployments
+       will cause downtime and may take a considerable amount of time to complete. Plan this switch
+       during a maintenance window when your application can tolerate service interruption.
+       Your data remains safe throughout the process.
      {{< /warning >}}
    - Scale up or down the node size.
      {{< warning >}}
@@ -284,6 +294,15 @@ application has to handle connection failures by retrying operations if needed.
 
 ## How to pause a deployment
 
+1. In the __Deployments__ page, click the deployment you wish to pause.
+2. Click the __Delete/Lock__ entry in the navigation.
+3. Click the __Pause deployment...__ button.
+4. To resume the deployment, go to the __Overview__ tab and click __Resume deployment__. The
+   deployment being paused displays the __Hibernated__ status until it has been
+   successfully resumed.
+
+## How to pause a deployment
+
 1. In the __Deployments__ page, click the deployment you wish to pause.
 2. Click the __Delete/Lock__ entry in the navigation.
 3. Click the __Pause deployment...__ button.
 
@@ -23,7 +23,7 @@ authentication.
 In this example we'll use two collections: a `users` collection to store the
 user objects with names and credentials, and a `sessions` collection to store
 the session data. We'll also make sure usernames are unique
-by adding a hash index:
+by adding a `persistent` index:
 
 ```js
 "use strict";
@@ -37,7 +37,7 @@ if (!db._collection(sessions)) {
   db._createDocumentCollection(sessions);
 }
 module.context.collection("users").ensureIndex({
-  type: "hash",
+  type: "persistent",
   unique: true,
   fields: ["username"]
 });
 
@@ -19,8 +19,9 @@ It is often beneficial to create an index on more than just one attribute. By ad
 to an index, an index can become more selective and thus reduce the number of documents that 
 queries need to process.
 
-ArangoDB's primary indexes, edges indexes and hash indexes will automatically provide selectivity
-estimates. Index selectivity estimates are provided in the web interface, the `indexes()` return 
+ArangoDB's `primary` and `edge` indexes automatically provide selectivity estimates.
+The `persistent`, `mdi`, and `mdi-prefixed` indexes do too, by default.
+Index selectivity estimates are provided in the web interface, the `indexes()` return 
 value and in the `explain()` output for a given query. 
 
 The more selective an index is, the more documents it will filter on average. The index selectivity