# What to Turn in

**Rule #1**: Internet Explorer is never the right choice. 

Make sure that your very own website is open in Google Chrome and hit Ctrl + P

![If you don't see this...are you sure you are in Google Chrome?](https://2507214486-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LpUPSf3tCxHePJxNjfg%2F-LxvW8vlJ5R5QpflmsYF%2F-LxvXDIvovtWiz5a8A0-%2FCapture.JPG?alt=media\&token=9435586c-d08b-4531-9e52-bb03e2b9da71)

Change the destination to save as `PDF` and save this file (not to your desktop folder) to your Software Development Folder as `lastname_firstpage`

Now go back to your website (not in notepad) at hit `Ctrl + U` you should now see your code with some handy dandy line numbers. Repeat the print to PDF process but this file name should be `lastname_firstpagecode`

Now go to the online class (remember this is the book), find the first web page assignment and turn in the files as listed...once again you need to read and figure out what gets turned in where. 


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://computational-thinking-in-room11.gitbook.io/room-112-dhs/html-1/my-1st-webpage/what-to-turn-in.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.