> For the complete documentation index, see [llms.txt](https://docs.voltera.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voltera.io/docs/nova/learn-nova/general-maintenance.md).
# General Maintenance
Regular maintenance is essential to ensuring the longevity and reliability of your printer. This section outlines the recommended cleaning procedures for key components.
## General Maintenance Tips
It's important to do a quick cleanup and inspection before and after each use of NOVA, this will ensure the longevity of your machine.
* Keep your hands clean to avoid transferring ink/paste to areas around your machine.
* If you notice material transfer, clean it as soon as you can.
* Wet inks can generally be wiped off using a paper towel or tissue.
* Dried ink that has not been cured can be cleaned by applying a small amount of solvent (isopropyl alcohol) and rubbing with a paper towel.
* Protect your Dispenser and Probe by returning them to the foam insert in the drawer between uses.
### Cleaning Supplies
Here is a list of items that are good to keep on hand when using NOVA:
{% hint style="danger" %}
Do not use **Acetone** to clean NOVA.
{% endhint %}
---
# 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.voltera.io/docs/nova/learn-nova/general-maintenance.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.
