diff --git a/ReadMe.md b/README.md
similarity index 83%
rename from ReadMe.md
rename to README.md
index 687b274..4d267ce 100644
--- a/ReadMe.md
+++ b/README.md
@@ -7,7 +7,9 @@ Chocolatey package configuration for the Cricut Design Space application.
 
 ## Creating Nuget Package
 
-Clone the repository and use Chocolatey to create the package
+Clone the repository and use Chocolatey to create the package:
+
+    $ choco pack
 
 ## Testing Nuget Package
 
@@ -15,6 +17,6 @@ Follow the instructions at the URL below to create and use a Chocolatey test env
 
     https://github.com/chocolatey-community/chocolatey-test-environment
 
-Note: as March 10, 2020, the default `shell/InstallChocolayet.ps1` file was not creating a TLS channel and thus would not install Chocolatey in the virtual machine. The link below contains a fix. Once the pull request is accepted in the test environment repository this message will be removed.
+Note: as March 10, 2020, the default `shell/InstallChocolatey.ps1` file was not creating a TLS channel and thus would not install Chocolatey in the virtual machine. The link below contains a fix. Once the pull request is accepted in the test environment repository this message will be removed.
 
     https://github.com/chocolatey-community/chocolatey-test-environment/pull/49/commits/6b5563c52cf208834cc662e3f14a00bdad9bf567
\ No newline at end of file
diff --git a/cricutdesignspace.nuspec b/cricutdesignspace.nuspec
index d15ed95..a499d79 100644
--- a/cricutdesignspace.nuspec
+++ b/cricutdesignspace.nuspec
@@ -1,80 +1,26 @@
 <?xml version="1.0" encoding="utf-8"?>
-<!-- Read this before creating packages: https://chocolatey.org/docs/create-packages -->
-<!-- It is especially important to read the above link to understand additional requirements when publishing packages to the community feed aka dot org (https://chocolatey.org/packages). -->
-
-<!-- Test your packages in a test environment: https://github.com/chocolatey/chocolatey-test-environment -->
-
-<!--
-This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Reference. Chocolatey uses a special version of NuGet.Core that allows us to do more than was initially possible. As such there are certain things to be aware of:
-
-* the package xmlns schema url may cause issues with nuget.exe
-* Any of the following elements can ONLY be used by choco tools - projectSourceUrl, docsUrl, mailingListUrl, bugTrackerUrl, packageSourceUrl, provides, conflicts, replaces 
-* nuget.exe can still install packages with those elements but they are ignored. Any authoring tools or commands will error on those elements 
--->
-
-<!-- You can embed software files directly into packages, as long as you are not bound by distribution rights. -->
-<!-- * If you are an organization making private packages, you probably have no issues here -->
-<!-- * If you are releasing to the community feed, you need to consider distribution rights. -->
-<!-- Do not remove this test for UTF-8: if “Ω” doesn’t appear as greek uppercase omega letter enclosed in quotation marks, you should use an editor that supports UTF-8, not this one. -->
 <package xmlns="http://schemas.microsoft.com/packaging/2015/06/nuspec.xsd">
   <metadata>
-    <!-- == PACKAGE SPECIFIC SECTION == -->
-    <!-- This section is about this package, although id and version have ties back to the software -->
-    <!-- id is lowercase and if you want a good separator for words, use '-', not '.'. Dots are only acceptable as suffixes for certain types of packages, e.g. .install, .portable, .extension, .template -->
-    <!-- If the software is cross-platform, attempt to use the same id as the debian/rpm package(s) if possible. -->
     <id>cricutdesignspace</id>
-    <!-- version should MATCH as closely as possible with the underlying software -->
-    <!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
-    <!-- Note that unstable versions like 0.0.1 can be considered a released version, but it's possible that one can release a 0.0.1-beta before you release a 0.0.1 version. If the version number is final, that is considered a released version and not a prerelease. -->
     <version>5.6.19</version>
-    <!-- <packageSourceUrl>Where is this Chocolatey package located (think GitHub)? packageSourceUrl is highly recommended for the community feed</packageSourceUrl>-->
-    <!-- owners is a poor name for maintainers of the package. It sticks around by this name for compatibility reasons. It basically means you. -->
-    <!--<owners>__REPLACE_YOUR_NAME__</owners>-->
-    <!-- ============================== -->
-
-    <!-- == SOFTWARE SPECIFIC SECTION == -->
-    <!-- This section is about the software itself -->
+    <owners>stevenpickles</owners>
     <title>CricutDesignSpace (Install)</title>
     <authors>Cricut</authors>
-    <!-- projectUrl is required for the community feed -->
     <projectUrl>https://design.cricut.com/</projectUrl>
     <iconUrl>https://is5-ssl.mzstatic.com/image/thumb/Purple114/v4/2d/e1/51/2de1511b-f8ad-320c-77d9-e809e1d65928/AppIcon-0-0-1x_U007emarketing-0-0-0-9-0-0-sRGB-0-0-0-GLES2_U002c0-512MB-85-220-0-0.png/246x0w.png</iconUrl>
-    <!-- <copyright>Year Software Vendor</copyright> -->
-    <!-- If there is a license Url available, it is required for the community feed -->
-    <!-- <licenseUrl>Software License Location __REMOVE_OR_FILL_OUT__</licenseUrl>
-    <requireLicenseAcceptance>true</requireLicenseAcceptance>-->
-    <!--<projectSourceUrl>Software Source Location - is the software FOSS somewhere? Link to it with this</projectSourceUrl>-->
+    <copyright>2020</copyright>
+    <licenseUrl>https://us.cricut.com/legal</licenseUrl>
+    <requireLicenseAcceptance>false</requireLicenseAcceptance>
+    <!-- Since Cricut Design Space is closed source there is no projectSourceUrl to link -->
+    <!-- <projectSourceUrl></projectSourceUrl>-->
     <docsUrl>https://help.cricut.com/hc/en-us/articles/360009428814-Downloading-and-Installing-Design-Space#windowsinstall</docsUrl>
-    <!--<mailingListUrl></mailingListUrl>-->
-    <!--<bugTrackerUrl></bugTrackerUrl>-->
+    <bugTrackerUrl>https://help.cricut.com/hc/en-us/articles/360020316674-Cricut-Contact-Information</bugTrackerUrl>
     <tags>cricut design space</tags>
     <summary>Design and wirelessly cut using Cricut Explore and Cricut Maker machines.</summary>
     <description>Cricut Design Space is a companion app that lets you design and wirelessly cut with Cricut Explore and Cricut Maker machines. Create a project from scratch or browse thousands of images, predesigned Make It Now projects, and fonts in the Cricut Image Library.</description>
-    <!-- <releaseNotes>__REPLACE_OR_REMOVE__MarkDown_Okay</releaseNotes> -->
-    <!-- =============================== -->      
-
-    <!-- Specifying dependencies and version ranges? https://docs.nuget.org/create/versioning#specifying-version-ranges-in-.nuspec-files -->
-    <!--<dependencies>
-      <dependency id="" version="__MINIMUM_VERSION__" />
-      <dependency id="" version="[__EXACT_VERSION__]" />
-      <dependency id="" version="[_MIN_VERSION_INCLUSIVE, MAX_VERSION_INCLUSIVE]" />
-      <dependency id="" version="[_MIN_VERSION_INCLUSIVE, MAX_VERSION_EXCLUSIVE)" />
-      <dependency id="" />
-      <dependency id="chocolatey-core.extension" version="1.1.0" />
-    </dependencies>-->
-    <!-- chocolatey-core.extension - https://chocolatey.org/packages/chocolatey-core.extension
-         - You want to use Get-UninstallRegistryKey on less than 0.9.10 (in chocolateyUninstall.ps1)
-         - You want to use Get-PackageParameters and on less than 0.11.0
-         - You want to take advantage of other functions in the core community maintainer's team extension package
-    -->
-
-    <!--<provides>NOT YET IMPLEMENTED</provides>-->
-    <!--<conflicts>NOT YET IMPLEMENTED</conflicts>-->
-    <!--<replaces>NOT YET IMPLEMENTED</replaces>-->
+    <releaseNotes>No release notes are available from the manufacturer.</releaseNotes>
   </metadata>
   <files>
-    <!-- this section controls what actually gets packaged into the Chocolatey package -->
     <file src="tools\**" target="tools" />
-    <!--Building from Linux? You may need this instead: <file src="tools/**" target="tools" />-->
   </files>
 </package>