fix some local links

Author: assafvayner

docs/hub/xet/deduplication.md

@@ -147,7 +147,7 @@ Each chunk has its content hashed using a cryptographic hash function (Blake3-ba
 
 ### Xorb Formation
 
-When new chunks need to be stored, they are aggregated into xorbs based on size and count limits. If adding a new chunk would exceed the maximum xorb size or chunk count, the current xorb is finalized and uploaded. [See section about xorb formation](../xorb)
+When new chunks need to be stored, they are aggregated into xorbs based on size and count limits. If adding a new chunk would exceed the maximum xorb size or chunk count, the current xorb is finalized and uploaded. [See section about xorb formation](./xorb)
 
 ### File Reconstruction Information
 

docs/hub/xet/download-protocol.md

@@ -17,6 +17,7 @@ To download a file given a file hash, first call the reconstruction API to get t
 
 Note that you will need at least a `read` scope auth token, [auth reference](./auth).
 
+> [!TIP]
 > For large files it is RECOMMENDED to request the reconstruction in batches i.e. the first 10GB, download all the data, then the next 10GB and so on. Clients can use the `Range` header to specify a range of file data.
 
 ## Stage 2: Understanding the Reconstruction Response
@@ -25,8 +26,6 @@ The reconstruction API returns a `QueryReconstructionResponse` object with three
 
 ### QueryReconstructionResponse Structure
 
-Scroll
-
 ```json
 {
   "offset_into_first_range": 0,
@@ -172,7 +171,7 @@ The downloaded data is in xorb format and MUST be deserialized:
 3. **Extract byte indices**: Track byte boundaries between chunks for range extraction
 4. **Validate length**: Decompressed length MUST match `unpacked_length` from the term
 
-**Note**: The specific deserialization process depends on the [Xorb format](../xorb).
+**Note**: The deserialization process depends on the [Xorb format](./xorb).
 
 ```python
 for term in terms:

docs/hub/xet/shard.md

@@ -260,7 +260,7 @@ struct FileDataSequenceEntry {
 
 Verification Entries MUST be set for shard uploads.
 
-To generate verification hashes for shard upload read the section about [Verification Hashes](../hashing#Term%20Verification%20Hashes).
+To generate verification hashes for shard upload read the section about [Verification Hashes](./hashing#Term-Verification-Hashes).
 
 ```rust
 struct FileVerificationEntry {

docs/hub/xet/xorb.md

@@ -111,7 +111,7 @@ Note that a Xorb MAY contain chunks that utilize different compression schemes.
 2. **Best Effort Prediction**
 
     In `xet-core`, to predict if BG4 will be useful we maximum KL divergence between the distribution of per-byte pop-counts on a sample of each of the 4 groups that would be formed.
-    You can read more about it in [bg4_prediction.rs](../cas_object/src/byte_grouping/bg4_prediction.rs) and accompanying scripts.
+    You can read more about it in [bg4_prediction.rs](./cas_object/src/byte_grouping/bg4_prediction.rs) and accompanying scripts.
 
     If the predictor does not show that BG4 will be better, we use Lz4 and in either case we will store the chunk as the uncompressed version if the compression scheme used does not show any benefit.