Fixed even more typos

config/logins.json

@@ -46,14 +46,14 @@
     "profiles": {
       "account1": {
         "explanation": "<b>R&S: displayName</b><br/>This profile provides a R&S compatible attribute bundle with the name of the user name being provided in the 'displayname' attribute",
-        "display": "R&S: display name",
+        "display": "Display name",
         "eduPersonPrincipalName": "jrockefeller@idp.example.org",
         "displayName": "John D. Rockefeller",
         "mail": "John.D.Rockefeller@idp.example.org"
       },
       "account2": {
         "explanation": "<b>R&S: surname + givename</b></br>This profile provides a R&S compatible attribute bundle with the name of the user name being provided in seperate 'surname' and 'givenname' attributes",
-        "display": "R&S: surname + givename",
+        "display": "Surname + givename",
         "eduPersonPrincipalName": "g_ohm@idp.example.org",
         "givenName": "Georg",
         "sn": "Ohm",
@@ -61,7 +61,7 @@
       },
       "account3": {
         "explanation": "<b>R&S: name and affiliation</b><br/>This profile provides a R&S compatible attribute bundle with the name of the user name being provided as 'displayname' and as seperate 'surname' and 'givenname' attributes. In addition the users affiliations are provided in the 'eduPersonScopedAffiliation' attribute",
-        "display": "R&S: name and affiliation",
+        "display": "Name and affiliation",
         "eduPersonPrincipalName": "jweeler@idp.example.org",
         "givenName": "Joseph",
         "sn": "Weeler",
@@ -74,7 +74,7 @@
       },
       "account4": {
         "explanation": "<b>R&S: ePPN and pseudonoymous epTID identifiers</b><br/>This profile provides a R&S compatible attribute bundle with the name of the user name being provided as 'displayname' and as seperate 'surname' and 'givenname' attributes. Please note the usage of both 'eduPersonPrincipalName' (ePPN) as well as 'eduPersonTargetedID' (ePTID)  which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point",
-        "display": "R&S: ePPN and pseudonoymous epTID identifiers",
+        "display": "ePPN and pseudonoymous epTID identifiers",
         "eduPersonPrincipalName": "awest@idp.example.org",
         "eduPersonTargetedID": "bd09168cf0c2e675b2def0ade6f50b7d4bb4aae",
         "givenName": "Anthony",
@@ -89,7 +89,7 @@
       },
       "account5": {
         "explanation": "<b>R&S: display name, ePPN and transparent epTID identifiers</b><br/>This profile provides a R&S compatible attribute bundle with the name of the user name being provided in the displayname attribute. Please note the usage of both 'eduPersonPrincipalName' (ePPN)  as well as 'eduPersonTargetedID' (ePTID) which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point",
-        "display": "R&S: display name, ePPN and transparent epTID identifiers",
+        "display": "Display name, ePPN and transparent epTID identifiers",
         "eduPersonPrincipalName": "bbernanke@idp.example.org",
         "eduPersonTargetedId": "bbernanke@idp.example.org",
         "displayName": "Ben Bernanke",
@@ -97,7 +97,7 @@
       },
       "account6": {
         "explanation": "<b>R&S: surname + givename, ePPN and transparent epTID identifiers</b><br/>This profile provides a R&S compatible attribute bundle with the name of the user name being provided as seperate 'surname' and 'givenname' attributes. Please note the usage of both 'eduPersonPrincipalName' (ePPN) as well as 'eduPersonTargetedID' (ePTID) which suggest the 'eduPersonPrincipalName' (ePPN) may not be a stable identifier, but may be reassigned at some point",
-        "display": "R&S: surname + givename, ePPN and transparent epTID identifiers",
+        "display": "Surname + givename, ePPN and transparent epTID identifiers",
         "eduPersonPrincipalName": "agreenspan@idp.example.org",
         "eduPersonTargetedId": "agreenspan@idp.example.org",
         "givenName": "Alan",
@@ -106,7 +106,7 @@
       },
       "account7": {
         "explanation": "<b>R&S: surname + givename, ePPN and epTID identifiers</b><br/>This profile provides a R&S compatible attribute bundle with the name of the user name being provided in the displayname attribute. Please note the usage of both 'eduPersonPrincipalName' (ePPN) as well as 'eduPersonTargetedID' (ePTID) which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point. In addition the users affiliations are provided in the 'eduPersonScopedAffiliation' attribute",
-        "display": "R&S: surname + givename, ePPN and epTID identifiers",
+        "display": "Surname + givename, ePPN and epTID identifiers",
         "eduPersonPrincipalName": "am_ampere@idp.example.org",
         "eduPersonTargetedId": "am_ampere@idp.example.org",
         "displayName": "André-Marie Ampère",
@@ -120,7 +120,7 @@
       },
       "account8": {
         "explanation": "<b>R&S: surname + givename, ePPN and epTID identifiers</b><br/>This profile provides a R&S compatible attribute bundle with the name of the user name being provided as seperate 'surname' and 'givenname' attributes.Please note the usage of both 'eduPersonPrincipalName' (ePPN) as well as 'eduPersonTargetedID' (ePTID) which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point. In addition the users affiliations are provided in the 'eduPersonScopedAffiliation' attribute",
-        "display": "R&S: surname + givename, ePPN and epTID identifiers",
+        "display": "Surname + givename, ePPN and epTID identifiers",
         "eduPersonPrincipalName": "w_rontgen@idp.example.org",
         "eduPersonTargetedId": "w_rontgen@idp.example.org",
         "givenName": "Wilhelm",