Shrinking log files on AG to manage VLF's

some of our databases have excessive VLF's in their log files and I plan to shrink and then grow them to an appropriate size. I'm going to use the Tiger Team script https://github.com/microsoft/tigertoolbox/tree/master/Fixing-VLFs All the databases are in Availability Groups, so I won't be changing the recovery model, but an answer by Ted here https://learn.microsoft.com/en-us/answers/questions/632536/shrink-a-database-log-file-which-is-synchronized-( says "You MUST MAKE sure that you don't use the truncate the log with truncate only. That will kill the log info that is needed to keep the database synchronized to the secondary." Is that right? Is using TruncateOnly problematic on AGs? It doesn't say anything about that in MS docs about shrinkfile.