dexter has uploaded this change for review. ( https://gerrit.osmocom.org/c/onomondo-eim/+/43654?usp=email )

Change subject: esipa_asn1_handler: fix typos ......................................................................

esipa_asn1_handler: fix typos

Related: SYS#8100 Change-Id: I14416250cdb523f5c1a20d3a3e3dbe5cc6c53bcd --- M src/esipa_asn1_handler.erl 1 file changed, 2 insertions(+), 2 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/onomondo-eim refs/changes/54/43654/1

diff --git a/src/esipa_asn1_handler.erl b/src/esipa_asn1_handler.erl index 2fe7603..f53b177 100644 --- a/src/esipa_asn1_handler.erl +++ b/src/esipa_asn1_handler.erl @@ -229,8 +229,8 @@ % Sub-procedure Profile Installation (see also GSMA SGP.22, section 3.1.3.3). The eIM uses the % result data contained in this message to conclude the download and to make the download results % available to the REST API user. However, in rare cases it is possible that a - % ProfileInstallationResult is received way too late as part of the Notification Delivery to - % Notification Receivers (see also GSMA SGP.32, section 3.7) procedure. By then the context in the + % ProfileInstallationResult is received way too late as part of the notification delivery to + % notification receivers (see also GSMA SGP.32, section 3.7) procedure. By then the context in the % eIM may be long gone. The eIM will be unable to match the ProfileInstallationResult to any % context but it will foward it to the SMDP+ anyway. case mnesia_db_work:bind(Pid, TransactionId) of