Removed references to NeSI name

docs/user-guides/launch-and-manage-instances/with_the_dashboard/launch-an-instance-via-dashboard.md

@@ -1,15 +1,15 @@
 ---
 hidden: false
 label_names:
 - instance
 - launch
 position: 2
 title: Launch an Instance via Dashboard
 vote_count: 1
 vote_sum: 1
 ---
 
-Log into the [NeSI FlexiHPC Dashboard](https://dashboard.cloud.nesi.org.nz/)
+Log into the [FlexiHPC Dashboard](https://dashboard.cloud.nesi.org.nz/)
 
 Select the project you would like to deploy the new instance too (Use the project selector on the top left-hand side):
 
@@ -78,7 +78,7 @@
 !!! note
     Instance sizes have a brief explanation in the name of what they are best used for.
 
     Example `compute1.1cpu2ram` is best for Compute heavy workloads with 1 vCPU and 2 GB of RAM or `memory1.1cpu4ram` is best for Memory heavy workloads with 1 vCPU and 4 GB of RAM
 
 **Networks**
 
@@ -86,9 +86,9 @@
 :   To add a network to the instance, click the `^` in the Available field.
 
 !!! note
-    If you haven't configured a network prior to the creation of a compute instance then the recommend network should be the one that has the same name as the project you are in. Example, I am in the `NeSI-SandBox-Environment` so I will pick the `NeSI-SandBox-Environment` network.
+    If you haven't configured a network prior to the creation of a compute instance then the recommend network should be the one that has the same name as the project you are in. Example, I am in the `SandBox-Environment` so I will pick the `SandBox-Environment` network.
 
     You shouldn't need to add the instance to an external network as a floating IP will be added later on should you need to access the instance from outside the FlexiHPC network.
 
 **Network Ports**
 
@@ -103,13 +103,13 @@
 If you have not created any security groups, you can assign only the default security group to the instance.
 
 !!! note
     By default the `default` security group is added to all instances. This is required should the instance want to communicate to the outside world or to any other instance within the FlexiHPC project.
 
     How to create `Security Groups` are explained here How to add/update and remove security groups
 
 **Key Pair**
 
 Specify a key pair that is associated with your FlexiHPC user login. If there is none available then you can create one by clicking `Create key Pair`
 
 If the image uses a static root password or a static key set (neither is recommended), you do not need to provide a key pair to launch the instance.
 
@@ -119,20 +119,20 @@
 **Configuration**
 
 `Customization Script Source`
 :   Specify a customization script that runs after your instance launches. This can either be applied by uploading a file from your local machine or entered manually within the textbox provided.
 
 **Server Groups**
 
 Server groups determine the Policy that FlexiHPC should apply during the deployment of the instance in regards to other servers within the same group.
 
 !!! info
     By default an instance doesn't need to be in a Server Group, however should you want to apply policies to your servers then please read Server Groups within FlexiHPC to create a Server Group and also understand each policy.
 
     Server Group should be created prior to the creation of the instance if so required.
 
 **Scheduler Hints**
 
 These are tags or labels that tell the underlying FlexiHPC on where to deploy an instance. An example would be, If your workload or instance requires an intel based processor then you would apply the corresponding Scheduler Hint to the instance so it is only deployed to intel based processors.
 
 **Metadata**