<para>This section explains the most common things to consider when creating a port.</para>

s/mostly/mostly be/

This one actually needs "should". It's a recommendation on when to create directories.

s/has to be/is/

s/upstream/the upstream/

setting <varname>USE_LDCONFIG</varname> to a list of

s/example/example,/

<filename>PREFIX/lib/bar</filename>,

s/has to/must/

s/in to/into/

s/cannot not be/cannot be/

<varname>RESTRICTED</varname>, since the latter variable

s/else/other/

s/Same/The same/

s/if port/if the port/

s/^/an /

Break sentence at NLS. Also use <acronym> tags on NLS.

s/on//

In high complexity cases, more advanced techniques

may be needed, such as

s/like/as/

I think this is one where "should" is correct.

s/so that/for/

When set, add the selected JDK port to the build dependencies.

When set, add the selected JDK port to the run dependencies.

When set, add the selected JDK port to the extract dependencies.

Should this have the single quotes?

"forecited" is a word, but a rare one. "previously listed variables" is better.

s/is/are/

s/use/uses/

s/the//

s/must/is/

mygroup</literal> if the port needs different values. This

allows the user to override them easily.</para>

s/the/a/

s/must make sure to/must/

Do not redefine these variables in the port.

s/entries using/entries for/

s/default define/default, define/

s/version define/version, define/

This is a recommendation:

earlier, all ports scripts should use</para>

s/have/have a/

s/If so that/If so, that/

"Should" is a recommendation here, and correct.

I don't think so, if it has those files, they must be listed in the plist, and be installed in the directory below. Maybe i should have used "must" and not "have to" ?

Should I add <acronym> around JDK too ? should I do this everywhere ?

nope.

Yes, "must" is more definite than "have to".

Yes. Anything that is an acronym should have <acronym> tags.