Fixed content after review

Author: BenjaminDannegard

content/hardware/04.pro/boards/portenta-x8/tutorials/waves-fleet-managment/content.md

@@ -13,7 +13,7 @@ hardware:
 
 ## Overview
 
-In a production environment it is convenient to plan updates, and have control over when and which devices are updated. FoundriesFactory Waves is the feature for this. It allows you to easily define a group of Portenta X8s and then push updates to that specific group. This tutorial will show you how to define that group and how to construct a Wave that can then be pushed to a group.
+In a production environment it is convenient to plan updates, and have control over when and which devices are updated. FoundriesFactory® Waves is the feature for this. It allows you to easily define a group of Portenta X8s and then push updates to that specific group. The difference between standard updates and using Waves to update, is that the Wave update will promote targets to production by double signing them, which makes the updates more manageable and controllable. This tutorial will show you how to define that group and how to construct a Wave that can then be pushed to a group.
 
 ## Goals
 
@@ -28,8 +28,7 @@ In a production environment it is convenient to plan updates, and have control o
 - Arduino Create account
 - Arduino Pro Cloud Subscription. [Learn more about the Pro Cloud](https://www.arduino.cc/pro/hardware/product/portenta-x8#pro-cloud).
 - Foundries.io™ account (linked with the Pro Cloud subscription)
-- FoundriesFactory® ([Check the Getting Started tutorial](https://docs.arduino.cc/tutorials/portenta-x8/out-of-the-box))
-- Devices already attached to your Factory ([Check the Getting Started tutorial](https://docs.arduino.cc/tutorials/portenta-x8/out-of-the-box))
+- FoundriesFactory® and devices already attached to your Factory. ([Check the Getting Started tutorial](https://docs.arduino.cc/tutorials/portenta-x8/out-of-the-box))
 
 ## Instructions
 
@@ -58,9 +57,21 @@ fioctl keys copy-targets /absolute/path/to/root.keys.tgz /path/to/target.only.ke
 
 Now we can move on to creating our Wave.
 
-### Creating the Wave
+### Creating a Dummy Wave for Production Targets
 
-The command below will create a Wave that can then be pushed to our devices. To create a Wave, we will sign it with a key, here we will use the targets only key. Then we give the Wave a name, target number, and tag. The `target number` needs to correspond to the target that we want the Wave to contain for our devices. The `tag` can be set as production or development. 
+Before a Factory can start doing production OTAs, an initial production Targets file must be created. More information can be found [here](https://docs.foundries.io/latest/reference-manual/ota/production-targets.html). This can be done by creating a dummy wave with the command:
+```
+fioctl wave init -k /absolute/path/to/targets.only.key.tgz <wave-name> <target number> <tag>
+```
+We can use `populate-targets` as the Wave name. The `target number` needs to correspond to a target that exists in our Factory. The `tag` should be set as `production`. Then complete the Wave with:
+```
+fioctl wave  complete populate-targets
+```
+This creates a new targets.json file for production devices subscribing to the production tag. It will include a single Target from CI build.
+
+### Creating a Wave
+
+Now we can start creating our Wave. The command below will create a Wave that can then be pushed to our devices. To create a Wave, we will sign it with a key, here we will use the targets only key. Then we give the Wave a name, target number, and tag. The `target number` needs to correspond to the target that we want the Wave to contain for our devices. The `tag` can be set as production or development. 
 ```
 fioctl wave init -k /absolute/path/to/targets.only.key.tgz <wave-name> <target number> <tag>
 ```