Jane wrote: "No, it is not..."
Here we get into the age-old Tech Writer's refrain, "it depends".
...on what your management wants,
...on what your consultant advises.
So....it depends.
All very true, and I agree.
But if your reference to technical writer indicates experience in same, then you'd know the importance of how language is used.
I took issue with - and dispute - a blanket statement about what a quality manual 'is'. You didn't say a QM 'can' be such & such or 'one model of a QM is to (do such & such)...'. You said: it's this. Not so.
A wall can be built of bricks.
But to state definitively that 'a quality manual is a restatement of the Standard' is about as 'true' as saying that "A wall is built from bricks."
While ISO 9001 is definite about certain things that must be
included in the QM (or referenced by it), it very definitely does
not prescriptively define what a QM is or shall be. And if 'ISO' hasn't... do you really want to go there?
Hence, a QM can be - and is! - many different things in many different formats according to factors which include the needs of the company, the preference or familiarity of the person creating it, and yes, their skill (or lack of) in technical writing.
It's one of the things I feel strongly about (had you guessed?)

You see, I've seen so many sheer bloody awful things purporting to be 'quality' manuals, and I know very, very well that a/they don't have to be awful and b/they don't have to restate the Standard. You can choose to do it that way, but there are other options. I also feel extremely strongly that your QM should make sense to the people who use it (never be written for an Auditor) and should add some value to the organisation. But enough about my strong feelings.
As hjilling said, sounds like you're off to a good start. But do focus on keeping it as simple as possible & useful.