Apply suggestions from code review

Co-authored-by: Alisa <7586237+alisaduncan@users.noreply.github.com>
Co-authored-by: Colton Beach <98902851+cbeac243@users.noreply.github.com>

Author: 3 people

_source/_posts/2024-02-29-net-scim.md

@@ -43,7 +43,7 @@ Create a directory called `okta-scim-server-dotnet`. Navigate to the directory i
 - At this point using the *https://localhost:7094/swagger/index.html* you will be able to see the Swagger UI. Typically, a browser tab will automatically open; if not, manually check for the URL to the Swagger UI under `Properties/launchSettings.json` and copy/paste this URL onto the browser:
 
 ### Setup Okta (the IdP)
-{% include setup/cli.md type="spa" framework="ASP.NET Core" loginRedirectUri="http://localhost:7094/swagger/oauth2-redirect.html" logoutRedirectUri="http://localhost:7094" %}
+{% include setup/cli.md type="spa" loginRedirectUri="http://localhost:7094/swagger/oauth2-redirect.html" logoutRedirectUri="http://localhost:7094" %}
 
 Note the `Issuer` and the `Client ID`. You'll need those values for your authentication configuration coming up soon.
 
@@ -90,7 +90,7 @@ public class Email
     public virtual User User { get; set; }
 }
 ```
-Add DB context for each entity framework in the `DataModels.cs` file, i.e., to the two models we created above. We'll also add some seed data using the method `OnModelCreating`, which will be useful for testing. In this sample, we will create support for the User resource type. However, if you want to expand on this, you can use similar concepts to maintain endpoints for other resource types, such as Group. Paste the following code just below the `Email` class:
+Add DB context for each entity framework in the `DataModels.cs` file, (i.e., to the two models we created above.) We'll also add some seed data using the method `OnModelCreating`, which will be useful for testing. In this sample, we will create support for the User resource type. However, if you want to expand on this, you can use similar concepts to maintain endpoints for other resource types, such as Group. Paste the following code just below the `Email` class:
 ```c#
 public partial class ScimDbContext : DbContext
 {
@@ -365,7 +365,7 @@ public class ScimEmail
 }
 ```
 We also need to create mappers between DB models and SCIM models to avoid many manual conversions. For this, we will use the `AutoMapper` package.
-- Install dependencies by running the following commands
+- Install dependencies by running the following commands:
     - `dotnet add package AutoMapper`
     - `dotnet add package Automapper.Extensions.Microsoft.DependencyInjection`
 - Add Mappings to `ScimModels.cs`: 
@@ -557,7 +557,7 @@ record WeatherForecast(DateOnly Date, int TemperatureC, string? Summary)
 ```
 
 ### Create the .NET SCIM server RESTful API endpoints
-Since we have created the necessary data and SCIM models. We can move on to creating the endpoints for user lifecycle management. First, let's set up dependencies, some basic global configuration, and clean up unnecessary code
+Since we have created the necessary data and SCIM models. We can move on to creating the endpoints for user lifecycle management. First, let's set up dependencies, some basic global configuration, and clean up unnecessary code.
 - Install dependencies by running `dotnet add package Newtonsoft.Json`
 - At the top of the `Program.cs` file, add `using` statements
     ```c#
@@ -619,7 +619,7 @@ app.Run();
 ```
 
 ### Retrieve a user
-We are using minimal APIs for creating endpoints. For retrieving a user, let's create the route that expects the user's `id` in the path and responds with a single `ScimUser` object if found and a `ScimErrorResponse` if the user doesn't exist. Add the following code before `app.Run();` in the `Program.cs` file.
+We are using minimal APIs for creating endpoints. For retrieving a user, let's create the route that expects the user's `id` in the path and responds with a single `ScimUser` object if found and a `ScimErrorResponse` if the user doesn't exist. Add the following code before `app.Run();` in the `Program.cs` file:
 ```c#
 var scimPrefix = "/scim/v2";
 var userRoute = $"{scimPrefix}/users";
@@ -1802,7 +1802,7 @@ app.MapPatch(userRoute + "/{id}", async Task<IResult> (int id, [FromBody] JsonDo
 app.Run();
 ```
 
-- At this point, our OAuth implementation can now can be tested on our CRUD endpoints. However, this needs an additional step. The Swagger UI should now have an `Authorize` button, click on this button, then click on the `select all` option under `Scopes` before clicking on the `Authorize` button again. If you do not authenticate, you will get `401` responses from any of the endpoints we've protected.
+- At this point, our OAuth implementation can now can be tested on our CRUD endpoints. However, this needs an additional step. The Swagger UI should now have an `Authorize` button. Click on this button, then click on the `select all` option under `Scopes` before clicking on the `Authorize` button again. If you do not authenticate, you will get `401` responses from any of the endpoints we've protected.
 
 ## Test requests to the .NET SCIM server locally using a tunnel
 
@@ -1830,7 +1830,7 @@ Keep the default settings in the **Sign-On Options** dialog, as our app doesn't
 
 In the **Provisioning** tab of the application, press the **Configure API Integration** button and check the **Enable API Integration** checkbox. Provide the **Base URL**, which is the ngrok localtunnel URL with `/scim/v2` appended to the end. The **OAuth Bearer Token** is can be retrieved from the test you did above either from UI or curl. Press **Save** to save the settings.
 
-For example, below is a highlighted sample base URL from ngrok.
+For example, below is a highlighted sample base URL from ngrok:
 
 {% img blog/net-scim/ngrok.jpeg alt:"Image of highlighted sample base URL from ngrok" width:"800" %}{: .center-image }
 
@@ -1870,7 +1870,7 @@ We can confirm that Tom's `active` attribute is now `false` in the Swagger UI by
 
 Let's say Tom gets hired full-time with the company and needs access to the application again. 
 
-To reactivate Tom's account, we will repeat the steps for assigning his Okta account to the application.  Reactivating Tom causes Okta to send a PATCH request to your scim server, setting their `active` attribute to `true`. 
+To reactivate Tom's account, we will repeat the steps for assigning his Okta account to the application. Reactivating Tom causes Okta to send a PATCH request to your SCIM server, setting their `active` attribute to `true`. 
 
 Again, we can confirm that Tom's account is now `active` through the Swagger UI by making a request to the GET Users endpoint filtering for Tom's email "tom.anderson@fake.domain".