Edited chapter_22_fixtures_and_wait_decorator.asciidoc with Atlas code editor

Author: troutman_margaret@yahoo.com

chapter_22_fixtures_and_wait_decorator.asciidoc

@@ -127,7 +127,7 @@ When we want to recognise a client as being a logged-in and authenticated user,
 again, rather than asking the client to send their username and password
 with every single request,
 the server can actually just mark that client's session as authenticated,
-and associate it with a user ID in its database.((("Django framework", "sessions")))
+and associate it with a user ID in its database.((("user IDs (UIDs)", "for Django sessions", secondary-sortas="Django")))((("Django framework", "sessions")))
 
 A Django session is a dictionary-like data structure,
 and the user ID is stored under the key given by `django.contrib.auth.SESSION_KEY`.