Readme updates

Author: Will Meek

README.md

@@ -174,24 +174,26 @@ The generated unit tests in `spec/unit/puppet/provider/foo_spec.rb` get automati
 
 ## Remote Resources
 
-Support for remote resources is enabled through the use of a `transport`. A transport class conatins the code for managing connections and processing information to/from the remote resource. Please see the [RSAPI specification](https://github.com/puppetlabs/puppet-specifications/tree/master/language/resource-api#transport) document on how to create a transport.
+Support for remote resources is enabled through the use of a `transport` class. A transport class contains the code for managing connections and processing information to/from the remote resource. Please see the [Resource API specification](https://github.com/puppetlabs/puppet-specifications/tree/master/language/resource-api#transport) document on how to create a transport class.
 
 ### `puppet device` support
 
-To connect to a remote resource through `puppet device` a `transport` must be called through a device shim.
+To connect to a remote resource through `puppet device` a `transport` class must be called through a device shim.
+
+For example:
 
 ```ruby
-# lib/puppet/util/network_device/remote_thing.rb
+# lib/puppet/util/network_device/device_type/device.rb
 
 require 'puppet'
 require 'puppet/resource_api/transport/wrapper'
-# force registering the transport
-require 'puppet/transport/schema/remote_thing'
+# force registering the transport schema
+require 'puppet/transport/schema/device_type'
 
-module Puppet::Util::NetworkDevice::RemoteThing
+module Puppet::Util::NetworkDevice::DeviceType
   class Device < Puppet::ResourceApi::Transport::Wrapper
     def initialize(url_or_config, _options = {})
-      super('remote_thing', url_or_config)
+      super('device_type', url_or_config)
     end
   end
 end
@@ -201,7 +203,7 @@ After this, `puppet device` will be able to use the new provider, and supply it
 
 #### Transport/Device specific providers
 
-To allow modules to deal with different backends independently of each other, the Resource API also implements a mechanism to use different API providers side-by-side. For a given transport/device (see above), the Resource API will first try to load a `Puppet::Provider::TypeName::DeviceType` class from `lib/puppet/provider/type_name/device_type.rb`, before falling back to the regular provider at `Puppet::Provider::TypeName::TypeName`.
+To allow modules to deal with different backends independently of each other, the Resource API also implements a mechanism to use different API providers side-by-side. For a given transport/device class (see above), the Resource API will first try to load a `Puppet::Provider::TypeName::DeviceType` class from `lib/puppet/provider/type_name/device_type.rb`, before falling back to the regular provider at `Puppet::Provider::TypeName::TypeName`.
 
 ## Further Reading