move things around and add content on restore from backup

modules/ROOT/pages/managing-instances/instance-details.adoc

@@ -2,10 +2,14 @@
 = Instance details
 :description: This page describes the instance details.
 
-From the instance card, select the more menu *(…​)* then select *instance details*.
-Apart from viewing the instance details, you can also rename your instance using the pen icon next to the instance name.
+From the instance card, select the more menu *(…​)* then select *Inspect*.
+From here you can see an Overview of the instance details, Snapshots, Restore from backup file, or see the logs.
 
-image::instancedetailsexpanded.png[]
+== Overview
+
+In the Overview, apart from viewing the instance details, you can also rename your instance using the pen icon next to the instance name.
+
+image::inspectdetails.png[]
 
 
 .Instance details
@@ -45,17 +49,8 @@ Backups are saved in the storage bucket of the cloud provider in the same region
 
 |===
 
-
-== Snapshots
-
-The data in your instance can be backed up, exported, and restored using snapshots.
-A snapshot is a copy of the data in an instance at a specific point in time.
-
-Neo4j regularly takes snapshots of your instance, and you can also take a snapshot on demand.
-These snapshots can be used to restore data to a different Neo4j instance.
-
 [[aura-vector-optimization]]
-== Vector optimization
+=== Vector optimization
 
 label:AuraDB-Professional[]
 label:AuraDB-Business-Critical[]
@@ -81,56 +76,67 @@ To learn more about how to use vector indexes, see link:https://neo4j.com/docs/c
 
 === Instance sizing guide
 
-The vector optimized configuration is intended to allow an Aura instances' available storage to be completely filled and still provide consistent vector search performance. 
-The table below shows the theoretical maximum GiB of vectors for each instance size, and the equivalent number of 768 dimension float-32 vectors. 
+The vector optimized configuration is intended to allow an Aura instances' available storage to be completely filled and still provide consistent vector search performance.
+The table below shows the theoretical maximum GiB of vectors for each instance size, and the equivalent number of 768 dimension float-32 vectors.
 
 [cols="1,1,2"]
 |===
-|Aura Instance Size |GiB vectors |Million vectors (768 dimensions)  
+|Aura Instance Size
+|GiB vectors
+|Million vectors (768 dimensions)
 
 |4GB
-|2.8 
+|2.8
 |0.9
 
 |8GB
-|5.6 
+|5.6
 |1.8
 
 |16GB
-|11.2 
+|11.2
 |3.6
 
 |32GB
-|22.4 
+|22.4
 |7.3
 
 |64GB
-|44.9 
+|44.9
 |14.6
 
 |128GB
-|89.8 
+|89.8
 |29.2
 
 |256GB
-|179.6 
+|179.6
 |58.4
 
 |512GB
-|359.3 
+|359.3
 |116.9
 
-|=== 
+|===
+
+GiB vectors is limited by available storage.
+As larger stores become available, you can increase the vector capacity for these instances.
+
+== Snapshots
+
+The data in your instance can be backed up, exported, and restored using snapshots.
+A snapshot is a copy of the data in an instance at a specific point in time.
+
+Neo4j regularly takes snapshots of your instance, and you can also take a snapshot on demand.
+These snapshots can be used to restore data to a different Neo4j instance.
 
-GiB vectors is limited by available storage. 
-As larger stores become available, we can increase the vector capacity for these instances.
 
-// == Import instance
+== Restore from backup file
 
-// _Feature coming soon!_
+You can restore a database to your instance by dragging and dropping it to this tab.
+It needs to be either a *.dump*, *.backup*, or *.tar* file.
+When you restore a database, all existing data is overwritten by your selected file.
 
 // == Logs
 
-// If something goes wrong, the logs are a good place to start.
-// The standard log is called `neo4j.log` and it contains general information about Neo4j.
-// There is one for each DBMS and it can be accessed directly from Desktop via the Developer menu. It opens in a separate window, which allows you to keep it in the background.
+// From the _Logs_ tab, you can request Query logs for a specified time frame.