More editing

README.md

@@ -43,7 +43,7 @@
 *svcs* (pronounced *services*) is a **dependency container** for Python.
 It gives you a central place to register factories for types/interfaces and then imperatively request instances of those types with **automatic cleanup** and **health checks**.
 
-It's a flexible Inversion-of-Control container that can be used for **dependency injection** or **service location**, but doesn't require global state, decorators, or mangling of function signatures.
+It's a flexible Inversion-of-Control container suitable for **dependency injection** or **service location**, while not requiring global state, decorators, or mangling of function signatures.
 
 <!-- begin benefits -->
 Benefits:

docs/typing-caveats.md

@@ -4,7 +4,7 @@
 
 If you try to `get()` an abstract class like an `Protocol` or an *abstract base classes* you'll get a Mypy error like this:
 
-```
+```text
 error: Only concrete class can be given where "type[P]" is expected  [type-abstract]
 ```
 

docs/why.md

@@ -2,7 +2,8 @@
 
 A {term}`service locator` like *svcs* allows you to configure and manage all your {term}`service`s in *one central place*, access them in a *consistent* way without worrying about *cleaning them up* and achieve *loose coupling*.
 
----
+
+## Modus Operandi
 
 In practice, that means that you say "*Give me a database connection*!" at runtime, and *svcs* will give you whatever you've configured to return when asked for a database connection.
 That can be an actual database connection, or it can be a mock object for testing.