diff --git a/docs/backend-system/building-backends/01-index.md b/docs/backend-system/building-backends/01-index.md
index 0f23ae0006..d4b463af41 100644
--- a/docs/backend-system/building-backends/01-index.md
+++ b/docs/backend-system/building-backends/01-index.md
@@ -61,11 +61,11 @@ All of these services can be replaced with your own implementations if you need
 For example, let's say we want to customize the core configuration service to enable remote configuration loading. That would look something like this:
 
 ```ts
-import { configServiceFactory } from '@backstage/backend-app-api';
+import { rootConfigServiceFactory } from '@backstage/backend-app-api';
 
 const backend = createBackend({
   services: [
-    configServiceFactory({
+    rootConfigServiceFactory({
       remote: { reloadIntervalSeconds: 60 },
     }),
   ],
diff --git a/docs/backend-system/core-services/01-index.md b/docs/backend-system/core-services/01-index.md
index c688055c96..a51db3c993 100644
--- a/docs/backend-system/core-services/01-index.md
+++ b/docs/backend-system/core-services/01-index.md
@@ -183,11 +183,11 @@ There's additional configuration that you can optionally pass to setup the `conf
 You can configure these additional options by adding an override for the core service when calling `createBackend` like follows:
 
 ```ts
-import { configServiceFactory } from '@backstage/backend-app-api';
+import { rootConfigServiceFactory } from '@backstage/backend-app-api';
 
 const backend = createBackend({
   services: [
-    configServiceFactory({
+    rootConfigServiceFactory({
       argv: [
         '--config',
         '/backstage/app-config.development.yaml',