I am not a DB pro, so please excuse me, but isn't MyISAM kind of the "old school" tech and not recommended now-a-days (especially for different types of snapshot backups).

I use amazon RDS for my sql server and its telling me:

This DB Instance also contains MyISAM tables that have not been migrated to InnoDB. These tables can impact your ability to perform point-in-time restores. Consider converting these tables to InnoDB. Please refer to http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.MySQL.CommonDBATasks.html#MySQL.CommonDBATasks.Tables

Any reason I can't force this table over to innodb?

well, fullText searching is still not fully adopted in many mysql installs sadly. But in the next year, I likely will be switching this over. The only reason for the one MyISAM table is for search indexing. You technically can feel free to change that. Please report back when you work the InnoDB string in the updates file so that I can add a commented note regarding this for others that want to change that over. The main concern again, is the fullText searching of title and content.