docs(effects): merge effect registration, delete standalone mentions

ngrx · markostanimirovic · Dec 9, 2024 · Sep 11, 2024 · Sep 13, 2024 · Oct 9, 2024
commit 6a49f4c7fbdbd4cbd7350c336892d3313d253906
diff --git a/projects/ngrx.io/content/guide/effects/index.md b/projects/ngrx.io/content/guide/effects/index.md
@@ -269,9 +269,10 @@ In that case, the [`inject` function](https://angular.dev/api/core/inject) must
 
 </div>
 
-## Registering Root Effects
+## Registering Effects
 
-Registering effects can also be done using the standalone APIs if you are bootstrapping an Angular application using standalone features.
+Feature-level effects are registered in the `providers` array of the route config. 
+The same `provideEffects()` function is used in root-level and feature-level effects.
 
 <code-example header="main.ts">
 import { bootstrapApplication } from '@angular/platform-browser';
@@ -297,27 +298,6 @@ Services used in root-level effects are **not** recommended to be used with serv
 
 </div>
 
-## Registering Feature Effects
-
-Feature-level effects are registered in the `providers` array of the route config. The same `provideEffects()` function is used in root-level and feature-level effects.
-
-<code-example header="movie-routes.ts">
-import { Route } from '@angular/router';
-import { provideEffects } from '@ngrx/effects';
-
-import { MoviesEffects } from './effects/movies.effects';
-import * as actorsEffects from './effects/actors.effects';
-
-export const routes: Route[] = [
-  {
-    path: 'movies',
-    providers: [
-      provideEffects(MoviesEffects, actorsEffects)
-    ]
-  }
-];
-</code-example>
-
 <div class="alert is-important">
 
 **Note:** Registering an effects class multiple times, either by `forRoot()`, `forFeature()`, or `provideEffects()`,