diff --git a/matlab/IMAS/gdat_imas.m b/matlab/IMAS/gdat_imas.m
index f0190f2e5a3e44483d7d647e607eee5fd50d34c3..9a32ab2feed4fb9be1bcffcc690bf065139455ef 100644
--- a/matlab/IMAS/gdat_imas.m
+++ b/matlab/IMAS/gdat_imas.m
@@ -7,8 +7,9 @@ function [gdat_data,gdat_params,error_status,varargout] = gdat_imas(shot,data_re
 %
 % If no inputs are provided, return the list of available pre-defined data_request in gdat_data and default parameters gdat_params
 %
-% IMAS assumes data access from IDS database ala IMAS with run_number, database_user, tokamak_name, data_major_version and  using imas_open_env and ids_get calls (added backend choice as well, default hdf5 (13), otherwise 12 for mdsplus)
-% Should be the same on ITER hpc and gateway, to be checked
+% IMAS assumes data access layer from IDS database ala IMAS with run_number, database_user, tokamak_name, data_major_version
+%      using imas_open_env/imas_create_env_backend and ids_get calls (added backend choice as well, default hdf5 (13), otherwise 12 for mdsplus)
+% Same calls at ITER, gateway, spcimas, ...
 %
 % At first only "ids" request implemented, but keywords like ip etc should relate to specific IDS as for any machine
 %