Skip to content

Commit c415c5e

Browse files
committed
Clarified sentence about no manifest
1 parent 8ba43a3 commit c415c5e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

reference/docs-conceptual/learn/ps101/10-script-modules.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -356,10 +356,10 @@ Sometimes, your module might include helper functions you don't want to expose t
356356
private functions are used internally by other functions in the module but aren't exposed to users.
357357
There are a few ways to handle this scenario.
358358

359-
If you're not following best practices and only have a `.psm1` file without a proper module
360-
structure, your only option is to control visibility using the `Export-ModuleMember` cmdlet. This
361-
option lets you explicitly define which functions should be exposed directly from within the `.psm1`
362-
script module file, keeping everything else private by default.
359+
If you're not following best practices and only have a `.psm1` file without a module manifest, your
360+
only option is to control visibility using the `Export-ModuleMember` cmdlet. This option lets you
361+
explicitly define which functions should be exposed directly from within the `.psm1` script module
362+
file, keeping everything else private by default.
363363

364364
In the following example, only the `Get-MrPSVersion` function is exposed to users of your module,
365365
while the `Get-MrComputerName` function remains accessible internally to other functions within the

0 commit comments

Comments
 (0)