Fix similar typos in docs

Signed-off-by: Arthit Suriyawongkul <[email protected]>

CHANGELOG.md

@@ -279,7 +279,7 @@
 - Option to disable ANSI terminal output with `--no-ansi` or `INSPECT_NO_ANSI`
 - Add chain of thought option to `multiple_choice()` and export `MultipleChoiceTemplate` enumeration
 - Allow Docker sandboxes configured with `x-default` to be referred to by their declared service name.
-- Improved error messages for Docier sandbox initialisation.
+- Improved error messages for Docker sandbox initialisation.
 - Improve legibility of Docker sandbox log entries (join rather than displaying as array)
 - Display user message immediately proceeding assistant message in model call transcripts.
 - Display images created by tool calls in the Viewer.

docs/eval-logs.qmd

@@ -90,7 +90,7 @@ If you do need to interact with the underlying JSON (e.g., when reading logs fro
 
 ## Image Logging
 
-By default, full base64 encoded copies of images are included in the log file. Image logging will not create performance problems when using `.eval` logs, however if you are using `.json` logs then large numbers of images could become unweildy (i.e. if your `.json` log file grows to 100mb or larger as a result).
+By default, full base64 encoded copies of images are included in the log file. Image logging will not create performance problems when using `.eval` logs, however if you are using `.json` logs then large numbers of images could become unwieldy (i.e. if your `.json` log file grows to 100mb or larger as a result).
 
 You can disable this using the `--no-log-images` flag. For example, here we enable the `.json` log format and disable image logging:
 

docs/extensions.qmd

@@ -324,7 +324,7 @@ The `_registry.py` file serves a place to import things that you wan't registere
 from .approvers import auto_approver
 ```
 
-You can then register your `auto_approver` Inspect extension (and anyting else imported into `_registry.py`) like this in `pyproject.toml`:
+You can then register your `auto_approver` Inspect extension (and anything else imported into `_registry.py`) like this in `pyproject.toml`:
 
 ::: {.panel-tabset group="entry-points"}
 ## Setuptools

docs/tools.qmd

@@ -20,7 +20,7 @@ Inspect has several built-in tools, including:
 
 -   [Bash and Python](#sec-bash-and-python) for executing arbitrary shell and Python code.
 
--   [Web Browser](#sec-web-browser), which provides the model with a headless Chromimum web browser that supports navigation, history, and mouse/keyboard interactions.
+-   [Web Browser](#sec-web-browser), which provides the model with a headless Chromium web browser that supports navigation, history, and mouse/keyboard interactions.
 
 -   [Web Search](#sec-web-search), which uses the Google Search API to execute and summarise web searches.
 
@@ -104,7 +104,7 @@ If you do not explicitly handle errors, then Inspect provides some default error
 
 -   `ToolError` — Special error thrown by tools to indicate they'd like to report an error to the model.
 
-These are all errors that are *expected* (in fact the `SandboxEnvironemnt` interface documents them as such) and possibly recoverable by the model (try a different command, read a different file, etc.). Unexpected errors (e.g. a network error communicating with a remote service or container runtime) on the other hand are not automatically handled and result in the `Sample` failing with an error.
+These are all errors that are *expected* (in fact the `SandboxEnvironment` interface documents them as such) and possibly recoverable by the model (try a different command, read a different file, etc.). Unexpected errors (e.g. a network error communicating with a remote service or container runtime) on the other hand are not automatically handled and result in the `Sample` failing with an error.
 
 Many tools can simply rely on the default handling to provide reasonable behaviour around both expected and unexpected errors.
 
@@ -120,7 +120,7 @@ Another type of explicit handling is re-raising an error to bypass Inspect's def
 
 ``` python
 try:
-  result = await sandobox().exec(
+  result = await sandbox().exec(
     cmd=["decode", file], 
     timeout=timeout
   )
@@ -314,7 +314,7 @@ See the [Agents](#sec-agents) section for more details on how to build evaluatio
 
 ## Web Browser {#sec-web-browser}
 
-The web browser tools provids models with the ability to browse the web using a headless Chromium browser. Navigation, history, and mouse/keyboard interactions are all supported.
+The web browser tools provides models with the ability to browse the web using a headless Chromium browser. Navigation, history, and mouse/keyboard interactions are all supported.
 
 ### Configuration
 
@@ -408,7 +408,7 @@ RUN pip install playwright
 RUN playwright install
 RUN playwright install-deps 
 
-# Install other dependancies
+# Install other dependencies
 RUN pip install dm-env-rpc pillow bs4 lxml
 
 # Copy Python files alongside the Dockerfile

src/inspect_ai/util/_sandbox/service.py

@@ -131,7 +131,7 @@ async def handle_requests(self) -> None:
         list_requests = f"ls -1 {self._requests_dir}/*.json"
         result = await self._sandbox.exec(["bash", "-c", list_requests])
 
-        # process reqests
+        # process requests
         if result.success:
             request_files = result.stdout.strip().splitlines()
             if request_files: