From be3cc407634bc057c3e46f14768140688d367356 Mon Sep 17 00:00:00 2001
From: giuliaelgarcia <147185635+giuliaelgarcia@users.noreply.github.com>
Date: Tue, 5 Mar 2024 11:14:49 +0000
Subject: [PATCH] Update integration.md

---
 docs/workflows/integration.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/workflows/integration.md b/docs/workflows/integration.md
index ec09341c..c690cc68 100644
--- a/docs/workflows/integration.md
+++ b/docs/workflows/integration.md
@@ -25,4 +25,4 @@ The ideal way to run `panpipes integration` is to use the output `MuData` file f
 The MuData object required should contain normalised data in the X slot of each modality,  a 'raw_counts' layer in each modality, and a sample_id column in each slot of the obs and the outer obs. A plus is a PCA in the obsm slot for each modality, if not it will be calculated on the flight with default parameters.
 
  ## Algorithms supported by panpipes for uni and multimodal integration 
- Please check [Integration methods implemented in panpipes](https://github.com/DendrouLab/panpipes/blob/docs_g/docs/usage/integration_methods.md)  for a description of the algorithms used in the integration step. 
+ Please check [Integration methods implemented in panpipes](https://github.com/DendrouLab/panpipes/blob/docs_g/docs/usage/integration_methods.md)  for a description of the algorithms and source references for the methods used in the integration step.