Better naming conventions.

Author: samuel-williams-shopify

context/best-practices.md

@@ -61,7 +61,7 @@ Place environments in `lib/my_library/environment/`:
 module MyLibrary
 	module Environment
 		module WebEnvironment
-			include Async::Service::Managed::Environment
+			include Async::Service::ManagedEnvironment
 
 			def service_class
 				MyLibrary::Service::WebService
@@ -87,7 +87,7 @@ Place services in `lib/my_library/service/`:
 # lib/my_library/service/web_service.rb
 module MyLibrary
 	module Service
-		class WebService < Async::Service::Managed::Service
+		class WebService < Async::Service::ManagedService
 			private def format_title(evaluator, server)
 				if server&.respond_to?(:connection_count)
 					"#{self.name} [#{evaluator.host}:#{evaluator.port}] (#{server.connection_count} connections)"
@@ -114,11 +114,11 @@ end
 
 ### Use `Managed::Environment` for Services
 
-Include {ruby Async::Service::Managed::Environment} for services that need robust lifecycle management using {ruby Async::Service::Managed::Service}:
+Include {ruby Async::Service::ManagedEnvironment} for services that need robust lifecycle management using {ruby Async::Service::ManagedService}:
 
 ```ruby
 module WebEnvironment
-	include Async::Service::Managed::Environment
+	include Async::Service::ManagedEnvironment
 
 	def service_class
 		WebService
@@ -201,10 +201,10 @@ end
 
 ### Use `Managed::Service` as Base Class
 
-Prefer `Async::Service::Managed::Service` over `Generic` for most services:
+Prefer `Async::Service::ManagedService` over `GenericService` for most services:
 
 ```ruby
-class WebService < Async::Service::Managed::Service
+class WebService < Async::Service::ManagedService
 	# Managed::Service automatically handles:
 	# - Container setup with proper options.
 	# - Health checking with process title updates.
@@ -247,7 +247,7 @@ Try to keep process titles short and focused.
 Utilize the `start` and `stop` hooks to manage shared resources effectively:
 
 ```ruby
-class WebService < Async::Service::Managed::Service
+class WebService < Async::Service::ManagedService
 	def start
 		# Bind to the endpoint in the container:
 		@endpoint = @evaluator.endpoint.bind

context/deployment.md

@@ -11,10 +11,10 @@ Let's start with a simple HTTP service that we'll deploy:
 # frozen_string_literal: true
 
 require "async/http"
-require "async/service/managed/service"
-require "async/service/managed/environment"
+require "async/service/managed_service"
+require "async/service/managed_environment"
 
-class WebService < Async::Service::Managed::Service
+class WebService < Async::Service::ManagedService
 	def start
 		super
 		@endpoint = @evaluator.endpoint
@@ -40,7 +40,7 @@ class WebService < Async::Service::Managed::Service
 end
 
 module WebEnvironment
-	include Async::Service::Managed::Environment
+	include Async::Service::ManagedEnvironment
 
 	def endpoint
 		Async::HTTP::Endpoint.parse("http://0.0.0.0:3000")

context/getting-started.md

@@ -14,13 +14,13 @@ $ bundle add async-service
 
 `async-service` has several core concepts:
 
-- A {ruby Async::Service::Generic} which represents the base class for implementing services.
+- A {ruby Async::Service::GenericService} which represents the base class for implementing services.
 - A {ruby Async::Service::Configuration} which manages service configurations and environments.
 - A {ruby Async::Service::Controller} which handles starting, stopping, and managing services.
 
 ## Usage
 
-Services are long-running processes that can be managed as a group. Each service extends `Async::Service::Generic` and implements a `setup` method that defines how the service runs.
+Services are long-running processes that can be managed as a group. Each service extends `Async::Service::GenericService` and implements a `setup` method that defines how the service runs.
 
 ### Basic Service
 
@@ -31,7 +31,7 @@ Create a simple service that runs continuously:
 
 require "async/service"
 
-class HelloService < Async::Service::Generic
+class HelloService < Async::Service::GenericService
 	def setup(container)
 		super
 
@@ -73,7 +73,7 @@ end
 In your service implementation, you can access these values through the environment and evaluator:
 
 ```ruby
-class WebServerService < Async::Service::Generic
+class WebServerService < Async::Service::GenericService
 	def setup(container)
 		super
 
@@ -103,7 +103,7 @@ You can define multiple services in a single configuration file:
 
 require "async/service"
 
-class WebService < Async::Service::Generic
+class WebService < Async::Service::GenericService
 	def setup(container)
 		super
 
@@ -115,7 +115,7 @@ class WebService < Async::Service::Generic
 	end
 end
 
-class WorkerService < Async::Service::Generic
+class WorkerService < Async::Service::GenericService
 	def setup(container)
 		super
 

context/service-architecture.md

@@ -82,14 +82,14 @@ end
 
 ## Service
 
-The {ruby Async::Service::Generic} represents the service implementation layer. It handles the actual business logic of your services, provides access to configuration through environment evaluators, and manages the service lifecycle including startup, execution, and shutdown phases.
+The {ruby Async::Service::GenericService} represents the service implementation layer. It handles the actual business logic of your services, provides access to configuration through environment evaluators, and manages the service lifecycle including startup, execution, and shutdown phases.
 
 ### Business Logic
 
 Services contain the actual implementation of what your service does:
 
 ```ruby
-class WebService < Async::Service::Generic
+class WebService < Async::Service::GenericService
 	def setup(container)
 		super
 
@@ -148,7 +148,7 @@ By evaluating the log_path in the child process, you ensure that each instance h
 Services define their startup, running, and shutdown behavior:
 
 ```ruby
-class MyService < Async::Service::Generic
+class MyService < Async::Service::GenericService
 	def start
 		super
 		# Service-specific startup logic including pre-loading libraries and binding to network interfaces before forking.
@@ -262,7 +262,7 @@ end
 
 ### Health Checking
 
-For services using `Async::Service::Managed::Service`, health checking is handled automatically. For services extending `Generic`, you can set up health checking manually:
+For services using `Async::Service::ManagedService`, health checking is handled automatically. For services extending `GenericService`, you can set up health checking manually:
 
 ```ruby
 def setup(container)
@@ -284,7 +284,7 @@ def setup(container)
 end
 ```
 
-Note: `Async::Service::Managed::Service` automatically handles health checking, container options, and process title formatting, so you typically don't need to set this up manually.
+Note: `Async::Service::ManagedService` automatically handles health checking, container options, and process title formatting, so you typically don't need to set this up manually.
 
 ## How They Work Together
 
@@ -305,7 +305,7 @@ end
 
 ```ruby
 # Services are defined using environments:
-class WebService < Async::Service::Generic
+class WebService < Async::Service::GenericService
 	def setup(container)
 		super
 
@@ -440,7 +440,7 @@ Create reusable configuration modules:
 
 ```ruby
 module ManagedEnvironment
-	include Async::Service::Managed::Environment
+	include Async::Service::ManagedEnvironment
 
 	def count
 		4
@@ -464,7 +464,7 @@ end
 Build service hierarchies:
 
 ```ruby
-class BaseWebService < Async::Service::Generic
+class BaseWebService < Async::Service::GenericService
 	def setup(container)
 		super
 		# Common web service setup

examples/deployment/server.rb

@@ -2,10 +2,10 @@
 # frozen_string_literal: true
 
 require "async/http"
-require "async/service/managed/service"
-require "async/service/managed/environment"
+require "async/service/managed_service"
+require "async/service/managed_environment"
 
-class WebService < Async::Service::Managed::Service
+class WebService < Async::Service::ManagedService
 	def start
 		super
 		@endpoint = @evaluator.endpoint
@@ -31,7 +31,7 @@ def run(instance, evaluator)
 end
 
 module WebEnvironment
-	include Async::Service::Managed::Environment
+	include Async::Service::ManagedEnvironment
 
 	def endpoint
 		Async::HTTP::Endpoint.parse("http://0.0.0.0:3000")

examples/hello/hello.rb

@@ -4,7 +4,7 @@
 # Released under the MIT License.
 # Copyright, 2024-2025, by Samuel Williams.
 
-class SleepService < Async::Service::Generic
+class SleepService < Async::Service::GenericService
 	def setup(container)
 		super
 

examples/hello/readme.md

@@ -27,7 +27,7 @@ Press `Ctrl+C` to stop the service.
 The example defines a simple service class:
 
 ~~~ ruby
-class SleepService < Async::Service::Generic
+class SleepService < Async::Service::GenericService
 	def setup(container)
 		super
 
@@ -45,7 +45,7 @@ end
 
 Key points:
 
-- **Inherits from `Async::Service::Generic`**: Provides the basic service interface
+- **Inherits from `Async::Service::GenericService`**: Provides the basic service interface
 - **Implements `setup(container)`**: Defines how the service runs
 - **Uses `container.run`**: Creates one instance with automatic restart
 - **Calls `instance.ready!`**: Signals the service is ready

examples/ipc/client.rb

@@ -16,7 +16,7 @@
 	ipc_socket_path File.expand_path("service.ipc", Dir.pwd)
 end
 
-class IPCClient < Async::Service::Generic
+class IPCClient < Async::Service::GenericService
 	def setup(container)
 		super
 

examples/ipc/server.rb

@@ -15,7 +15,7 @@
 	ipc_socket_path File.expand_path("service.ipc", Dir.pwd)
 end
 
-class IPCServer < Async::Service::Generic
+class IPCServer < Async::Service::GenericService
 	def setup(container)
 		super
 

examples/ipc/service.rb

@@ -6,11 +6,11 @@
 
 require "socket"
 require "async"
-require "async/service/managed/service"
-require "async/service/managed/environment"
+require "async/service/managed_service"
+require "async/service/managed_environment"
 
 # Server service that listens on a Unix domain socket and responds with "Hello World"
-class IPCServer < Async::Service::Managed::Service
+class IPCServer < Async::Service::ManagedService
 	def run(instance, evaluator)
 		socket_path = evaluator.ipc_socket_path
 
@@ -47,7 +47,7 @@ def run(instance, evaluator)
 end
 
 # Client service that periodically connects to the server
-class IPCClient < Async::Service::Managed::Service
+class IPCClient < Async::Service::ManagedService
 	def run(instance, evaluator)
 		socket_path = evaluator.ipc_socket_path
 		timeout = evaluator.ipc_connection_timeout
@@ -88,7 +88,7 @@ def run(instance, evaluator)
 end
 
 module IPCEnvironment
-	include Async::Service::Managed::Environment
+	include Async::Service::ManagedEnvironment
 
 	def ipc_socket_path
 		File.expand_path("service.ipc", Dir.pwd)