clarify narrative

Backport from version to be used in UI; clarify which combinations of
inputs are not supported in the Marxan Cloud platform.

docs/download-upload-clone/legacy-marxan-projects/use-cases-and-available-features.md

@@ -37,45 +37,48 @@
 
 ## Functionality available depending on data supplied by the user
 
-- a+b (planning unit grid and input db)
+### When uploading planning unit grid and input db (a+b)
 
-In this use case, for example, users may be transitioning a legacy project to
-the Marxan MaPP platform, rather than making it available as an historical
-archive.
+This may be the case when users are transitioning a legacy project to the Marxan
+MaPP platform (rather than making it available as an historical archive, for
+example).
 
-Users will not be able to add, remove or combine (split/stratification)
-features; the exact spatial distribution of features will not be available for
-display; planning unit lock status will be set from input `pu.dat` but without
-first adding spatial data for protected areas, users won't be able to rely on
-protected areas to set the default lock status of planning units.
+The following limitations will apply:
 
-- a+b+c (planning unit grid, input db and output db)
+- users will not be able to add, remove or combine (split/stratification)
+  features;
+- the exact spatial distribution of features will not be available for display;
+- planning unit lock status will be set from input `pu.dat`, but without first
+  adding spatial data for protected areas, users won't be able to rely on
+  protected areas to set the default lock status of planning units.
 
-In this use, for example, users may intend to upload a historical project to be
-shared in its archived state.
+### When uploading planning unit grid, input db and output db (a+b+c)
 
-Identical limitations to what was described in the previous use case will apply
-(in case users wish to continue working on the project within the Marxan MaPP
-platform); output data may be locked (i.e. running Marxan will be disallowed)
-if the user wishes to preserve a historical record of solutions calculated
-outside of the Marxan MaPP platform.
+This may be the case when users intend to upload a historical project to be
+shared in its archived state.
 
+- identical limitations to what was described in the previous use case will
+  apply (in case users wish to continue working on the project within the Marxan
+  MaPP platform);
+- output data may be locked (i.e. running Marxan will be disallowed) if the user
+  wishes to preserve a historical record of solutions calculated outside of the
+  Marxan MaPP platform.
 
-- a+b+c+d+e (planning unit grid, input db, output db and feature data)
+## When uploading planning unit grid, input db, output db and feature data (a+b+c+d+e)
 
-In this use case, for example, users may intend to transition to using Marxan
-MaPP for an existing project for which extensive source data is available; they
-may wish to showcase an historical record of the project as created outside of
-Marxan MaPP (by keeping the original output solutions intact), while working on
-a copy of the original project as a new scenario or set of scenarios, adding any
-further spatial data directly within the Marxan MaPP platform.
+This may be the case when users intend to transition to using Marxan MaPP for an
+existing project for which extensive source data is available; they may wish to
+showcase an historical record of the project as created outside of Marxan MaPP
+(by keeping the original output solutions intact), while working on a copy of
+the original project as a new scenario or set of scenarios, adding any further
+spatial data directly within the Marxan MaPP platform.
 
 With the data supplied at project import stage, some limitations will still
 apply (for example, default lock status from protected areas, until a protected
 area shapefile is uploaded in a cloned scenario) but the imported legacy project
 will largely be functional like a native Marxan MaPP project.
 
-- a+c (planning unit grid and output db)
+### When uploading planning unit grid and output db (a+c)
 
 **This combination is _not_ supported in the current version of the MarxanCloud
 platform. Input files are _always_ required.**
@@ -90,8 +93,7 @@ some of the maps where no suitable data is available to plot them.
 The project's solutions will be available as an archived historical artifact for
 reference.
 
-- a+c+d+e (planning unit grid, output db, all feature data and cost surface
-  data)
+### When importing planning unit grid, output db, all feature data and cost surface data (a+c+d+e)
 
 **This combination is _not_ supported in the current version of the MarxanCloud
 platform. Input files are _always_ required.**