Merge pull request #1222 from steviecoaster/sept_webinar

(maint) Fix Extension guide

Author: pauby

src/content/docs/en-us/guides/create/create-extension-package.mdx

@@ -47,7 +47,7 @@ You might choose to use this over installing a full PowerShell module if you did
 
 ### Extension Package
 
-An extension package is organised much like any other Chocolatey package - though instead of the scripts within the `tools` directory you may be familiar with, there should be an `extensions` directory.
+An extension package is organized much like any other Chocolatey package - though instead of the scripts within the `tools` directory you may be familiar with, there should be an `extensions` directory.
 
 We'll now run through how to create an extension package, assuming you have an environment set up as in <Xref title="Preparing Your Environment for Package Creation" value="howto-prepare-env" />.
 
@@ -79,6 +79,9 @@ Follow the steps below to get started:
     <summary>Extension package for testing.</summary>
     <tags>extension chocolatey package</tags>
   </metadata>
+  <files>
+    <file src="extensions\**" target="extensions" />
+  </files>
 </package>
 ```
 
@@ -124,6 +127,8 @@ function Set-ConfigValue {
         $Configuration | ConvertTo-Json | Set-Content -Path $Path
     }
 }
+
+Export-ModuleMember -Function Set-ConfigValue
 ```
 
 So, if you browse through the files in VS Code or Explorer, you should see a file structure like this: