Reformatted structure

Author: Donna-Marie Smith

content/en/docs/2025.3/Guides/user-guides/user-interfaces/gateway/Admin/studio-export/_index.md

@@ -21,10 +21,16 @@ Studio Export is a feature that enables one or more flows to be exported into a
 
 Any flow in the system may be exported; it is not necessary for the administrator to have View or Edit authorisation for the flows to be exported.
 
+## Actions
+
+### Export Flows
+
 Individual flows are selected by clicking the checkbox in the `Export?` column adjacent to the flow to be exported. If a group is selected, then all the flows contained in that group, and any sub-groups, will be implicitly set; any implicitly set may be individually deselected by clicking the checkbox adjacent to the flow.
 
 Clicking `Export` will create the Studio Package from the Master Versions in the Master Repository of the selected flows, including their group hierarchy, and then download the package to the host’s browser as a file named `export.studiopkg` or `export <n>.studiopkg`, where `<n>` represents an integer to avoid naming conflict with other Studio Package files contained in the same folder.
 
+See the [Export Individual Flows][Export Individual Flows tutorial] tutorial for a step-by-step guide.
+
 ## Remarks
 
 ### Known Limitations

content/en/docs/2025.3/Guides/user-guides/user-interfaces/gateway/Admin/studio-import/_index.md

@@ -19,14 +19,6 @@ Studio Import is a feature that enables individual flows, contained in a Studio
 
 {{< figure src="/images/Studio Import.png" title="Studio Import" >}}
 
-Individual flows contained in the Studio Package may be individually selected for importing into {{% ctx %}} Studio; it is not a requirement that all the flows contained in the Studio Package are imported simultaneously.
-
-When the selected flows from the Studio Package are imported, they will become the Master Version of the flows in the destination Master Repository, replacing any existing Master Versions.
-
-After importing the flows, it is necessary to check the authorisation assigned to imported flows is appropriate for their use.
-
-See the [Import Individual Flows][Import Individual Flows tutorial] tutorial for a step-by-step guide.
-
 ## Actions
 
 ### Favoured Hierarchy
@@ -39,6 +31,16 @@ Alternatively, it is possible to have the display favour the `package hierarchy`
 
 The `Edit import hierarchy`, enables any individual imported flows to be assigned to any Group in the hierarchy of the destination {{% ctx %}} Studio. The display will show the entire existing hierarchy of the destination {{% ctx %}} Studio, extended by any necessary Groups from the Studio Package hierarchy where the imported flows do not already exist on the destination {{% ctx %}} Studio; it is not necessary for the administrator to have View or Edit authorisation for any flows to view the entire system Group hierarchy.
 
+### Import
+
+Individual flows contained in the Studio Package may be individually selected for importing into {{% ctx %}} Studio; it is not a requirement that all the flows contained in the Studio Package are imported simultaneously.
+
+When the selected flows from the Studio Package are imported, they will become the Master Version of the flows in the destination Master Repository, replacing any existing Master Versions.
+
+After importing the flows, it is necessary to check the authorisation assigned to imported flows is appropriate for their use.
+
+See the [Import Individual Flows][Import Individual Flows tutorial] tutorial for a step-by-step guide.
+
 ## Remarks
 
 ### Known Limitations