Fix section refs.

Signed-off-by: chris <chris.sommers@keysight.com>

docs/v1/P4Runtime-Spec.mdk

@@ -3411,7 +3411,7 @@ property in the P4~16~ source code, with no `const` qualifier before
 `entries`, and at least one entry in that list.  In the P4Info, such
 tables have `has_initial_entries` flag equal to true, but
 `is_const_table` is false.  For tables declared with `const entries`,
-see Section [#sec-constant-tables].
+see Section on [Constant Tables](#sec-constant-tables).
 
 Every P4 table falls into one of three categories:
 
@@ -3446,8 +3446,8 @@ number of entries supported by the target for the table.
 
 The contents of preinitialized tables can be queried by the client
 through a `ReadRequest`.  The server fills in the same fields in the
-response as it does for constant tables, as described in Section
-[#sec-constant-tables], and with the same restrictions on table
+response as it does for constant tables, as described in Section on
+[Constant Tables](#sec-constant-tables), and with the same restrictions on table
 features supported.
 
 If the table requires a priority value for entries, the priorities of
@@ -6572,7 +6572,7 @@ properties, but we may include on in future versions of the API.
   * Add a `Type` field to the `MeterSpec` message allowing users to restrict the
     type of meters that can be used for a table and a new `eburst` field to the
     `MeterConfig` message for use with one of the new `MeterSpec` types. See
-    [Meter & DirectMeter section](#sec-meter-directmeter).
+    Section on [Meter & DirectMeter](#sec-meter-directmeter).
   * Defined new meter annotations `@two_rate_three_color`, `@single_rate_two_color`, `@single_rate_three_color`
   * Enable P4Runtime servers to provide per-color counter values when direct or
     indirect meter entries are read.
@@ -6587,7 +6587,7 @@ properties, but we may include on in future versions of the API.
   * Enable C++ Arena Allocation [@ArenaAllocation] by default in p4runtime.proto.
   * Clarified the meaning of set and unset scalar and message fields, see section [#sec-default-valued-fields].
   * Described Dataplane Volatile Objects, see section [sec-data-plane-volatile-objects]
-  * Clarified use of bytestrings in messages, see section [#sec-bytestrings]
+  * Clarified use of bytestrings in messages, see section on [Bytestrings](#sec-bytestrings)
 
 * Replication
   * Add a `metadata` field to the `MulticastGroupEntry` message.
@@ -6599,7 +6599,7 @@ properties, but we may include on in future versions of the API.
     type `int<W>`) apply to all minor revisions of P4Runtime v1, not just to
     P4Runtime v1.0.
   * Add `has_initial_entries` and `is_const` field fields to `Table` message to distinguish mutable and immutable initial table entries,
-    see section [#sec-constant-tables].
+    see Section on [Constant Tables](#sec-constant-tables).
 
 ### Changes in v1.3.0