update docs now that scopes are available

astro/src/content/docs/lifecycle/authenticate-users/oauth/modes.mdx

@@ -213,9 +213,7 @@ The workflow for this mode looks like:
 
 The **First-party service authorization** mode is the inverse of the **Third-party service authorization** mode. When another application wishes to call your APIs on behalf of one of your users, you are in this mode. Here, your application is the "third-party service" discussed above. Your application asks the user if they want to grant the other application specific permissions. Basically, if you are building a platform and want developers to be able to call your APIs on behalf of their users, you'll need to support this OAuth mode.
 
-With this mode, your OAuth server might display a "permission grant screen" to the user asking if they want to grant the third-party application permissions to your APIs. This isn't strictly necessary and depends on your requirements, but if it is, you want custom scopes.
-
-Custom scopes are not currently supported in FusionAuth; here's the [GitHub tracking issue](https://github.com/FusionAuth/fusionauth-issues/issues/275).
+With this mode, you can create custom scopes for each application. To learn how to use scopes, read the documentation [here](/docs/lifecycle/authenticate-users/oauth/scopes).
 
 ## Machine-to-machine Authorization