"Now" is not needed.

"If not, the distribution file format might require overriding one or more of"

End the sentence after DISTFILES:

..., or <varname>DISTFILES</varname>.</para>

and delete the next two lines.

Break this compound sentence into two sentences:

"default. This is rarely necessary.</para>"

s/Package/The package/

s/tree, check/tree. Make sure/

This whole paragraph is full of asides.

<para><varname>PORTREVISION</varname> is a monotonically increasing value which is reset to 0 with every increase of <varname>PORTVERSION</varname>, typically every time there is a new official vendor release.
If <varname>PORTREVISION</varname> is non-zero, the value is appended to the package name.
Changes to <varname>PORTREVISION</varname> are used by automated tools like &man.pkg-version.8; to determine that a new package is available.</para>

<para>Changes in the packing list or the install-time behavior of the package. For example, a change to a script which generates initial data for the package, like &man.ssh.1; host keys.</para>

Break compound sentence:

s/differences, that is,/differences. For example,/

This paragraph would also benefit from breaking out the asides into separate sentences.

Break sentences up:

s/bumped because/bumped. Without increasing <varname>PORTREVISION</varname>, the/

Another paragraph with asides. Not your fault, but fix if you can.

End the first sentence after "grief". After that...

If the description above was not clear enough, please consult the &a.ports;.</para>

s/change/changes/

This sentence is long and confusing. Break into multiple sentences, and if you show the wrong way, show it first:

For example, do not do ... . The correct way is ... .

"think about it" seems a little weak, but I can't think of a better version.

Break out aside:

"states the compiled-in defaults. The hyphen is optional.

s/follows/follow/

s/there are/there is/

s/to serial/to the serial/

Remove the emdash and split the sentence:

s/libraries&mdash; they/libraries. They/

"should not" would be okay here, as a recommendation. The emphasis should be on "not" either way.

Break compound sentence, with the "for example" in the second sentence.

Break into two sentences instead of the emdash.

use <acronym> tags on FTP and HTTP.

s/get/be/

Break sentence at the semicolon.

Insert "the" before CATEGORIES.

Avoid passive voice.

s/will be/is/

"... be deleted and the port placed only in the other subdirectory.</para>

s/clearly cut/clearly defined/

send-pr is gone. "port submission in the bug database" (and a link)?

Break sentence at semicolon.

Remove "from".

s/be added/are included/

"The older expanded format can still be used, although there"

"really is no reason to do so:</para>

I don't understand what this sentence is saying.

It does need the "the" before DISTFILES.

<para>When none of the <varname>DISTFILES</varname> need to be uncompressed, set <varname>EXTRACT_ONLY</varname> to the empty string.</para>

<acronym> tags for FTP and HTTP.

Break sentence at the emdash.

Nice!

Remove "section".

s/the port/the new port's/

Extra "with".

s/these/the/

s/for example,/like/

Should probably have <acronym> tags around GPL.

Good catch!

s/has to/have to/

s/in/is/

(Not yours, I know.)

Nice!

s/is/their/

Break at semicolon.

Remove "this"

Replace &mdash; with comma.

"using variables cleverly, only a very short"

s/Runnig/Running/

<acronym> tags on GNU.

s/can/values can/

"The form shown above is discouraged. The preferred method is using a configure knob to really enable and disable the feature to match the option:"

(I suggest only showing the preferred way and not mentioning the other way.)

s/in to/into/

s/all/all,/

If the port cannot be built when other specific ports are already

s/use/Use/

"Enumerate" is nice, but probably more difficult for translators than "Use package names, not port names or origins."

Actually, that is not clear to me. Package names being a full filename? And above, it says "list the other *port* names". An example would help, along with consistent statements.

"Must" does not seem right. What if DEBUG is set?

s/do/Do/, but that sentence is vague. How do I know when I need to strip binaries manually?

I guess I don't understand what this part about the name is explaining. Why should the first letter be lower case? The nonspecific "think about it" does not tell me the goal. Am I supposed to think about converting the whole thing to lower case? And then... is just thinking about it enough?

It's been considered. One difficulty is the semicolons that are part of entities. Also, semicolons are only one of the signs of compound sentences. There are colons and parens and commas and lots of others.

Well, hum, the idea is that you should really not have a package name that starts with a capital letter. Then, you should refrain from having capital letter later in the name. So, well, I don't really know what you're supposed to be thinking about :-)

design *of* the new

The "if ever" is redundant but can be kept if you feel it is needed. (It's a subset of "rarely".)

"for example," is not needed in this line.

Double "use".

"to use" is not needed.

I still don't see *why* the first letter should not be upper case. We have ports that actually break that rule, like ImageMagick. Is it for ASCII sorting?

s/port/port's/

s/time/times/

Yes, I'll keep it, people should almost never need to do that :-)

Ok, yes, I've discussed it with my fellow portmgr, and it is not needed any more, it seems. Rewording it. (Well, more like axing it.)