Skip to content

Commit f2dbd48

Browse files
authored
QA
editorial
1 parent 9ad1c64 commit f2dbd48

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -553,7 +553,7 @@ <h3 class="heading settled" data-level="2.1" id="terminology"><span class="secno
553553
<p>Let us then try to understand the <em>authentication</em> process and how it differs from identification, verification, and authorization:</p>
554554
<ul>
555555
<li data-md>
556-
<p><strong>Identification</strong> is recognizing an entity through the information it provides. For example, we enter our first name, surname, and email address in a social network (and there are different levels of proofing of our real-identity).</p>
556+
<p><strong>Identification</strong> is recognizing an entity through the information it provides. For example, we enter our first name, surname, and email address in a social network (and there are different levels of proofing of our real identity).</p>
557557
<li data-md>
558558
<p><strong>Verification</strong> allows us to confirm that the presented information is valid through further testing. Verification is a generic process that can take different forms and have different effects. For example, we often receive an email with a confirmation link to verify an email address. We confirm that the email address is under our control by clicking on it. This type of verification demonstrates control over the identifier. Verifying identity information online, such as a specific name and surname, is more complex. When verifying identity information, we use the term <em>identity verification</em>.</p>
559559
<li data-md>

0 commit comments

Comments
 (0)