PBG Instruction Manual version 1.0

[adam]

Thanks Kick and Dave C; your suggested edits have been made.

[Dedman]

it's amazing how many times you can read a document and still find typo's or spooling errors

[chrissyinbkk]

Cannot comment on the manual itself as it is the likes of me that will rely on it... to me it's well done, but being a Pom had to find one tiny error... page 27, the pic of the jack.. we would spell it piece not peice....

[Sonic Mountain]

it's amazing how many times you can read a document and still find typo's or spooling errors

I have this all the time, you can't see the forest for the trees. The amount of things I've printed only to realise there is a typo or something I missed on screen is embarrassing. I wouldn't stress man, this is why you get others to check your work.

[Dedman]

a few years back I wrote a few fiction stories, I don't know how many times I've read them, loads of people read them on a couple of forums, I read one last week and found several typos LOL

[Marcel]

I felt rather honoured when I saw one of my build photos in the the wonderful work that Dedman has created. Actually I loved it, however I do see the faults in my own work and would prefer that another photo which I'll upload soon be used that has those faults removed.

I also think that where photos have come from build diaries that a comment beside the photo indicating the source would be nice. Something like "Bridge assembly of 'The Blaster' a SGJ-1 kit as done by Forum member XYZ." would be helpful to a/ limit the scope of applicability of some photos and b/ point builders back towards the build diaries by others which gives added weight to how useful they are.

[Rabbitz]

it's amazing how many times you can read a document and still find typo's or spooling errors

I guess that's why editors and proofreaders used to exist - it is essentially impossible to proofread your own work.

Your brain plays tricks - it knows exactly what you wanted to say, so that is what you see.

Proofreading was a trade with a three year apprenticeship.

[Dedman]

I guess that's why editors and proofreaders used to exist - it is essentially impossible to proofread your own work.

Your brain plays tricks - it knows exactly what you wanted to say, so that is what you see.

Proofreading was a trade with a three year apprenticeship.

yep, had a few friends who were proof ,readers, type setters, layout....all those trades are gone.

[Kick]

I also think that where photos have come from build diaries that a comment beside the photo indicating the source would be nice. Something like "Bridge assembly of 'The Blaster' a SGJ-1 kit as done by Forum member XYZ." would be helpful to a/ limit the scope of applicability of some photos and b/ point builders back towards the build diaries by others which gives added weight to how useful they are.

I totally agree with you Marcel. This way you actually can show what the possibilities are to build your own guitar. Great idea!

Just thinking of it: it could be a nice idea to make a photo collage of builds of GOTM from the past to end the document.

[adam]

I also think that where photos have come from build diaries that a comment beside the photo indicating the source would be nice. Something like "Bridge assembly of 'The Blaster' a SGJ-1 kit as done by Forum member XYZ." would be helpful to a/ limit the scope of applicability of some photos and b/ point builders back towards the build diaries by others which gives added weight to how useful they are.

Hi Marcel, absolutely, we should always credit photos where they are not taken by PBG. We'll get onto this for the next Draft.

Also, if anyone has photos that would fill these spots, example: (INSERT PIC SHOWING PROPERLY CLAMPED NECK), post them here or email to me, if you are happy for them to be used.