Install <package role="port">www/nspluginwrapper</package> from the port.

Not your fault, but this sentence is weird. It's not really that large a port. Is it large enough to make a difference to the user? Probably not, so I suggest ending the sentence after the package name.

If "which is a large port" is kept, a comma is needed before it.

Install <package role="port">ww/linux-c6-flashplugin11</package> from the port.

I think the command needs to be updated because browser_plugins is not present on new systems. But I have not tested it.

Either way, we should try to avoid line continuations.

As above, I'm not sure this is the way to do it any more. If it is, this step should be mentioned before creating the link.

Just mentioning the port name is enough:

Then install <package role="port">www/opera-linuxplugins</package>.

s/In order for/For/

s/the following/this/

This is handled by USES= webplugin:linux, normally automatically, from within a port:

xmj@mx12:~/repos/linux-ports-cleantree/www/linux-c6-flashplugin11$ make -V WEBPLUGIN_DIR
/usr/local/lib/browser_plugins/linux-c6-flashplugin

So, that step is actually superfluous. I'll remove it.

Again, superfluous. Nice catch!

Best to use <package role="port"> when explicitly referring to a port.

<package role="port">

<package role="port">

The "...port, as a package is not available" can be misread. Break into two sentences:

"... port. Licensing prevents making a package available."

This is a whitespace-only change and should be done separately.

The first actual change is on line 223, so I'm not sure what you mean.

If it was different it would be marked red/green here in Phabric

It was light green here, apparently a change in the underlying file. Never mind.