diff --git a/docs/simplesamlphp-idp-more.txt b/docs/simplesamlphp-idp-more.txt
index 25fcaf049f1d4a2752abbe96019ba69fe53a5de1..60d2c4626fcaf0173b1b4e656f1e1be9c2fb9930 100644
--- a/docs/simplesamlphp-idp-more.txt
+++ b/docs/simplesamlphp-idp-more.txt
@@ -46,7 +46,7 @@ If you do not want to start the SSO flow at the SP, you may use the IdP-first se
 
 Here is an example of such an url:
 
-	https://idp.example.org/simplesaml/saml2/idp/SSOService.php?spentityid=dev.andreas.feide.no
+	https://idp.example.org/simplesaml/saml2/idp/SSOService.php?spentityid=urn:mace:feide.no:someservice
 
 You can also add a RelayState parameter to the IdP-first URL:
 
@@ -73,10 +73,12 @@ The parameters are as follows:
     This parameter is required.
 
 `target`
-:   The target parameter the SP should receive.
+:   The target parameter the SP should receive with the authentication response.
     This is often the page the user should be sent to after authentication.
     This parameter is optional for the IdP, but must be specified if the SP you are targeting is running simpleSAMLphp SP.
 
+:   *Note*: This parameter must be sent as `target` (with lowercase letters) when starting the authentication, while it is sent as `TARGET` (with uppercase letters) in the authentication response.
+
 
 IdP-initiated logout
 --------------------
diff --git a/modules/saml/docs/sp.txt b/modules/saml/docs/sp.txt
index be2d7de7b26590f79554882083f3b970beafa675..90b1f0dabeb9e121a1db66a01d819ce0d55637f5 100644
--- a/modules/saml/docs/sp.txt
+++ b/modules/saml/docs/sp.txt
@@ -319,7 +319,9 @@ Options
 :   The page the user should be redirected to after an IdP initiated SSO.
 
 :   *Note*: SAML 2 specific.
-    For SAML 1.1 SPs, you must specify the `TARGET` in the authentication response.
+    For SAML 1.1 SPs, you must specify the `TARGET` parameter in the authentication response.
+    How to set that parameter is depends on the IdP.
+    For simpleSAMLphp, see the documentation for [IdP-first flow](./simplesamlphp-idp-more#section_4_1).
 
 `url`
 :   An URL to your service provider. Will be added as an OrganizationURL-element in the metadata.