DOCS-3497: Update deploy software

Author: npentrel

docs/dev/reference/glossary/module.md

@@ -2,10 +2,10 @@
 title: Module
 id: module
 full_link:
-short_description: A module provides one or more modular resources, which add resource types or models that are not built into Viam.
+short_description: A module is a code package which provides one or more modular resources, which add resource types or models that are not built into Viam.
 ---
 
-A _module_ provides one or more {{< glossary_tooltip term_id="modular-resource" text="modular resources" >}}, which add {{< glossary_tooltip term_id="resource" text="resource" >}} {{< glossary_tooltip term_id="type" text="types" >}} or {{< glossary_tooltip term_id="model" text="models" >}} that are not built into Viam.
+A _module_ is a code package which provides one or more {{< glossary_tooltip term_id="modular-resource" text="modular resources" >}}, which add {{< glossary_tooltip term_id="resource" text="resource" >}} {{< glossary_tooltip term_id="type" text="types" >}} or {{< glossary_tooltip term_id="model" text="models" >}} that are not built into Viam.
 Modules run alongside `viam-server` as separate process, communicating with `viam-server` over UNIX sockets.
 
 You can [create your own module](/operate/get-started/other-hardware/) or [add existing modules from the Viam Registry](/operate/get-started/supported-hardware/).

docs/manage/fleet/reuse-configuration.md

@@ -15,7 +15,7 @@ languages: []
 viamresources: []
 platformarea: ["fleet"]
 level: "Beginner"
-date: "2024-08-09"
+date: "2025-02-07"
 # updated: ""  # When the tutorial was last entirely checked
 next: /manage/fleet/provision/setup/
 cost: "0"
@@ -39,7 +39,7 @@ You must be an [organization owner](/manage/manage/rbac/) to create fragments fo
 Start by configuring one of your machines.
 
 In the [Viam app](https://app.viam.com), use the **CONFIGURE** tab to build a configuration for all resources you want to use on all your machines.
-You can use all available resources except [triggers](/data-ai/data/advanced/alert-data/) in the configuration for your machine.
+You can use all available resources in the configuration for your machine except [triggers](/data-ai/data/advanced/alert-data/) which aren't supported.
 This means you can also use fragments inside a fragment.
 
 {{<imgproc src="/how-tos/one-to-many/config.png" resize="800x" class="fill" style="width: 400px" declaredimensions=true alt="Configuration builder UI">}}
@@ -48,7 +48,7 @@ This means you can also use fragments inside a fragment.
 {{% tablestep %}}
 **2. Copy the raw JSON**
 
-In your machine's **CONFIGURE** tab, switch to **JSON** and copy the raw JSON.
+In your machine's **CONFIGURE** tab, switch to **JSON** and copy the raw JSON configuration object.
 
 {{<imgproc src="/how-tos/one-to-many/raw-json.png" resize="700x" class="fill" style="width: 400px" declaredimensions=true alt="JSON subtab of the CONFIGURE tab">}}
 
@@ -79,7 +79,7 @@ If you want to edit the fragment later, do it from this screen.
 **4. Delete the original configuration (optional)**
 
 Now that the configuration is saved as a fragment, you can delete each resource in the original config from your machine and _replace the config with the fragment_ in the next step.
-By using the new fragment, all your machines will use the exact same configuration.
+By using the new fragment, this and every other machine you add the fragment to will use the exact same configuration.
 
 {{% /tablestep %}}
 {{< /table >}}
@@ -88,7 +88,7 @@ By using the new fragment, all your machines will use the exact same configurati
 
 With your fragment created, you can add it to all machines that should have it.
 
-In the following, you will see how to add a fragment manually. If you are working in a factory setting and need to set up devices before they reach the end user, you can also fragments while [provisioning](/manage/fleet/provision/setup/) your fleet.
+In the following steps, you will see how to add a fragment manually. If you are working in a factory setting and need to set up devices before they reach the end user, you can also use fragments to [provision](/manage/fleet/provision/setup/) your machines.
 
 {{< table >}}
 {{% tablestep %}}

docs/manage/software/deploy-software.md

@@ -5,7 +5,7 @@ weight: 30
 layout: "docs"
 type: "docs"
 images: ["/registry/module-puzzle-piece.svg"]
-description: You can use a fragment to deploy software packages and ML models to many machines, as well as to update deployed versions of those software packages and ML models.
+description: "Deploy code packages with machine control logic to one or more machines."
 languages: []
 viamresources: []
 platformarea: ["registry", "fleet"]
@@ -18,28 +18,29 @@ aliases:
 cost: "0"
 ---
 
-To deploy code or other software to individual machines:
+{{< glossary_tooltip term_id="module" text="Modules" >}} are code packages that provide most of the functionality on your machines: drivers, integrations, and control logic.
+
+The following steps show you how to create modules with control logic and how to deploy all modules over the air (OTA) to your machine:
 
 1. [Create a module with machine control logic](#create-a-module-with-machine-control-logic)
-2. [Create a fragment with the configuration for your machines](#create-a-fragment)
-3. [Add the fragment to your machines](#add-the-fragment-to-your-machines)
+2. [Create a configuration fragment with the modules for your machine](#create-a-fragment)
+3. [Add the fragment to one or more machines](#add-the-fragment-to-your-machines)
 
 ## Prerequisites
 
-This guide assumes that you have [at least one machine](/operate/get-started/setup/) with [configured hardware and software resources](/operate/get-started/supported-hardware/).
+Start by [setting up one machine](/operate/get-started/setup/).
 
 ## Create a module with machine control logic
 
-You can operate devices by running control logic on another device, for example using an app, or on the machine itself using a {{< glossary_tooltip term_id="module" text="module" >}}.
-If all your machine control logic runs on another device or server, move on to [Create a fragment](#create-a-fragment).
-
-If at least some of your machine control logic should run on your machine, place the control logic in a module by following these steps:
+While you can operate devices by running control logic on another device, for example using an app, you can also run control logic on the machine itself using a {{< glossary_tooltip term_id="module" text="module" >}}.
 
 {{% alert title="OTA updates for microcontrollers" color="note" %}}
-The following steps do not cover how to create a module with machine control logic for microcontrollers.
-For microcontrollers, see [Micro-RDK modules](/operate/get-started/other-hardware/micro-module/) and [Over-the-air firmware updates](/operate/get-started/other-hardware/micro-module/#over-the-air-updates) instead.
+The following steps cover how to create a module for machines running `viam-server`.
+For microcontrollers, see [Micro-RDK modules](/operate/get-started/other-hardware/micro-module/) and [Over-the-air firmware updates](/operate/get-started/other-hardware/micro-module/#over-the-air-updates).
 {{% /alert %}}
 
+Place the control logic in a module by following these steps:
+
 {{< table >}}
 {{% tablestep link="/operate/get-started/other-hardware/" %}}
 **1. Generate stub files**
@@ -79,7 +80,7 @@ When your new model gets added to your machine, its `reconfigure()` method gets
 If you want your control logic to run in a loop in the background, you can start this loop here.
 Be sure to also implement logic to handle subsequent calls to the reconfigure method gracefully.
 
-For example, in Python, start your logic in <FILE>src/main.py</FILE>:
+For example, in Python, start your logic in the `reconfigure()` method of <FILE>src/main.py</FILE>:
 
 ```python {class="line-numbers linkable-line-numbers" data-line="20-28"}
 # Add these imports
@@ -189,18 +190,19 @@ Your module will now be built, packaged and pushed to the Viam Registry.
 ## Create a fragment
 
 Viam has a built-in tool called _{{< glossary_tooltip term_id="fragment" text="fragments" >}}_ for using the same configuration on multiple machines.
-When deploying or updating software on many machines, you should use fragments.
+When deploying or updating software on many machines, you should use fragments to deploy your modules OTA to your machines.
 
-The following example creates a fragment with a camera and a servo, as well as with the [control logic module](#create-a-module-with-machine-control-logic).
+The following example starts with a machine with a camera and a servo and adds the [control logic module](#create-a-module-with-machine-control-logic).
+The resulting machine configuration gets used to create the fragment for reuse on other machines.
 
 {{< table >}}
 {{% tablestep link="/operate/get-started/supported-hardware/" %}}
 **1. Configure your software**
 
 Go to your [machine](#prerequisites) in the [Viam app](https://app.viam.com).
-Ensure all hardware and other resources your machine uses are configured.
+[Configure the hardware and software resources](/operate/get-started/supported-hardware/) you want to use on your machine.
 
-Add your control logic module.
+Then add your control logic module.
 
 {{<imgproc src="/how-tos/deploy-packages/add-package.png" resize="800x" class="fill aligncenter" style="width: 500px" declaredimensions=true alt="Configuration builder UI">}}
 
@@ -265,7 +267,7 @@ We only created this machine to easily generate the JSON config for the fragment
 
 ## Add the fragment to your machines
 
-Generally, you will use [provisioning](/manage/fleet/provision/setup/) to add this fragment to your machines.
+Generally, fragments are used with [provisioning](/manage/fleet/provision/setup/) to deploy and manage softwareon many machines.
 
 You can also add the fragment manually to the machines that need it: