Attended to PR comments

Author: Kalyan Krishna

5-WebApp-AuthZ/5-1-Roles/README-incremental-instructions.md

@@ -172,7 +172,7 @@ When you click on the page that fetches the signed-in user's roles and group ass
 
 > Did the sample not work for you as expected? Did you encounter issues trying this sample? Then please reach out to us using the [GitHub Issues](../../../../issues) page.
 
-### Support in ASP.NET OWIN middleware libraries
+### Support in ASP.NET Core middleware libraries
 
 The asp.net middleware supports roles populated from claims by specifying the claim in the `RoleClaimType` property of `TokenValidationParameters`.
 

5-WebApp-AuthZ/5-1-Roles/README.md

@@ -248,7 +248,7 @@ When you click on the page that fetches the signed-in user's roles and group ass
 
 > Did the sample not work for you as expected? Did you encounter issues trying this sample? Then please reach out to us using the [GitHub Issues](../../../../issues) page. 
 
-### Support in ASP.NET OWIN middleware libraries
+### Support in ASP.NET Core middleware libraries
 
 The asp.net middleware supports roles populated from claims by specifying the claim in the `RoleClaimType` property of `TokenValidationParameters`.
 

5-WebApp-AuthZ/5-2-Groups/README-incremental-instructions.md

@@ -140,7 +140,7 @@ In case, you are authenticating using the [implicit grant flow](https://docs.mic
 1. A claim named `hasgroups` with a value of true will be present in the token instead of the `groups` claim .
 1. The maximum number of groups provided in the `groups` claim is limited to 6. This is done to prevent  the URI fragment beyond the URL length limits.
 
-### Support in ASP.NET OWIN middleware libraries
+### Support in ASP.NET Core middleware libraries
 
 The asp.net middleware supports roles populated from claims by specifying the claim in the `RoleClaimType` property of `TokenValidationParameters`.
 Since the `groups` claim contains the object ids of the security groups than actual names, you'd use the group id's instead of group names. See [Role-based authorization in ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/security/authorization/roles?view=aspnetcore-2.2) for more info.

5-WebApp-AuthZ/5-2-Groups/README.md

@@ -233,7 +233,7 @@ In case, you are authenticating using the [implicit grant flow](https://docs.mic
 1. A claim named `hasgroups` with a value of true will be present in the token instead of the `groups` claim .
 1. The maximum number of groups provided in the `groups` claim is limited to 6. This is done to prevent  the URI fragment beyond the URL length limits.
 
-### Support in ASP.NET OWIN middleware libraries
+### Support in ASP.NET Core middleware libraries
 
 The asp.net middleware supports roles populated from claims by specifying the claim in the `RoleClaimType` property of `TokenValidationParameters`.
 Since the `groups` claim contains the object ids of the security groups than actual names, you'd use the group id's instead of group names. See [Role-based authorization in ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/security/authorization/roles?view=aspnetcore-2.2) for more info.