> For the complete documentation index, see [llms.txt](https://docs.wcproducts.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcproducts.com/welcome/shop-accessories/super-pit/misc/legacy-products/legacy-single-upper-kit/steps-5-8.md).
# Steps 5-8
## Step 5
Take the shims along with the assembly from Step 4 and lay them in the case. Line up the shims with the assembly, make sure everything is square and straight. Use tape if needed to hold the shims into position while marking out hole positions. Take a sharpie and mark all the holes to drill to 0.201" into the wood.
{% hint style="warning" %}
Do not drill out the holes in this step.
{% endhint %}
{% tabs %}
{% tab title="Layout" %}
{% endtab %}
{% tab title="Drilling Locations" %}
The reference picture below only shows half of the drilling locations that need to be marked.
{% hint style="info" %}
Ensure that all rails that are in contact with the case get the holes marked.
{% endhint %}
{% endtab %}
{% endtabs %}
## Step 6
Remove the shims and assembly from the case and drill holes. If any of the holes line up with any metal or handles we recommend not drilling those holes.
## Step 7
Take shims and assembly from Step 4 and set them back in the case in the same layout that was used to mark the drilling locations in Step 5. Use #10-32 x 1" L bolts with lock nuts to bolt everything down. We recommend not tightening everything fully yet.
## Step 8
Install the rest of the bin rails and then tighten everything down.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.wcproducts.com/welcome/shop-accessories/super-pit/misc/legacy-products/legacy-single-upper-kit/steps-5-8.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
