Clarify about Distribution::Resource

Closes #3095

Author: coke

doc/Language/modules.rakudoc

@@ -783,10 +783,12 @@ C<META6.json>) so that the distribution path can be provided to the program.
 }
 =end code
 
-The additional file can then be accessed inside module code:
+The additional file can then be accessed inside module code. Note the
+example here is returning a L<C<Distribution::Resource>|/type/Distribution::Resource> object. It should
+B<not> be considered as a path to an object in the filesystem.
+
 =begin code
 my $template-text = %?RESOURCES<templates/default-template.mustache>.slurp;
-# Note that %?RESOURCES provides a C<IO> path object
 =end code
 
 =end item
@@ -931,8 +933,11 @@ newer ones, use C<6.d> if it requires, at least the Diwali version.
 The C<resources> section is optional, but if present, should contain a list
 of the files in your C<resources> directory that you wish to be installed.
 These will be installed with hashed names alongside your library files.
-Their installed location can be determined through the C<%?RESOURCES> L<C<Hash>|/type/Hash>
-indexed on the name provided. The C<tags> section is also optional. It is used to describe
+B<Note>: Accessing these files via C<%?RESOURCES> is B<not>
+getting their installed locations or an L<C<IO>|/type/IO> class: You are accessing a L<C<Distribution::Resource>|/type/Distribution::Resource>.
+object indexed on the name provided.
+
+The C<tags> section is also optional. It is used to describe
 the module in the Raku ecosystem.
 
 The C<depends>, C<build-depends>, and C<test-depends> sections include different modules that