In your screenshot, the text "FEATURED EXPERT" appears to be Helvetica, not Futura PT. Different typefaces can have different apparent sizes for the same numeric point size, so you should check that first.
Typekit sync fonts are essentially identical to any traditional desktop font you might purchase -- so assuming they are getting installed and showing up in your font menu, any other problems with text appearance and handling would be related to the application or OS.
Having said that, I would try quitting Pages, unsyncing/resyncing the fonts from Typekit, and restarting Pages. Adobe applications are very good at dynamically updating fonts as they are installed, but that's not always the case with other desktop applications. (Often, but not always.)
You'll find some more, general sync troubleshooting advice here: TYPEKIT | Troubleshooting Guide: syncing desktop f...
Thanks, Christopher. After I posted my original question, I did come to realize that it was Helvetica not Future PT showing. Here’s what happened, and here’s why I still need some guidance…
The document dropped Future PT because when my wifi signal dropped, the Creative Cloud app displayed this error symbol (see graphic) in my menu bar.
At that point, my computer could no longer access my TypeKit fonts and the document reverted to the system's Helvetica default.
This was not an isolated incident.
If I turn wifi off manually, there is no issue and CC continues to operate in the background as it should, with TypeKit fonts still available.
However, if the wifi drops out on its own, I get the above error symbol and I then lose access to my TypeKit fonts. Very rarely, the CC app will self-correct when the signal is restored. More often than not, I must quit the CC app and relaunch it in order to get things back to normal.
This doesn’t strike me as normal behavior Have you ever encountered anything like it? Do you know of a fix that will allow the CC app to self-correct when the wifi signal is restored?Any assistance will be appreciated!
P.S. TypeKit troubleshooting doesn’t address this particular issue.
Thanks for the details. Obviously that sync behavior is not normal, nor expected. I'll forward it to some folks here for a look and see if there's any immediate remedy.