diff --git a/docs/src/main/asciidoc/writing-extensions.adoc b/docs/src/main/asciidoc/writing-extensions.adoc
index 52334084b0a5b3..89fcafce1b9e48 100644
--- a/docs/src/main/asciidoc/writing-extensions.adoc
+++ b/docs/src/main/asciidoc/writing-extensions.adoc
@@ -2040,6 +2040,31 @@ public final class MyExtProcessor {
 If you are using `META-INF/services` files you need to register the files as resources so that your native image can find them,
 but you also need to register each listed class for reflection so they can be instantiated or inspected at run-time:
 
+[source,java]
+----
+public final class MyExtProcessor {
+
+    @BuildStep
+    void registerNativeImageReources(BuildProducer<ServiceProviderBuildItem> services) {
+        String service = "META-INF/services/" + io.quarkus.SomeService.class.getName();
+        
+        // find out all the implementation classes listed in the service files
+        Set<String> implementations = 
+            ServiceUtil.classNamesNamedIn(Thread.currentThread().getContextClassLoader(),
+                                          service);
+
+        // register every listed implementation class so they can be instantiated 
+        // in native-image at run-time
+        services.produce(
+            new ServiceProviderBuildItem(io.quarkus.SomeService.class.getName(), 
+                                         implementations.toArray(new String[0])));
+    }
+}
+----
+
+NOTE: This only registers the implementation classes for instantiation via reflection (you will not be able
+to inspect its fields and methods). If you need to do that, you can do it this way:
+
 [source,java]
 ----
 public final class MyExtProcessor {
@@ -2063,7 +2088,7 @@ public final class MyExtProcessor {
 }
 ----
 
-This is the easiest way to get your services running natively, but it's less efficient than scanning the implementation
+While this is the easiest way to get your services running natively, it's less efficient than scanning the implementation
 classes at build time and generating code that registers them at static-init time instead of relying on reflection.
 
 You can achieve that by adapting the previous build step to use a static-init recorder instead of registering