fix some typos and clumsy wording

spec/src/main/asciidoc/core/beanmanager_lite.asciidoc

@@ -2,18 +2,17 @@
 
 == Programmatic access to container
 
-CDI 3.0 used to provide a single `BeanManager` object, which allows access to many useful operations.
-In CDI 4.0, this is split into `BeanContainer` and `BeanManager`.
+The `BeanContainer` and `BeanManager` interfaces allow programmatic access to the CDI container.
 
-`BeanContainer` provides access to a subset of `BeanManager` features which can be implemented in more restricted environments;
-It is available in {cdi_lite} environments.
+`BeanContainer` provides features that can be implemented in more restricted environments.
+It is available in {cdi_lite} environment, and therefore also in {cdi_full} environment.
 
-`BeanManager` extends `BeanContainer` and provides the remaining features.
-It is available in {cdi_full} environments.
+`BeanManager` extends `BeanContainer` and provides additional features.
+It is only available in {cdi_full} environment.
 
 In {cdi_lite} environment, attempting to obtain a `BeanManager` or invoking methods on it results in non-portable behavior.
 
-[[beanmanager]]
+[[beancontainer]]
 
 === The `BeanContainer` object
 
@@ -24,10 +23,11 @@ Thus, any bean may obtain an instance of `BeanContainer` by injecting it:
 
 [source, java]
 ----
-@Inject BeanContainer manager;
+@Inject BeanContainer container;
 ----
 
 The operations of `BeanContainer` may be called at any time during the execution of the application.
+// TODO Full has restrictions on when BeanManager methods can be called, do we want to reflect them here in some way?
 
 [[provider]]
 

spec/src/main/asciidoc/core/injectionandresolution_full.asciidoc

@@ -15,7 +15,7 @@ An alternative is not available for injection, lookup or name resolution to clas
 
 ==== Declaring selected alternatives in {cdi_full}
 
-{cdi_full} provides an additional way to select alternatives to the one defined in <<declaring_selected_alternatives_application>>:
+{cdi_full} provides an additional way to select alternatives to the one defined in <<declaring_selected_alternatives_application>>.
 
 [[declaring_selected_alternatives_bean_archive]]
 

spec/src/main/asciidoc/core/interceptors_full.asciidoc

@@ -16,7 +16,7 @@ Interceptor bindings may be used to associate interceptors with any managed bean
 
 It is possible to apply interceptors programmatically to the return value of a producer method, with the `InterceptionFactory` interface as defined in <<interception_factory>>.
 
-[[enabled_interceptors_full]]
+[[enabled_interceptors]]
 
 === Interceptor enablement and ordering in {cdi_full}
 

spec/src/main/asciidoc/core/spi.asciidoc

@@ -202,11 +202,11 @@ The container sets the value of all injected fields, and calls all initializer m
 
 Implementations of `Producer` and `InjectionTarget` must ensure that the set of injection points returned by `getInjectionPoints()` are injected by `produce()` or `inject()`.
 
-[[beanmanager_full]]
+[[beanmanager]]
 
 === The `BeanManager` object
 
-In addition to rules defined in <<beanmanager>>, the following rules apply.
+In addition to rules defined in <<beancontainer>>, the following rules apply.
 
 The interface `jakarta.enterprise.inject.spi.BeanManager` provides operations for obtaining contextual references for beans, along with many other operations of use to applications and portable extensions.