> For the complete documentation index, see [llms.txt](https://docs.gxc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gxc.io/hw/5g/5g-network-mobile-kits/mng-00x-mobile-network-gateway/mng-00x-quick-start-guide/preface.md).

# Preface

This preface provides information on the documentation conventions used in this document and information to contact GXC Technical Support.

## Conventions

This section describes the documentation conventions used in this document.

### Note, Caution, and Warning Conventions

This document uses the following conventions for note, caution, and warning statements.

{% hint style="info" %}
**NOTE:** Presents important information or references to information not included in this document.
{% endhint %}

{% hint style="warning" %}
**CAUTION:** Presents information on situations that could result in damage to equipment or loss of data.
{% endhint %}

{% hint style="danger" %}
**WARNING:** Presents information on situations that could cause hazards including bodily injury.
{% endhint %}

## Contact GXC Technical Support

Contact GXC Technical Support at <support.onyx@gxc.io>.


---

# 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.gxc.io/hw/5g/5g-network-mobile-kits/mng-00x-mobile-network-gateway/mng-00x-quick-start-guide/preface.md?ask=<question>&goal=<user_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.