Add remarks buckets of sub-types and nature of referenced relationships

src/main/asciidoc/concepts/basics.adoc

@@ -122,6 +122,7 @@ It is comparable to the "collection" in Document databases, the "table" in Relat
 You can have up to 2,147,483,648 buckets in a database.
 
 A bucket can only be part of one type. This means two types can not share the same bucket.
+Also, <<Inheritance,sub-types>> have their separate buckets from their super-types.
 
 When you create a new type, the <<SQL-Create-Type,`CREATE TYPE`>> statement automatically creates the physical buckets (files) that serve as the default location in which to store data for that type.
 ArcadeDB forms the bucket names by using the type name + underscore + a sequential number starting from 0. For example, the first bucket for the type `Beer` will be `Beer_0` and the correspondent file in the file system will be `Beer_0.31.65536.bucket`.
@@ -237,7 +238,7 @@ It can manage relationships in a schema-full or schema-less scenario.
 ==== Referenced Relationships
 
 In Relational databases, tables are linked through `JOIN` commands, which can prove costly on computing resources.
-ArcadeDB manages relationships natively without computing a `JOIN` but storing direct links to the target objects of the relationship. This boosts the load speed for the entire graph of connected objects, such as in graph and object database systems.
+ArcadeDB manages relationships natively without computing a `JOIN` but storing a direct `LINK` to the target object of the relationship. This boosts the load speed for the entire graph of connected objects, such as in graph and object database systems.
 
 Example
 
@@ -247,6 +248,10 @@ Example
     RID #5:23               RID #10:2
 ```
 
+Note, that referenced relationships differ from edges:
+references are properties connecting any record while edges are types connecting vertices,
+and particularly, graph traversal is only applicable to edges.
+
 [discrete]
 ==== Embedded Relationships