Merge pull request #5919 from OpenLiberty/5724-BELL

edits per SME review

modules/reference/pages/feature/bells/examples.adoc

@@ -13,17 +13,17 @@ The minimum `server.xml` configuration for the BELL feature requires a `library`
 <bell libraryRef="servicesLib" />
 ----
 
-For any BELL configuration, the BELL feature discovers all services in the `META-INF/services` folder of the referenced library. Alternatively, you can configure the `service` attribute to specify a service for Open liberty to look up in the `META-INF/service` folder, as shown in the following example.
+The BELL feature discovers all services in the `META-INF/services` folder of the referenced library. Alternatively, you can configure the `service` attribute to specify the name of the service the feature looks up in the `META-INF/service` folder, as shown in the following example.
 
 [source,xml,subs="verbatim,quotes"]
 ----
 <bell libraryRef="servicesLib"
    service="_name.of.fully.qualified.api.or.spi.interface_" />
 ----
 
-For all services that are discovered or specified, the BELL feature registers the service interface and implementation class as an OSGi service, which makes the service available to the Open Liberty runtime.
+For every service that is discovered or specified, the BELL feature registers the service interface and implementation class as an OSGi service, which makes the service available to the Open Liberty runtime.
 
-Be sure to enable the Open Liberty features that provide the API or SPI packages that are required by the library. For example, you must enable the feature:servlet[display=Jakarta Servlet] feature for a library that provides an implementation of the `jakarta.servlet.ServletContainerInitializer` interface because this feature provides the `jakarta.servlet` API package.
+Be sure to enable the Open Liberty features that provide the API or SPI packages that are required by the library. 
 
 === Implement an SPI with BELL services