Update README.md

README.md

@@ -18,7 +18,7 @@ The data is broadcast via UDP on a specified port, and can be received using the
 
 ### Difference with the ZED Unity Plugin
 
-The ZED Unity plugin, available [here](), is a full integration of the SDK features in Unity, except for the multi-camera data fusion. It comes as an Unity Package, allowing dialogue between your project and all the ZED SDK capabilities. 
+The ZED Unity plugin, available [here](https://github.com/stereolabs/zed-unity), is a full integration of the SDK features in Unity, except for the multi-camera data fusion. It comes as an Unity Package, allowing dialogue between your project and all the ZED SDK capabilities. 
 
 This sample comes as an alternative and a complement, allowing your Unity project to receive only **Body Tracking data**, from one or several cameras. The Unity project provided does not implement any dialogue with the SDK, only being able to receive data from the sender tools (not the SDK directly).
 
@@ -57,7 +57,7 @@ Main prefabs :
 
 - First, download and install the latest version of the ZED SDK on [stereolabs.com](https://www.stereolabs.com/developers/) (**Minimum requirement: ZED SDK v4.0**).
     - For more information, read the ZED [Documentation](https://www.stereolabs.com/docs) and [API documentation](https://www.stereolabs.com/docs/api/)
-- Download the C++ samples and the Unity project (or unitypackage) on the [Releases page](). You can also directly pull the master branch of the repo for an up-to-date version.
+- Download the C++ samples and the Unity project (or unitypackage) on the Releases page on this repo. You can also directly pull the `main` branch of the repo for an up-to-date version.
 - Generate either or both of the projects (`fusion` or `mono`) using CMake.
 - Open the `main.cpp` file and set the `servAddress` and `servPort` variables with your desired address and port.
     - The default values are `230.0.0.1` for the IP and `20001` for the port.
@@ -81,7 +81,7 @@ Main prefabs :
     // ----------------------------------
 ```
 
-- Build the sample and execute it, passing your calibration file (see [the documentation about ZED360]() for more details) as argument, if you're using the Fusion sender, or either nothing or your SVO file for the mono-camera sender.
+- Build the sample and execute it, passing your calibration file generated by ZED360 as argument, if you're using the Fusion sender, or either nothing or your SVO file for the mono-camera sender.
 ```
 > path/to/the/ZED_Sender_Fusion.exe path/to/the/calib_file.json
 ```
@@ -104,8 +104,8 @@ These are located on the `ZED Skeleton Tracking Manager` script in the `Fusion M
 - `Enable Avatar` / `Enable SDK Skeleton` : controls the visibility of the 3D avatar and of the skeleton directly derived from the keypoints of the SDK.
 - `Avatars` : Array of 3D avatars randomly chosen when detecting a new person.
     - All of Unity **Humanoid** avatars should be compatible, provided they are made into a prefab with a `ZEDSkeletonAnimator` component attached.
-- `Enable SDK Skeleton` : controls the visibility of the *stickman* view of the SDK keypoints. Whereas the 3D avatar is animated using local rotations derived from the keypoints, this show the actual positions of the keypoints detected by the SDK.
-- `Log Fusion Metrics` : enables logging the metrics sent by the Fusion module in the console. More information in the [Fusion Documentation]().
+- `Enable SDK Skeleton` : controls the visibility of the stickman view of the SDK keypoints. Whereas the 3D avatar is animated using local rotations derived from the keypoints, this show the actual positions of the keypoints detected by the SDK.
+- `Log Fusion Metrics` : enables logging the metrics sent by the Fusion module in the console.
 
 ## Support
 You will find guidance and assistance :