Merge pull request #483 from gmlueck/gmlueck/fix-info-messages

Fix longstanding informational messages

(cherry picked from commit 65011a8)

adoc/Makefile

@@ -136,7 +136,7 @@ ATTRIBOPTS   = --attribute revdate="$(SPECDATE)" \
   --attribute generated=$(GENERATED) \
   --attribute refprefix \
   $(VERSIONATTRIBS)
-ADOCMISCOPTS = --require asciidoctor-diagram --failure-level ERROR
+ADOCMISCOPTS = --require asciidoctor-diagram --failure-level INFO
 ADOCEXTS     = --require $(CURDIR)/config/spec-macros.rb \
 	--require $(CURDIR)/config/rouge_sycl.rb
 ADOCOPTS     = --doctype book $(ADOCMISCOPTS) $(ATTRIBOPTS) \

adoc/chapters/architecture.adoc

@@ -338,7 +338,7 @@ different queues.  When a <<command-group>> is submitted to a SYCL <<queue>>,
 the requirements of the kernel execution are captured.  The implementation can
 start executing a kernel as soon as its requirements have been satisfied.
 
-==== <<backend, SYCL backend>> resources managed by the SYCL application
+==== Backend resources managed by the SYCL application
 
 The SYCL runtime integrated with the SYCL application will manage
 the resources required by the <<backend-api>>

adoc/chapters/programming_interface.adoc

@@ -16359,7 +16359,7 @@ object passed to the <<async-handler>> is constructed by the <<sycl-runtime>>.
 
 
 [[subsubsec:exception.nohandler]]
-==== Behavior without an <<async-handler>>
+==== Behavior without an async handler
 
 If an asynchronous error occurs in a queue or context that has no user-supplied
 asynchronous error handler object <<async-handler>>, then an implementation-defined
@@ -16369,7 +16369,7 @@ a user-supplied <<async-handler>> would be, as defined in
 report all errors passed to it, when possible, and must then invoke
 [code]#std::terminate# or equivalent.
 
-==== Priorities of <<async-handler,async handlers>>
+==== Priorities of async handlers
 
 If the SYCL runtime can associate an <<async-error>> with a specific queue,
 then: