From dc47dfdc33d9c499bded843c9904e99c1453f93f Mon Sep 17 00:00:00 2001 From: Rebecca Dimock Date: Tue, 12 Nov 2024 17:19:06 -0600 Subject: [PATCH] run tox --- docs/guides/serverless-hamsim-template.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/serverless-hamsim-template.ipynb b/docs/guides/serverless-hamsim-template.ipynb index 23a108aa6be..fba01d5e491 100644 --- a/docs/guides/serverless-hamsim-template.ipynb +++ b/docs/guides/serverless-hamsim-template.ipynb @@ -55,7 +55,7 @@ "tags": [] }, "source": [ - "By now you've seen a basic example of how to get started writing, uploading, and running a program with Qiskit Serverless. If you haven't, start with [What is Qiskit Serverless?](/guides/serverless) for some background information first. \n", + "By now you've seen a basic example of how to get started writing, uploading, and running a program with Qiskit Serverless. If you haven't, start with [What is Qiskit Serverless?](/guides/serverless) for some background information first.\n", "\n", "The workloads you are building for your own use cases are likely not as simple as the examples previously shown. For example, you might need to carefully consider what domain-level inputs and outputs are relevant for your application, how to make sure your program can be reusable across a range of those inputs, and what kind of information you need returned during the execution of the job so you can better evaluate the progress of your workload. You might even want to incorporate a \"dry run\" mode that lets you test the impact of a set of particular inputs before sending the resulting circuits to hardware.\n", "\n",