Using longer names.

docs/permission.js

@@ -240,6 +240,8 @@ class PermissionOfferResponse {
  * the properties of Permission depend on what the permission is applied to, and so are
  * left undocumented here.
  * @since 2.3.0
+ *
+ * @memberof Realm.Sync
  */
 class Permission {
 
@@ -317,6 +319,9 @@ class Permission {
  * a Realm, and can also be created manually if you wish to grant permissions to a user
  * which has not yet connected to this Realm.
  * @since 2.3.0
+ * @class
+ * @name Realm.Sync.Permission.User
+ * @memberof Realm.Sync.Permission
  */
 class User {
     /**
@@ -337,6 +342,9 @@ class User {
  * connect to the Realm are automatically added to it. Any other roles you wish to use are
  * managed as normal Realm objects.
  * @since 2.3.0
+ * @class
+ * @name Realm.Sync.Permission.Role
+ * @memberof Realm.Sync.Permission
  */
 class Role {
     /**
@@ -358,6 +366,9 @@ class Role {
  * An instance of this object is automatically created in the Realm for class in your schema,
  * and should not be created manually.
  * @since 2.3.0
+ * @class
+ * @name Realm.Sync.Permission.Class
+ * @memberof Realm.Sync.Permission
  */
 class Class {
     /**
@@ -379,6 +390,9 @@ class Class {
  * An object of this type is automatically created in the Realm for you, and more objects
  * cannot be created manually.
  * @since 2.3.0
+ * @class
+ * @name Realm.Sync.Permission.Realm
+ * @memberof Realm.Sync.Permission
  */
 class Realm {
     /**

docs/sync.js

@@ -16,6 +16,7 @@
 //
 ////////////////////////////////////////////////////////////////////////////
 
+
 /**
  * When opening a Realm created with Realm Mobile Platform v1.x, it is automatically
  * migrated to the v2.x format. In case this migration
@@ -646,6 +647,7 @@ class Worker {
 
 /**
  * Class for creating custom Data Connectors. Only available in the Enterprise Edition.
+ *
  * @memberof Realm.Sync
  */
 class Adapter {