Fixed typo in text

PsCustomObject · PsCustomObject · commit 7292b79c401e · 2021-10-24T11:09:56.000+02:00
diff --git a/_posts/2021-06-02-Setup-Internal-PowerShell-Repository.md b/_posts/2021-06-02-Setup-Internal-PowerShell-Repository.md
@@ -11,7 +11,7 @@ tags:
 
 toc: true
 header:
-    teaser: "/assets/images/PowerShell_Logo.png"
+  teaser: "/assets/images/PowerShell_Logo.png"
 ---
 
 ## PowerShell repositories
@@ -20,9 +20,9 @@ If you follow my blog you probably know my [GitHub](https://github.com/PsCustomO
 
 In my posts I often talked about [PowerShell Gallery](https://pscustomobject.github.io/powershell/tips/PowerShell-Restore-Default-Repository/) which you probably already used to install a module released by Microsoft or other developers.
 
-Both are great tools when sharing code with a large audience over the internet, GitHub Private repositories are scope of this article,  but a large chunk of my work involves developing *modules* that me and my colleagues user internally for automation purposes. These modules usually leverage technologies that are available only in my work environment and sometimes implement functions that would not have much sense outside my company.
+Both are great tools when sharing code with a large audience over the internet, GitHub Private repositories are scope of this article, but a large chunk of my work involves developing _modules_ that me and my colleagues user internally for automation purposes. These modules usually leverage technologies that are available only in my work environment and sometimes implement functions that would not have much sense outside my company.
 
-One of the main issues we faced when initially started development of our own modules is ease of distribution to other team members for this reason we've setup internal **NuGet** repositories which can be used an *internal* PowerShell Gallery.
+One of the main issues we faced when initially started development of our own modules is ease of distribution to other team members for this reason we've setup internal **NuGet** repositories which can be used an _internal_ PowerShell Gallery.
 
 ## Required tools
 
@@ -32,11 +32,11 @@ Here's what you will need to follow this article and setup your own PowerShell r
 - The ASP.NET and web development workload installed [here's](https://docs.microsoft.com/en-us/visualstudio/install/modify-visual-studio?view=vs-2019) a guide on how to modify an existing Visual Studio installation in case you don't have the appropriate workload installed already
 - A server running a supported copy of **Windows Server** I am using Windows 2019 but 2016 will do just fine
 
-**Note:** If you do not have or cannot install Visual Studio at the end of the post I have posted a link to my [GitHub Repository](https://github.com/PsCustomObject/Nuget-PowerShell-Repository/tree/main/NuGetRepository/NuGetRepository) 
+**Note:** If you do not have or cannot install Visual Studio at the end of the post I have posted a link to my [GitHub Repository](https://github.com/PsCustomObject/Nuget-PowerShell-Repository/tree/main/NuGetRepository/NuGetRepository)
 
 ## Create the Visual Studio Project
 
-Once all requirements are in place open Visual Studio and  create a project using the *ASP.Web Application (Visual C#)* template.
+Once all requirements are in place open Visual Studio and create a project using the _ASP.Web Application (Visual C#)_ template.
 
 <figure>
   <a href="https://pscustomobject.github.io//assets/images/NugetArticle/VS_Create_New_Project.png">
@@ -48,28 +48,28 @@ Once all requirements are in place open Visual Studio and  create a project usin
   <img src="/assets/images/NugetArticle/VS_Web_Application.png"></a>
 </figure>
 
-Application name is not important just avoid *NuGet* as this would create a conflict with one of the *packages* we need to install as part of the dependencies, in my example I've used **NuGetRepository** but it can really be anything
+Application name is not important just avoid _NuGet_ as this would create a conflict with one of the _packages_ we need to install as part of the dependencies, in my example I've used **NuGetRepository** but it can really be anything
 
 <figure>
   <a href="https://pscustomobject.github.io//assets/images/NugetArticle/Application_Configuration.png">
   <img src="/assets/images/NugetArticle/Application_Configuration.png"></a>
 </figure>
 
-In the screen that will appear simply select the *Empty* template and then the *Create*  button
+In the screen that will appear simply select the _Empty_ template and then the _Create_ button
 
 <figure>
   <a href="https://pscustomobject.github.io//assets/images/NugetArticle/Project_Configuration.png">
   <img src="/assets/images/NugetArticle/Project_Configuration.png"></a>
 </figure>
 
-Once project has finished loading/being created *right-click* on the project name in *solution explorer* and select **Manage NuGet Packages**
+Once project has finished loading/being created _right-click_ on the project name in _solution explorer_ and select **Manage NuGet Packages**
 
 <figure>
   <a href="https://pscustomobject.github.io//assets/images/NugetArticle/Manage_NuGet_Package.png">
   <img src="/assets/images/NugetArticle/Manage_NuGet_Package.png"></a>
 </figure>
 
-In the *NuGetRepository* window select the *Broswe* tab and search for package **NuGet.Server** and click on the **Install** button.
+In the _NuGetRepository_ window select the _Browse_ tab and search for package **NuGet.Server** and click on the **Install** button.
 
 <figure>
   <a href="https://pscustomobject.github.io//assets/images/NugetArticle/Install_NuGet_Component.png">
@@ -78,29 +78,29 @@ In the *NuGetRepository* window select the *Broswe* tab and search for package *
 
 Keep I am using the latest stable release available at the time of this writing but you can select a different version of the package suiting your needs.
 
-This step will take some time, depending on your connection speed, and a window showing you changes to the solution and asking your confirmation will appear in which case simply click on the *Ok* button.
+This step will take some time, depending on your connection speed, and a window showing you changes to the solution and asking your confirmation will appear in which case simply click on the _Ok_ button.
 
-Once the installation step is complete I highly recommend to change the build type from *Debug*, default for new projects, to *Release* as this will disable all debug logging that is otherwise enabled for the solution.
+Once the installation step is complete I highly recommend to change the build type from _Debug_, default for new projects, to _Release_ as this will disable all debug logging that is otherwise enabled for the solution.
 
 <figure>
   <a href="https://pscustomobject.github.io//assets/images/NugetArticle/Set_Build_Type.png">
   <img src="/assets/images/NugetArticle/Set_Build_Type.png"></a>
 </figure>
 
-Once this is done go to *Build / Build Solution* menu, or press F6 if you're lazy like me, to *package* together all files making up the solution.
+Once this is done go to _Build / Build Solution_ menu, or press F6 if you're lazy like me, to _package_ together all files making up the solution.
 
-This will create a folder structure, under the path previously specified, containing all files required by the solution. Project path is visible in the **Properties** window under the *Project Folder* field
+This will create a folder structure, under the path previously specified, containing all files required by the solution. Project path is visible in the **Properties** window under the _Project Folder_ field
 
 <figure>
   <a href="https://pscustomobject.github.io//assets/images/NugetArticle/Project_Path.png">
   <img src="/assets/images/NugetArticle/Project_Path.png"></a>
 </figure>
 
-**Note:** By default solution will be build under the  C:\Users\username\source\repos\AppName\AppName\ path
+**Note:** By default solution will be build under the C:\Users\username\source\repos\AppName\AppName\ path
 
 ## Install required Server Components
 
-Once the solution has been build in Visual Studio move on the server that will be hosting the repository and launch the following cmdlet from an elevated PowerShell session to install required *IIS* components
+Once the solution has been build in Visual Studio move on the server that will be hosting the repository and launch the following cmdlet from an elevated PowerShell session to install required _IIS_ components
 
 ```powershell
 # Splatted version
@@ -115,9 +115,9 @@ Install-WindowsFeature @paramInstallWindowsFeature
 Install-WindowsFeature Web-Server,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Filter,Web-ISAPI-Ext -IncludeManagementTools
 ```
 
-Once all components are in place copy the solution files to a directory on the server with the default being *C:\inetpub\wwwroot*. Path is not really import and could be anything you'd like, I will just stick with the default.
+Once all components are in place copy the solution files to a directory on the server with the default being _C:\inetpub\wwwroot_. Path is not really import and could be anything you'd like, I will just stick with the default.
 
-As a refrence here's how the content of my application folder looks like on my test server
+As a reference here's how the content of my application folder looks like on my test server
 
 <figure>
   <a href="https://pscustomobject.github.io//assets/images/NugetArticle/IIS_Application.png">
@@ -126,7 +126,7 @@ As a refrence here's how the content of my application folder looks like on my t
 
 ### Update Web.Config configuration file
 
-The **web.config** file is located in the project root folder, assuming default path this will be *C:\inetpub\wwwroot\NuGetRepository*, open it with a text editor and under the **\<system.web\>** section you should see line similar the following (actual .Net Framework version could vary)
+The **web.config** file is located in the project root folder, assuming default path this will be _C:\inetpub\wwwroot\NuGetRepository_, open it with a text editor and under the **\<system.web\>** section you should see line similar the following (actual .Net Framework version could vary)
 
 ```xml
   <system.web>
@@ -147,11 +147,11 @@ Comment out or delete one of the instances of **\<compilation\>** tag so that re
   </system.web>
 ```
 
-**Note:** If the *web.config* file is not updated when opening the IIS Application an *Internal Server Error* message will be displayed an application won't work.
+**Note:** If the _web.config_ file is not updated when opening the IIS Application an _Internal Server Error_ message will be displayed an application won't work.
 
 ## Deploy Application to IIS
 
-We can finally deploy the *NuGet* application to IIS to do so open **IIS Manager / Expand <Server Name> / Sites** right-click on Default Web Site and select **Add Application**
+We can finally deploy the _NuGet_ application to IIS to do so open **IIS Manager / Expand <Server Name> / Sites** right-click on Default Web Site and select **Add Application**
 
 <figure>
   <a href="https://pscustomobject.github.io//assets/images/NugetArticle/Add_Application.png">
@@ -174,7 +174,7 @@ To test the configuration point your browser to **http://localhost/Nuget** which
 
 ### Configure Package Directory
 
-In the default configuration packages are stored under the same path where the application lives in the *Packages* directory, in our example *C:\inetpub\wwwroot\Nuget\Packages*. This can be changed in the *web.config* configuration file via the following tag
+In the default configuration packages are stored under the same path where the application lives in the _Packages_ directory, in our example _C:\inetpub\wwwroot\Nuget\Packages_. This can be changed in the _web.config_ configuration file via the following tag
 
 ```xml
     <!--
@@ -186,23 +186,23 @@ In the default configuration packages are stored under the same path where the a
 
 ### Configure Repository API Key
 
-Up to this point the repository is ready and can be used to *download* packages from it but if we need to *upload* data, in our example PowerShell modules, to it we would need some form of authentication which in NuGet is accomplished through an API key.
+Up to this point the repository is ready and can be used to _download_ packages from it but if we need to _upload_ data, in our example PowerShell modules, to it we would need some form of authentication which in NuGet is accomplished through an API key.
 
-First of all generate a unique API key, I generally use a GUID generated via *New-Guid* cmdlet, open the *web.config* file and update the **apiKey** value as in the following example
+First of all generate a unique API key, I generally use a GUID generated via _New-Guid_ cmdlet, open the _web.config_ file and update the **apiKey** value as in the following example
 
 ```xml
     <!--
-    Determines if an Api Key is required to push\delete packages from the server. 
+    Determines if an Api Key is required to push\delete packages from the server.
     -->
     <add key="requireApiKey" value="true" />
-    <!-- 
+    <!--
     Set the value here to allow people to push/delete packages from the server.
     NOTE: This is a shared key (password) for all users.
     -->
     <add key="apiKey" value="<GUID VALUE>" />
 ```
 
-If you want to disable authentication all together you can simply set the **requireApiKey** to *false*.
+If you want to disable authentication all together you can simply set the **requireApiKey** to _false_.
 
 ## Closing notes
 
