Re: non-parallelism - looking for the ok to let it go...

[Paresh Naik <paresh -dot- n -dot- naik -at- gmail -dot- com>]

If attempting parallelism results in many awkward constructions, I would not
aim for perfect, 100% parallel constructions. Here’s what "Read Me First"
says:



However, do not write a heading using a gerund merely for the purpose of
achieving

parallelism, as shown in the following example. Note that the heading
“Understanding

Management Operations” erroneously implies that the user must understand the
operations before attempting to perform them.

*Incorrect:*

Understanding Management Operations

Creating a Managed Object

Selecting a Managed Object

*Correct:*

Management Operations

Creating a Managed Object

Selecting a Managed Object


Thanks,
Paresh
On Wed, Jul 27, 2011 at 3:40 AM, Monique Semp <monique -dot- semp -at- earthlink -dot- net>wrote:

> Hello writers (on two lists; sorry to clutter up you multi-list
> subscribers’ inboxes),
>
> So I’ve got a bundle of PPT “vertical block list” smart art diagrams
> (really just nice graphics around two-level bullet lists) that the client
> really likes and wants me to include in a Best Practices doc. There’s all
> sorts of wonderful info in those “diagrams” and I’ve had no problem writing
> lots of good context and details.
>
> The only issue is... there’s just no good way to force parallelism in the
> diagrams’ text lists. I can get the “level 1” points to parallel without
> much awkwardness, but then the “level 2” points are all over the place:
> present-tense verbs, imperative verbs, nouns, phrases, you name it – it’s
> all in there.
>
> I’m inclined to just let it go because the content *is* what’s important
> (and perhaps I’ll have time or inspiration while they’re performing their
> reviews to actually make real progress on the parallel dream), and I’m
> looking for an ok from the tech writing community :-).
>
> Aside from a rap on the knuckles (or no award if I were to enter this doc
> in the STC competition – but please don’t let this thread devolve into a
> heated STC discussion!), what can happen after all, right?
>
> Let the machinations begin,
> -Monique
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Create and publish documentation through multiple channels with
> Doc-To-Help.
> Choose your authoring formats and get any output you may need. Try
> Doc-To-Help, now with MS SharePoint integration, free for 30-days.
> http://www.doctohelp.com
>
> ---
> You are currently subscribed to TECHWR-L as paresh -dot- n -dot- naik -at- gmail -dot- com -dot- 
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> http://lists.techwr-l.com/mailman/options/techwr-l/paresh.n.naik%40gmail.com
>
>
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
> http://www.techwr-l.com/ for more resources and info.
>
> Please move off-topic discussions to the Chat list, at:
> http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days.
http://www.doctohelp.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info.

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat