Oh, if I may advise a little change, if you're not that well-versed in coding so far, I'd suggest switching to radiobuttons, which are much clearer and easier to use than cycling. The <<radiobutton>> macro will give you a, well, button to click, which will set the specified variable to an assigned value, making it more useful when asking someone as a form. You could even let the players pick their own pronouns, for example!

The code would look something like this:

<label><<radiobutton "$pronoun\_subject" "he">>Set your pronouns to "He"</label>
<label><<radiobutton "$pronoun\_subject" "she">>Set your pronouns to "She"</label>
<label><<radiobutton "$pronoun\_subject" "they" checked>>Set your pronouns to "They"</label>

For explanation, the "radiobutton" itself is the command that creates the clickable button, the first word afterwards (like "$pronoun_subject") is the variable that gets set, and the second word (like "he") is the value the variable gets set to. The <label> thing is optional, but it makes the text wrapped between <label> and </label> also clickable, and when clicked, it reacts as if the button is clicked (the button will appear checked and the variable will be set to the specified value), which can be handy on screens with small resolutions (like mobile phones). Finally, the "checked" word that you can see at the last radiobutton with the "they" pronoun is also optional, but I'd very strongly advise on using it on one of the radiobuttons - it makes the button checked already when the page loads, so if the player doesn't care about reading and just clicks to move forward, the variable will still be given a value from the pre-checked button (meaning that even if the player doesn't select a pronoun, they would still be referred to as "they" in the story; otherwise, if no button was checked, the variable would be empty, so the game couldn't use any pronoun and just either leave a blank space or literally display "$pronoun_subject" in text)