docs: fix the socket example, procedure structure, terminology, front matter and links

[rweesner]

Fixes a socket-number example that contradicted the configuration reference, restructures
the machine-creation procedure, brings terminology and front matter in line with the
documentation standards, and adds the release-notes legend.

6 files, one commit. No product behavior is described here that the pages did not already
state.

Installation

• Socket number example. The machine-creation procedure gave 3100 as the example.
  The configuration page says the Java Agent's SocketNumberToSAM defaults to 17100
  and that the machine's socket number must match it — so following the example produced
  a machine the agent would not talk to. The step now says the value must match
  SocketNumberToSAM, which defaults to 17100.
• Procedure structure. The three parts of the procedure were bold "Step 1 / Step 2 /
  Step 3" labels with no lead-in. They are now headings, each with a "To …, complete the
  following steps:" lead-in.
• Standards. Optional steps start with "(Optional)"; menu paths bold each label rather
  than the whole path; installer wizard pages are "steps" and dialogs are "windows".

Configuration file

• The allowed-address example used a routable address; now 192.0.2.10, from a range
  reserved for documentation.
• Two references to Enterprise Manager "screens" are reworded.

Landing page

Added title, description and tags front matter in the same shape as the other agent
sites. The link menu is unchanged.

Release notes

Added the marker legend used by the core OpCon release notes. The markers are unchanged —
they match the page as the release authors left it.

Links

The two relative links without the .md extension now use it.

Follow-ups for an owner

These need someone who knows the product; the pages cannot settle them.

1. JORS socket default. The configuration table gives JORSSocket a default of
   18110; the example Agent.config on the same page sets 17110.
2. Section name. The table calls the section [Application Connector Settings]; the
   example calls it [Application Connection Settings]. If the agent matches section
   names, one of these is ignored. LibrariesDirectory also appears as Libraries in the
   table and libraries in the example.
3. Undocumented features. The release notes describe the JAR operation (16.1.0)
   and the Alternate JVM field, JVM Arguments and Environment Variables tabs,
   and JAVA_ENV_VARS / JAVA_JVM_ARGS (17.0.0), but no page documents them. The
   overview lists three operation types while the machine-messages page describes
   anything other than Class or Command as invalid.
4. "Right-select" in the Start communication step. The standards ban both "click" and
   "right-select" without giving an approved wording — open across all agent sites.
5. Requirements. .NET Framework 4.0 is out of support; the current requirement needs
   confirming.

Verification

• 0 front-matter gaps, 0 dead links, 0 broken anchors, 0 orphan pages.
• Every numbered procedure has a lead-in; all 17 relative links use .md.
• The site builds.

🤖 Generated with Claude Code