What is the difference between feature flags and feature toggles (if any)?
If you take it on an objective only point of view, there's no difference.

But feature toggles carry a heavy binary "on/off" for the whole application idea, whereas feature flags are a more relaxed term which can encompass ramp up testing more easily.

When you launch a ramp up testing and turn the new feature on for 10% of your traffic or user base and move up to 20% the next week and so on, the toggle term become counter productive.
Some people (managers/commercials/some client support people) may not really understand only a part of the clients get the new feature.

Ramp up can be defined as (quote from wikipedia on software testing technology):


  The usual sequence is to ramp up the load: to start with a few virtual
  users and increase the number over time to a predetermined maximum.
  The test result shows how the performance varies with the load, given
  as number of users vs. response time.


I like etsy's feature API (even is not maintained) as source for explanation, it's an easy to undertand framework which has a good readme around feature flags and their uses.

So the difference can be done in the usage of the terms to just help avoiding confusion on what happens on the application.