The Title field will also keep that name in power automate, as the Dataverse that drives these things uses that field as kind of default identifier.
You can do a few things - it's hard to see your image as it's small and doesn't magnify.
I recommend you make sure you are renaming your actions so 'Get Item from list 1', and 'Get Item from list 2' are clear. This lets you clearly see what you are grabbing from the dynamic content. You should see it in grouped categories to choose from in your available dynamic content: 'Get Item from list 1' list items and then another section 'Get Item from list 2' list items respectively. If you don't see your 'Get Item from list 2' section in your dynamic content options, your logic probably needs to be updated, as it can't use an item it doesn't have (you can use variables to get and store a bit of dynamic content, but that introduces another layer of logic into the mix).
This can get kind of messy, as you need to make sure your logic is clear. If 1 flow run creates 1 document, from 1 record in 1 list and 1 record in another list, that flow logic will be simpler and look very different from a 1 flow run creates many documents from 1 record in 1 list and 1 record in another list or 1 flow run creates 1 document from many record in 1 list and 1 or many records in another list , etc.
You have to be very clear and intentional with your logic and the subsequent nested loop ('for each') logic. If you 'get item' with a 'for each' loop, you can't use that same "get item' info anywhere outside of that 'for each' loop (unless you use a variable or compose statement to get and STORE that info to use farther on in the flow).
You can get item(s) from yours lists and use a variable or compose statement to get and STORE that info to use farther on in the flow BUT that starts to get even more complicated in with logic. You really have to understand the logic of loops and exactly what your loop(s) are doing, and when they are doing it, with what info. What, where, and when you get content, and what, where and when you will then use that content needs to be precise.
I recommend using compose statements to test each section of your logic to see if it's working the way you think it should - create a flow with some part (or all if you like) of your logic, using compose statements at each step with the dynamic content output of that step. Run the flow & check the compose statements to see what it's generating where and when. If it's not what you are looking for, rearrange your logic a little, and try again. Keep checking until you get the desired output! It takes patience, but I find it helps when I have tricky logic to work with.