Kerby - Replacing code chunks within an .exe file is difficult, but you have 3 alternatives that I can think of...
1. Replace the entire .exe file with each update.
2. Keep the 'updatable' topics in a separate .js or text file outside of the .exe. An update would mean replacing the external file(s). The new information would display in the books the next time they're opened.
If you choose to update specific files on the user machine, you will need to keep track of what topics need updating, perhaps in an .ini file.
Your ebooks will go online to compare the existing topic version with the topics latest_version_number. If the latest_version number is larger than your existing_topic_version, you see the flashing update notice. Click the icon, and you pull the new data down from the server. The process then resets the existing_topic_version to the latest values.
3. Keep the updatable topics in a separate .js or text file on a web server. Users would have to be online to see the new content.
Perhaps this would be a more manageable solution. Include the external web file in the book, and when you edit that file on the server, the changes display in all the books when they go online.
There might be some other ways to accomplish this as well...
hope this helps -