Update README.md

README.md

@@ -33,6 +33,7 @@
   * [Relationship Mapping](#relationship-mapping)
     * [One-to-many](#one-to-many)
     * [One-to-one](#one-to-one)
+    * [One-to-one (simplified)](#one-to-one-simplified)
   * [Networking](#networking)
   * [Supported iOS, OS X, watchOS and tvOS Versions](#supported-ios-os-x-watchos-and-tvos-versions)
 * [Components](#components)
@@ -294,6 +295,8 @@ This model is simple, a user as a company. A compatible JSON would look like thi
 ]
 ```
 
+#### One-to-one Simplified
+
 As you can see this procedures require the full JSON object to be included, but when working with APIs, sometimes you already have synced all the required items. Sync supports this too.
 
 For example, in the one-to-one example, you have a user, that has one company. If you already have synced all the companies then your JSON would only need the `company_id`. As a sidenote only do this if you are 100% sure that all the required items (companies) have been synced.