Hi Shana,
It is a lowercase 'L' (l). Here are a couple more screenshots to show you what is happening.
The labelled point layer of addresses is the layer I created the Geocoder from. As you can see "1625 Jaywin Circle" is a valid address as it exists in the point layer, but when I type it in the Locate toolbar, it does not get a match with my custom Geocoder.
But....when I type the address in as "1625 Jaywin Cl" it does get a match. A few times a year I geocode addresses that get typed into a database, so I need a geocoder that gets as many matches as possible to avoid too much manual coding of points. I just don't understand how the coder is not matching addresses like this, that seem to be typed in properly.
Here are some of the settings from the Geocoder. From the fields I use I should be getting a match regardless of using 'Circle' or 'Cl', since I have both those fields defined.
And here are the attributes for this particular address, from the point file the Geocoder references:
I'm a bit confused as to why it doesn't work. This Geocoder is definitely working better than anything I ever tried in ArcMap, but still in ArcPro I would like it to work even better still.
Thanks. If you have any other ideas, please let me know.