From 628c72f30c4f108e756f4941c0877dc206ae6903 Mon Sep 17 00:00:00 2001
From: Scott Carter <89930327+dlz-scarter@users.noreply.github.com>
Date: Fri, 21 Jun 2024 12:31:50 -0400
Subject: [PATCH] Clarity on -PackagePath parameter

The way this section is presently written, it can be assumed that the -PackagePath parameter only works for offline servicing
---
 docset/winserver2022-ps/dism/Add-AppxProvisionedPackage.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docset/winserver2022-ps/dism/Add-AppxProvisionedPackage.md b/docset/winserver2022-ps/dism/Add-AppxProvisionedPackage.md
index de473bb4b0..1ec7ef0dd9 100644
--- a/docset/winserver2022-ps/dism/Add-AppxProvisionedPackage.md
+++ b/docset/winserver2022-ps/dism/Add-AppxProvisionedPackage.md
@@ -209,7 +209,7 @@ Specifies the location of the app package (.appx) to add to the Windows image.
 This package will be added for every new user account.
 To add an app package (.appx) for a particular user or to test a package while developing your app, use the **Add-AppxPackage** cmdlet instead.
 
-The *PackagePath* parameter is only supported for offline servicing when the technician computer is running a version of Windows that supports Windows 8 apps.
+When performing offline servicing, the *PackagePath* parameter is only supported if the technician computer is running a version of Windows that supports Windows 8 apps.
 
 ```yaml
 Type: String