1 files changed, 4 insertions, 4 deletions
diff --git a/90.md b/90.md
index 241eb38..5a15ebb 100644
--- a/90.md
+++ b/90.md
@@ -162,8 +162,8 @@ Service providers can give feedback about a job back to the customer.
 ```
 * `content`: Either empty or a job-result (e.g. for partial-result samples)
-* `amount` tag: as defined in the [Job Result](#job-result) section.
+* `amount` tag: as defined in the [Job Result](#job-result-kind6000-6999) section.
-* `status` tag: Service Providers SHOULD indicate what this feedback status refers to. [Appendix 1](#appendix-1-job-feedback-status) defines status. Extra human-readable information can be added as an extra argument.
+* `status` tag: Service Providers SHOULD indicate what this feedback status refers to. [Job Feedback Status](#job-feedback-status) defines status. Extra human-readable information can be added as an extra argument.
 * NOTE: If the input params requires input to be encrypted, then `content` field will have encrypted payload with `p` tag as key.
@@ -177,7 +177,7 @@ Service providers can give feedback about a job back to the customer.
 | `success`          | Service Provider successfully processed the job.                                                            |
 | `partial`          | Service Provider partially processed the job. The `.content` might include a sample of the partial results. |
-Any job feedback event MIGHT include results in the `.content` field, as described in the [Job Result](#job-result) section. This is useful for service providers to provide a sample of the results that have been processed so far.
+Any job feedback event MIGHT include results in the `.content` field, as described in the [Job Result](#job-result-kind6000-6999) section. This is useful for service providers to provide a sample of the results that have been processed so far.
 # Protocol Flow
@@ -199,7 +199,7 @@ Some service providers might choose to submit a `payment-required` as the first
 It's not up to this NIP to define how individual vending machines should choose to run their business.
 # Cancellation
-A job request might be cancelled by publishing a `kind:5` delete request event tagging the job request event.
+A job request might be canceled by publishing a `kind:5` delete request event tagging the job request event.
 # Appendix 1: Job chaining
 A Customer MAY request multiple jobs to be processed as a chain, where the output of a job is the input of another job. (e.g. podcast transcription -> summarization of the transcription). This is done by specifying as input an event id of a different job with the `job` type.

diff --git a/90.md b/90.md index 241eb38..5a15ebb 100644 --- a/90.md +++ b/90.md
@@ -162,8 +162,8 @@ Service providers can give feedback about a job back to the customer.
162	```	162	```
163		163
164	* `content`: Either empty or a job-result (e.g. for partial-result samples)	164	* `content`: Either empty or a job-result (e.g. for partial-result samples)
165	* `amount` tag: as defined in the [Job Result](#job-result) section.	165	* `amount` tag: as defined in the [Job Result](#job-result-kind6000-6999) section.
166	* `status` tag: Service Providers SHOULD indicate what this feedback status refers to. [Appendix 1](#appendix-1-job-feedback-status) defines status. Extra human-readable information can be added as an extra argument.	166	* `status` tag: Service Providers SHOULD indicate what this feedback status refers to. [Job Feedback Status](#job-feedback-status) defines status. Extra human-readable information can be added as an extra argument.
167		167
168	* NOTE: If the input params requires input to be encrypted, then `content` field will have encrypted payload with `p` tag as key.	168	* NOTE: If the input params requires input to be encrypted, then `content` field will have encrypted payload with `p` tag as key.
169		169
@@ -177,7 +177,7 @@ Service providers can give feedback about a job back to the customer.
177	\| `success` \| Service Provider successfully processed the job. \|	177	\| `success` \| Service Provider successfully processed the job. \|
178	\| `partial` \| Service Provider partially processed the job. The `.content` might include a sample of the partial results. \|	178	\| `partial` \| Service Provider partially processed the job. The `.content` might include a sample of the partial results. \|
179		179
180	Any job feedback event MIGHT include results in the `.content` field, as described in the [Job Result](#job-result) section. This is useful for service providers to provide a sample of the results that have been processed so far.	180	Any job feedback event MIGHT include results in the `.content` field, as described in the [Job Result](#job-result-kind6000-6999) section. This is useful for service providers to provide a sample of the results that have been processed so far.
181		181
182		182
183	# Protocol Flow	183	# Protocol Flow
@@ -199,7 +199,7 @@ Some service providers might choose to submit a `payment-required` as the first
199	It's not up to this NIP to define how individual vending machines should choose to run their business.	199	It's not up to this NIP to define how individual vending machines should choose to run their business.
200		200
201	# Cancellation	201	# Cancellation
202	A job request might be cancelled by publishing a `kind:5` delete request event tagging the job request event.	202	A job request might be canceled by publishing a `kind:5` delete request event tagging the job request event.
203		203
204	# Appendix 1: Job chaining	204	# Appendix 1: Job chaining
205	A Customer MAY request multiple jobs to be processed as a chain, where the output of a job is the input of another job. (e.g. podcast transcription -> summarization of the transcription). This is done by specifying as input an event id of a different job with the `job` type.	205	A Customer MAY request multiple jobs to be processed as a chain, where the output of a job is the input of another job. (e.g. podcast transcription -> summarization of the transcription). This is done by specifying as input an event id of a different job with the `job` type.