Something about a rocket having a user's manual makes me smile. Seems like a proper space agency name for this document would be much more space program sounding than just "user's manual". Even software programmers use terms like User Acceptance Training instead of just training. That one always makes me laugh too though, "You're going to learn to accept this software whether you like it or not."
I have never heard of User Acceptance Training. I have heard of User Acceptance Testing (UAT), which is about users testing the software, not training users on the software. The goal of UAT is to work with the user to verify that the software's functionality and usability are "acceptable". https://en.wikipedia.org/wiki/Acceptance_testing#User_accept...
It's always agrressive against the users. The users are the poor saps that have to accept whatever the devs have droped on them. The users have no say other than suggest it doesn't work, doesn't promote efficient workflows, whatever. It's then up to the devs to fix, but they feel like they've delivered according to specs so tough. The User will Accept Whatever from the all powerful dev team. How about User Acceptability Testing. At least it then makes it sound like the devs are going to give a damn about the users feedback.
Is this a Word Autosave, or someone aactually hitting save but couldn't be bothered to actually name the doc? It's clearly Word generating the filename.
I think it just goes to show that nobody likes creating documentation.
But it is Word that takes the firsr line of text to use as the filename, not the PDF writer. It could be a combo though. Word using the first line of text for the filename, then the PDF export appending the name of the app.
> This user’s guide is intended for pre-contract mission planning and for understanding SpaceX’s standard services. The user’s guide is not intended for detailed design use. Data for detailed design purposes will be exchanged directly between a SpaceX customer and a SpaceX mission manager.
