I’m not 100 percent, but my fractured foot is well on the mend. I now have my first two runs since early July under my belt and happily report both went well.

I logged the first Aug. 31 — a little over a mile in a little over 10 minutes. The second I ran today, about two and a half miles at a 8:42 average pace. I felt a little tinge of soreness in the injured foot after the first run. After today’s run, I’m happy to report no soreness (so far) in that foot.

What I did notice today, on a fairly hilly run: tightness in my chest. Two months off from running apparently made my heart soft and pasty, and my lungs stingy. I labored through the hills and found myself around the second mile looking for the finish line.

That’s okay, though. It’ll come back, as sure as the foot will heal.

Also, these runs served as a good test for Run Keeper, the new-to-me log app. It works with the GPS in my new iPhone, and seems to track pretty well. The distance it measured for the first run matched Gmaps Pedometer (what I had been using to calculate distance) almost exactly. For the second, longer run, it had a one-twentieth of a mile difference from GPed. While that difference could add up over a much longer run, it’s close enough for me. Plus, I can live with a little difference in exchange for not having to plot the maps myself when I get home. Run Keeper also keeps stats of pace, elevation, speed, calories burned and split times.

I have used the app Pace for almost two years. It records distance, duration and average pace, and calculates calories. I’ll likely still use it, doing double entry, since Run Keeper apparently doesn’t allow for tracking miles logged on a pair of shoes (like the 600-plus-mile Nikes I really should retire — but they’re so comfortable!), or miles logged toward a goal (like marathon training).

Anyway, to summarize: I’m back. And it feels good.