From c415c5ed5a42031c2d14c13cc1752a72aa5306d9 Mon Sep 17 00:00:00 2001
From: "Mike F. Robbins" <6719572+mikefrobbins@users.noreply.github.com>
Date: Thu, 6 Nov 2025 15:47:34 -0600
Subject: [PATCH] Clarified sentence about no manifest

---
 .../docs-conceptual/learn/ps101/10-script-modules.md      | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/reference/docs-conceptual/learn/ps101/10-script-modules.md b/reference/docs-conceptual/learn/ps101/10-script-modules.md
index 7dbf1b21a528..bd39d1f7d076 100644
--- a/reference/docs-conceptual/learn/ps101/10-script-modules.md
+++ b/reference/docs-conceptual/learn/ps101/10-script-modules.md
@@ -356,10 +356,10 @@ Sometimes, your module might include helper functions you don't want to expose t
 private functions are used internally by other functions in the module but aren't exposed to users.
 There are a few ways to handle this scenario.
 
-If you're not following best practices and only have a `.psm1` file without a proper module
-structure, your only option is to control visibility using the `Export-ModuleMember` cmdlet. This
-option lets you explicitly define which functions should be exposed directly from within the `.psm1`
-script module file, keeping everything else private by default.
+If you're not following best practices and only have a `.psm1` file without a module manifest, your
+only option is to control visibility using the `Export-ModuleMember` cmdlet. This option lets you
+explicitly define which functions should be exposed directly from within the `.psm1` script module
+file, keeping everything else private by default.
 
 In the following example, only the `Get-MrPSVersion` function is exposed to users of your module,
 while the `Get-MrComputerName` function remains accessible internally to other functions within the