Update filter-as-segment.md

Author: corranrogue9

graph/articles/filter-as-segment.md

@@ -6,7 +6,7 @@ For example, the `riskyUsers` API on Microsoft Graph has an action defined to le
 
 ```xml
 <Action Name="dismiss" IsBound="true">
-  <Parameter Name="bindingParameter" Type="Collection(self.riskyUser)" />
+  <Parameter Name="bindingParameter" Type="Collection(microsoft.graph.riskyUser)" />
   <Parameter Name="userIds" Type="Collection(Edm.String)" />
 </Action>
 ```
@@ -32,20 +32,26 @@ in order to dismiss the risky users with the provided IDs. Using the filter-as-s
 </Action>
 ```
 
-and clients could call:
+and clients could call
 
 ```http
-POST /identityProtection/riskyUsers/$filter=@f/dismiss?@f=id IN ({userId1},{userId2},...)
+POST /identityProtection/riskyUsers/$filter=@f/dismiss?@f=id IN ('{userId1}','{userId2}',...)
 ```
 
 Doing this is beneficial due to the robust nature of OData filter expressions: clients will be able to dismiss risky users based on any supported filter without the service team needing to implement a new `dismiss` overload that filters based on the new criteria.
 However, there are some concerns about the discoverability of using the filter-as-segment feature, as well as the support of [parameter aliasing](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_ParameterAliases) that's required.
 As a result, functions should be introduced that act in the same way as the filter-as-segment:
 
 ```xml
-<Function Name="userFilter" IsBound="true" IsComposable="true">
-  <Parameter Name="bindingParameter" Type="Collection(Microsoft.DirectoryServices.user)" Nullable="false" />
+<Function Name="filter" IsBound="true" IsComposable="true">
+  <Parameter Name="bindingParameter" Type="Collection(microsoft.graph.riskyUser)" Nullable="false" />
   <Parameter Name="expression" Type="Edm.String" Nullable="false" />
-  <ReturnType Type="Collection(Microsoft.DirectoryServices.user)" />
+  <ReturnType Type="Collection(microsoft.graph.riskyUser)" />
 </Function>
 ```
+
+Clients would now be able to call
+
+```http
+POST /identityProtection/riskyUsers/filter(expression='id IN (''{userId1}'',''{userId2}'',...)')/dismiss
+```