When your documentation is under version control, it is typically not an unreasonable request for the person doing the documentation and/or managing the documentation to ensure that it is properly checked-in -- be they a technical developer or otherwise.
In my experience, a sticky note on the desktop (virtual or not) with the few git/svn/etc commands, or the interaction path with one's GUI client of choice, on the desktop of an otherwise non-technical person has worked just fine when the responsibility and expectation is made clear that documentation checkin is part of the job.
You may not be able to do this in your specific situation, but if we took out the "my husband is the CTO and does some things for me" (note: this was in the original question) and tackled the issue in general then some options include:
- The person learns how to use version control and it is made part of their workflow, as noted above (and again, not unreasonable, although the project manager or technical lead or whomever keeps an eye on things might have to keep an extra eye on things the first few times).
- The person doesn't learn how to use version control and the workflow step for documentation check in falls to someone on the development team or perhaps the release manager (depending on when the checkin happens).
- Something else probably more convoluted and inefficient than keeping a sticky note on the desktop about how to checkin a document...