Update paths in docs and examples

docsite/source/component-dirs.html.md

@@ -201,7 +201,7 @@ Set this to false if you’re using dry-container with an autoloader.
 When using a class autoloader, consider setting this to `Dry::System::Loader::Autoloading`:
 
 ```ruby
-require "dry/system/loader/autoloading"
+require "dry/system"
 
 class Application < Dry::System::Container
   configure do |config|

docsite/source/container.html.md

@@ -9,7 +9,7 @@ The main API of dry-system is the abstract container that you inherit from. It a
 Let's say you want to define an application container that will provide a logger:
 
 ``` ruby
-require 'dry/system/container'
+require 'dry/system'
 
 class Application < Dry::System::Container
   configure do |config|
@@ -32,7 +32,7 @@ By using simple naming conventions we can automatically register objects within
 Let's provide a custom logger object and put it under a custom load-path that we will configure:
 
 ``` ruby
-require 'dry/system/container'
+require 'dry/system'
 
 class Application < Dry::System::Container
   configure do |config|

docsite/source/dependency-auto-injection.html.md

@@ -41,7 +41,7 @@ Here's a sample setup for this scenario:
 
 ``` ruby
 # system/container.rb
-require "dry/system/container"
+require "dry/system"
 
 class Application < Dry::System::Container
   configure do |config|

docsite/source/external-provider-sources.html.md

@@ -39,7 +39,7 @@ Then you can use this provider source when you register a provider in a dry-syst
 ``` ruby
 # system/app/container.rb
 
-require "dry/system/container"
+require "dry/system"
 require "my_gem/provider_sources"
 
 module App

docsite/source/settings.html.md

@@ -11,7 +11,7 @@ dry-system provides a `:settings` provider source that you can use to load setti
 ```ruby
 # system/providers/settings.rb:
 
-require "dry/system/provider_sources"
+require "dry/system"
 
 Application.register_provider(:settings, from: :dry_system) do
   before :prepare do

docsite/source/test-mode.html.md

@@ -8,7 +8,7 @@ In some cases it is useful to stub a component in your tests. To enable this, dr
 in which a container will not be frozen during finalization. This allows you to use `stub` API to stub a given component.
 
 ``` ruby
-require 'dry/system/container'
+require 'dry/system'
 
 class Application < Dry::System::Container
   configure do |config|

examples/custom_configuration_auto_register/system/container.rb

@@ -1,6 +1,6 @@
 # frozen_string_literal: true
 
-require "dry/system/container"
+require "dry/system"
 
 class App < Dry::System::Container
   configure do |config|

examples/standalone/system/container.rb

@@ -2,7 +2,7 @@
 
 require "dry/events"
 require "dry/monitor/notifications"
-require "dry/system/container"
+require "dry/system"
 
 class App < Dry::System::Container
   use :dependency_graph

examples/zeitwerk/system/container.rb

@@ -1,6 +1,6 @@
 # frozen_string_literal: true
 
-require "dry/system/container"
+require "dry/system"
 
 class App < Dry::System::Container
   use :env, inferrer: -> { ENV.fetch("RACK_ENV", :development).to_sym }

lib/dry/system/container.rb

@@ -148,7 +148,7 @@ def configured?
         #
         # @example
         #   # system/container.rb
-        #   require "dry/system/container"
+        #   require "dry/system"
         #   require "logger"
         #
         #   class Core < Dry::System::Container