remove .ttl from RDFSource URIs

content-representation.md

@@ -42,7 +42,7 @@ Our motivation is threefold:
   even though the resource is stored as a Turtle file).
 
  3. Direct mapping: the URLs map directly to the file system resources -- i.e.
-  `https://example.org/test.ttl` maps to `/home/user/www/test.ttl`
+  `https://example.org/avatar.png` maps to `/home/user/www/avatar.png`
 
 Servers must support the HEAD method for reading data. This returns a list of
 headers related to the resource in question. Among these headers, two very

recommendations-server.md

@@ -49,7 +49,7 @@ space#preferencesFile](http://www.w3.org/ns/pim/space#preferencesFile) property.
 
 ```ttl
 <#me>
-    <http://www.w3.org/ns/pim/space#preferencesFile> <../settings/preferences.ttl> ;
+    <http://www.w3.org/ns/pim/space#preferencesFile> <../settings/preferences> ;
 ```
 
 ##### `/inbox/` (Inbox)

solid-webid-profiles.md

@@ -140,7 +140,7 @@ across several RDF documents:
 
 * `/profile/card` - their primary (public-readable) WebID Profile.
   Which would contain a `space:preferencesFile` link to:
-* `/settings/prefs.ttl` - a private (only the user has read/write access)
+* `/settings/preferences` - a private (only the user has read/write access)
   Preferences file which contains further profile-related statements.
 
 ### Extended Profile
@@ -247,16 +247,16 @@ For example, a link to the Listed Type Index in the main profile document:
 <#me>
     a foaf:Person ;
     <http://www.w3.org/ns/solid/terms#publicTypeIndex>
-        </settings/publicTypeIndex.ttl> .
+        </settings/publicTypeIndex> .
 ```
 
 And an example corresponding link to the Unlisted Type Index, in a private
 resources of the Extended Profile, such as the Preferences file
-(in `/settings/prefs.ttl`):
+(in `/settings/preferences`):
 
 ```ttl
 # ...
 <#me>
     <http://www.w3.org/ns/solid/terms#privateTypeIndex>
-        </settings/privateTypeIndex.ttl> .
+        </settings/privateTypeIndex> .
 ```