When performing the Elastic indexing of headers, doesn't like headers with dot notation

[ddibble-rip]

I'm getting some weird errors from dactyl when trying to build the payment object schema. This is only when trying to publish the doc to the clients site using Jenkins.

I'm thinking dactyl is seeing two heading that start with the same object name, and it's not liking it. latest error is this:

Previous error was this (different section of the page:

01:21:54 Uploading to ES: PUT https://HOSTNAME/ripplenet_payment_object-v1.1.4-supporting_info_schema/article/payment-object-additional-info.rmtinf.html
01:21:54 ES upload failed with error: '{"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"Could not dynamically add mapping for field [Amt.DscntApldAmt.Tp.Cd Known Values]. Existing mapping for [subheadings.Amt] must be of type object but found [text]."}],"type":"mapper_parsing_exception","reason":"Could not dynamically add mapping for field [Amt.DscntApldAmt.Tp.Cd Known Values]. Existing mapping for [subheadings.Amt] must be of type object but found [text]."},"status":400}'
01:21:54 Build step 'Execute shell' marked build as failure
01:21:54 Stopping Docker container after build completion
01:21:54 $ ssh-agent -k
01:21:54 unset SSH_AUTH_SOCK;
01:21:54 unset SSH_AGENT_PID;
01:21:54 echo Agent pid 19008 killed;
01:21:54 [ssh-agent] Stopped.

In each of these cases, dactyl hit a header that had previously started with the same word.

Examples of failed builds are in Jenkins project: clients-doc-push, builds: 846-850 Happens with documents/network-rulebook/payment-object-addl-info/properties/rmtinf.md

There's a barf when dactyl hits the header

##### `LineDtls.Id.Tp.CdOrPrtry` Known Values

AS there is already a header

#### `LineDtls`

in the file that has been indexed