> 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/assembly-instructions/table-kit/steps-5-11.md).
# Steps 5-11
## Step 5
Place the assembled Table Legs into the case in the desired location, ensuring it sits square and aligned. Using a sharpie, mark all required hole locations that will need to be drilled out in the next step.
{% hint style="warning" %}
Do not drill out the holes in this step.
{% endhint %}
## Step 6
Remove the assembly from the case and drill the marked out holes. If any of the holes line up with any metal or handles we recommend not drilling those holes.
## Step 7
Take the Table Legs and set them back in the case in the same location that was used to mark the drilling locations in Step 5. Use #10-32 x 2-3/4" L bolts and #10-32 Nuts to bolt everything down.
## Step 8
Place your workspace top into position and mark all required hole locations that will need to be drilled out in the next step.
## Step 9
Remove the assembly from the case and drill the marked out holes. If any of the holes line up with any metal or handles we recommend not drilling those holes.
## Step 10
Place your workspace top into position and bolt it down using #10-32 bolts and nuts as shown below.
## Step 11
Install the Table Support Bracket using the #10 x 1/2"L Particleboard Screws.
---
# 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/assembly-instructions/table-kit/steps-5-11.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.
