secilc/docs: use fenced code blocks for cil examples

Also fixes the occasional missing brackets as higlighted by my editor,
however the individual examples where not reviewed much closer.

secilc was chosen as language name because the compiler is named secilc
and outside of SELinux the name cil is less searchable and could lead to
confusion.

Signed-off-by: Jonathan Hettwer <j2468h@gmail.com>

secilc/docs/Makefile

@@ -51,7 +51,7 @@ $(TMPDIR)/%.md: %.md | $(TMPDIR)
 $(TMPDIR)/policy.cil: $(TESTDIR)/policy.cil
 	cp -f $< $@
 	@# add a title for the TOC to policy.cil. This is needed to play nicely with the PDF conversion.
-	$(SED) -i '1i Example Policy\n=========\n```' $@
+	$(SED) -i '1i Example Policy\n=========\n```secil' $@
 	echo '```' >> $@
 
 html: $(PANDOC_FILE_LIST) $(TMPDIR)/policy.cil

secilc/docs/cil_access_vector_rules.md

@@ -8,7 +8,9 @@ Specifies the access allowed between a source and target type. Note that access
 
 **Rule definition:**
 
+```secil
     (allow source_id target_id|self classpermissionset_id ...)
+```
 
 **Where:**
 
@@ -42,6 +44,7 @@ Specifies the access allowed between a source and target type. Note that access
 
 These examples show a selection of possible permutations of [`allow`](cil_access_vector_rules.md#allow) rules:
 
+```secil
     (class binder (impersonate call set_context_mgr transfer receive))
     (class property_service (set))
     (class zygote (specifyids specifyrlimits specifycapabilities specifyinvokewith specifyseinfo))
@@ -84,6 +87,7 @@ These examples show a selection of possible permutations of [`allow`](cil_access
         (allow type_5 type_5 (property_service (set)))
         (allow type_1 all_types (property_service (set)))
     )
+```
 
 auditallow
 ----------
@@ -92,7 +96,9 @@ Audit the access rights defined if there is a valid allow rule. Note: It does NO
 
 **Rule definition:**
 
+```secil
     (auditallow source_id target_id|self classpermissionset_id ...)
+```
 
 **Where:**
 
@@ -126,10 +132,11 @@ Audit the access rights defined if there is a valid allow rule. Note: It does NO
 
 This example will log an audit event whenever the corresponding [`allow`](cil_access_vector_rules.md#allow) rule grants access to the specified permissions:
 
+```secil
     (allow release_app.process secmark_demo.browser_packet (packet (send recv append bind)))
 
     (auditallow release_app.process secmark_demo.browser_packet (packet (send recv)))
-
+```
 
 dontaudit
 ---------
@@ -140,7 +147,9 @@ Note that these rules can be omitted by the CIL compiler command line parameter
 
 **Rule definition:**
 
+```secil
     (dontaudit source_id target_id|self classpermissionset_id ...)
+```
 
 **Where:**
 
@@ -174,7 +183,9 @@ Note that these rules can be omitted by the CIL compiler command line parameter
 
 This example will not audit the denied access:
 
+```secil
     (dontaudit zygote.process self (capability (fsetid)))
+```
 
 neverallow
 ----------
@@ -185,7 +196,9 @@ Note that these rules can be over-ridden by the CIL compiler command line parame
 
 **Rule definition:**
 
+```secil
     (neverallow source_id target_id|self classpermissionset_id ...)
+```
 
 **Where:**
 
@@ -219,6 +232,7 @@ Note that these rules can be over-ridden by the CIL compiler command line parame
 
 This example will not compile as `type_3` is not allowed to be a source type for the [`allow`](cil_access_vector_rules.md#allow) rule:
 
+```secil
     (class property_service (set))
 
     (block av_rules
@@ -232,6 +246,7 @@ This example will not compile as `type_3` is not allowed to be a source type for
         ; This rule will fail compilation:
         (allow type_3 self (property_service (set)))
     )
+```
 
 allowx
 ------
@@ -242,7 +257,9 @@ Note that for this to work there must *also* be valid equivalent [`allow`](cil_a
 
 **Rule definition:**
 
+```secil
     (allowx source_id target_id|self permissionx_id)
+```
 
 **Where:**
 
@@ -276,12 +293,14 @@ Note that for this to work there must *also* be valid equivalent [`allow`](cil_a
 
 These examples show a selection of possible permutations of [`allowx`](cil_access_vector_rules.md#allowx) rules:
 
+```secil
     (allow type_1 type_2 (tcp_socket (ioctl))) ;; pre-requisite
     (allowx type_1 type_2 (ioctl tcp_socket (range 0x2000 0x20FF)))
 
     (permissionx ioctl_nodebug (ioctl udp_socket (not (range 0x4000 0x4010))))
     (allow type_3 type_4 (udp_socket (ioctl))) ;; pre-requisite
     (allowx type_3 type_4 ioctl_nodebug)
+```
 
 
 auditallowx
@@ -293,7 +312,9 @@ Note that for this to work there must *also* be valid equivalent [`auditallow`](
 
 **Rule definition:**
 
+```secil
     (auditallowx source_id target_id|self permissionx_id)
+```
 
 **Where:**
 
@@ -327,11 +348,12 @@ Note that for this to work there must *also* be valid equivalent [`auditallow`](
 
 This example will log an audit event whenever the corresponding [`allowx`](cil_access_vector_rules.md#allowx) rule grants access to the specified extended permissions:
 
+```secil
     (allowx type_1 type_2 (ioctl tcp_socket (range 0x2000 0x20FF)))
 
     (auditallow type_1 type_2 (tcp_socket (ioctl))) ;; pre-requisite
     (auditallowx type_1 type_2 (ioctl tcp_socket (range 0x2005 0x2010)))
-
+```
 
 dontauditx
 ----------
@@ -344,7 +366,9 @@ Note that these rules can be omitted by the CIL compiler command line parameter
 
 **Rule definition:**
 
+```secil
     (dontauditx source_id target_id|self permissionx_id)
+```
 
 **Where:**
 
@@ -378,9 +402,10 @@ Note that these rules can be omitted by the CIL compiler command line parameter
 
 This example will not audit the denied access:
 
+```secil
     (allowx type_1 type_2 (ioctl tcp_socket (0x1))) ;; pre-requisite, just some irrelevant random ioctl
     (dontauditx type_1 type_2 (ioctl tcp_socket (range 0x3000 0x30FF)))
-
+```
 
 neverallowx
 ----------
@@ -390,7 +415,9 @@ Note that these rules can be over-ridden by the CIL compiler command line parame
 
 **Rule definition:**
 
+```secil
     (neverallowx source_id target_id|self permissionx_id)
+```
 
 **Where:**
 
@@ -424,6 +451,7 @@ Note that these rules can be over-ridden by the CIL compiler command line parame
 
 This example will not compile as `type_3` is not allowed to be a source type and ioctl range for the [`allowx`](cil_access_vector_rules.md#allowx) rule:
 
+```secil
 	(class property_service (ioctl))
 	(block av_rules
 		(type type_1)
@@ -435,3 +463,4 @@ This example will not compile as `type_3` is not allowed to be a source type and
 		; This rule will fail compilation:
 		(allowx type_3 self (ioctl property_service (0x20A0)))
 	)
+```

secilc/docs/cil_call_macro_statements.md

@@ -10,7 +10,9 @@ Each parameter passed contains an argument to be resolved by the [macro](#macro)
 
 **Statement definition:**
 
+```secil
     (call macro_id [(param ...)])
+```
 
 **Where:**
 
@@ -58,10 +60,12 @@ When resolving macros the following places are checked in this order:
 
 **Statement definition:**
 
+```secil
     (macro macro_id ([(param_type param_id) ...])
         cil_statements
         ...
     )
+```
 
 **Where:**
 
@@ -99,6 +103,7 @@ When resolving macros the following places are checked in this order:
 
 This example will instantiate the `binder_call` macro in the calling namespace (`my_domain`) and replace `ARG1` with `appdomain` and `ARG2` with `binderservicedomain`:
 
+```secil
     (block my_domain
         (call binder_call (appdomain binderservicedomain))
     )
@@ -108,9 +113,11 @@ This example will instantiate the `binder_call` macro in the calling namespace (
         (allow ARG2 ARG1 (binder (transfer)))
         (allow ARG1 ARG2 (fd (use)))
     )
+```
 
 This example does not pass any parameters to the macro but adds a [`type`](cil_type_statements.md#type) identifier to the current namespace:
 
+```secil
     (block unconfined
         (call add_type)
         ....
@@ -119,14 +126,17 @@ This example does not pass any parameters to the macro but adds a [`type`](cil_t
             (type exec)
         )
     )
+```
 
 This example passes an anonymous and named IP address to the macro:
 
+```secil
     (ipaddr netmask_1 255.255.255.0)
-    (context netlabel_1 (system.user object_r unconfined.object low_low)
+    (context netlabel_1 (system.user object_r unconfined.object low_low))
 
     (call build_nodecon ((192.168.1.64) netmask_1))
 
     (macro build_nodecon ((ipaddr ARG1) (ipaddr ARG2))
         (nodecon ARG1 ARG2  netlabel_1)
     )
+```

secilc/docs/cil_class_and_permission_statements.md

@@ -8,7 +8,9 @@ Declares a common identifier in the current namespace with a set of common permi
 
 **Statement definition:**
 
+```secil
     (common common_id (permission_id ...))
+```
 
 **Where:**
 
@@ -37,7 +39,9 @@ Declares a common identifier in the current namespace with a set of common permi
 
 This common statement will associate the [`common`](cil_class_and_permission_statements.md#common) identifier '`file`' with the list of permissions:
 
+```secil
     (common file (ioctl read write create getattr setattr lock relabelfrom relabelto append unlink link rename execute swapon quotaon mounton))
+```
 
 classcommon
 -----------
@@ -46,7 +50,9 @@ Associate a [`class`](cil_class_and_permission_statements.md#class) identifier t
 
 **Statement definition:**
 
+```secil
     (classcommon class_id common_id)
+```
 
 **Where:**
 
@@ -75,9 +81,11 @@ Associate a [`class`](cil_class_and_permission_statements.md#class) identifier t
 
 This associates the `dir` class with the list of permissions declared by the `file common` identifier:
 
+```secil
     (common file (ioctl read write create getattr setattr lock relabelfrom relabelto append unlink link rename execute swapon quotaon mounton))
 
     (classcommon dir file)
+```
 
 class
 -----
@@ -86,7 +94,9 @@ Declares a class and zero or more permissions in the current namespace.
 
 **Statement definition:**
 
+```secil
     (class class_id (permission_id ...))
+```
 
 **Where:**
 
@@ -115,29 +125,39 @@ Declares a class and zero or more permissions in the current namespace.
 
 This example defines a set of permissions for the `binder` class identifier:
 
+```secil
     (class binder (impersonate call set_context_mgr transfer receive))
+```
 
 This example defines a common set of permissions to be used by the `sem` class, the `(class sem ())` does not define any other permissions (i.e. an empty list):
 
+```secil
     (common ipc (create destroy getattr setattr read write associate unix_read unix_write))
 
     (classcommon sem ipc)
     (class sem ())
+```
 
 and will produce the following set of permissions for the `sem` class identifier of:
 
+```secil
     (class sem (create destroy getattr setattr read write associate unix_read unix_write))
+```
 
 This example, with the following combination of the [`common`](cil_class_and_permission_statements.md#common), [`classcommon`](cil_class_and_permission_statements.md#classcommon) and [`class`](cil_class_and_permission_statements.md#class) statements:
 
+```secil
     (common file (ioctl read write create getattr setattr lock relabelfrom relabelto append unlink link rename execute swapon quotaon mounton))
 
     (classcommon dir file)
     (class dir (add_name remove_name reparent search rmdir open audit_access execmod))
+```
 
 will produce a set of permissions for the `dir` class identifier of:
 
+```secil
     (class dir (add_name remove_name reparent search rmdir open audit_access execmod ioctl read write create getattr setattr lock relabelfrom relabelto append unlink link rename execute swapon quotaon mounton))
+```
 
 classorder
 ----------
@@ -146,7 +166,9 @@ Defines the order of [class](#class)'s. This is a mandatory statement. Multiple
 
 **Statement definition:**
 
+```secil
     (classorder (class_id ...))
+```
 
 **Where:**
 
@@ -171,11 +193,13 @@ Defines the order of [class](#class)'s. This is a mandatory statement. Multiple
 
 This will produce an ordered list of "`file dir process`"
 
+```secil
     (class process)
     (class file)
     (class dir)
     (classorder (file dir))
     (classorder (dir process))
+```
 
 **Unordered Classorder Statement:**
 
@@ -185,6 +209,7 @@ If users do not have knowledge of the existing [`classorder`](#classorder), the
 
 This will produce an unordered list of "`file dir foo a bar baz`"
 
+```secil
 	(class file)
 	(class dir)
 	(class foo)
@@ -195,6 +220,7 @@ This will produce an unordered list of "`file dir foo a bar baz`"
 	(classorder (dir foo))
 	(classorder (unordered a))
 	(classorder (unordered bar foo baz))
+```
 
 classpermission
 ---------------
@@ -203,7 +229,9 @@ Declares a class permission set identifier in the current namespace that can be
 
 **Statement definition:**
 
+```secil
     (classpermission classpermissionset_id)
+```
 
 **Where:**
 
@@ -235,7 +263,9 @@ Defines a class permission set identifier in the current namespace that associat
 
 **Statement definition:**
 
+```secil
     (classpermissionset classpermissionset_id (class_id (permission_id | expr ...)))
+```
 
 **Where:**
 
@@ -278,6 +308,7 @@ Defines a class permission set identifier in the current namespace that associat
 
 These class permission set statements will resolve to the permission sets shown in the kernel policy language [`allow`](cil_access_vector_rules.md#allow) rules:
 
+```secil
     (class zygote (specifyids specifyrlimits specifycapabilities specifyinvokewith specifyseinfo))
 
     (type test_1)
@@ -322,6 +353,7 @@ These class permission set statements will resolve to the permission sets shown
     (classpermissionset zygote_all_perms (zygote (all)))
     (allow unconfined.process test_5 zygote_all_perms)
     ;; allow unconfined.process test_5 : zygote { specifyids specifyrlimits specifycapabilities specifyinvokewith specifyseinfo } ;
+```
 
 classmap
 --------
@@ -346,7 +378,9 @@ Declares a class map identifier in the current namespace and one or more class m
 
 **Statement definition:**
 
+```secil
     (classmap classmap_id (classmapping_id ...))
+```
 
 **Where:**
 
@@ -382,7 +416,9 @@ Define sets of [`classpermissionset`](cil_class_and_permission_statements.md#cla
 
 **Statement definition:**
 
+```secil
     (classmapping classmap_id classmapping_id classpermissionset_id)
+```
 
 **Where:**
 
@@ -415,6 +451,7 @@ Define sets of [`classpermissionset`](cil_class_and_permission_statements.md#cla
 
 These class mapping statements will resolve to the permission sets shown in the kernel policy language [`allow`](cil_access_vector_rules.md#allow) rules:
 
+```secil
     (class binder (impersonate call set_context_mgr transfer receive))
     (class property_service (set))
     (class zygote (specifyids specifyrlimits specifycapabilities specifyinvokewith specifyseinfo))
@@ -454,6 +491,7 @@ These class mapping statements will resolve to the permission sets shown in the
 
     ;; allow map_example.type_3 map_example.type_3 : binder { impersonate call set_context_mgr } ;
     ;; allow map_example.type_3 map_example.type_3 : zygote { specifyrlimits specifycapabilities specifyinvokewith specifyseinfo } ;
+```
 
 permissionx
 -----------
@@ -462,7 +500,9 @@ Defines a named extended permission, which can be used in the [`allowx`](cil_acc
 
 **Statement definition:**
 
+```secil
     (permissionx permissionx_id (kind class_id (permission ... | expr ...)))
+```
 
 **Where:**
 
@@ -517,6 +557,8 @@ Defines a named extended permission, which can be used in the [`allowx`](cil_acc
 
 **Examples:**
 
+```secil
     (permissionx ioctl_1 (ioctl tcp_socket (0x2000 0x3000 0x4000)))
     (permissionx ioctl_2 (ioctl tcp_socket (range 0x6000 0x60FF)))
     (permissionx ioctl_3 (ioctl tcp_socket (and (range 0x8000 0x90FF) (not (range 0x8100 0x82FF)))))
+```

secilc/docs/cil_conditional_statements.md

@@ -8,7 +8,9 @@ Declares a run time boolean as true or false in the current namespace. The [`boo
 
 **Statement definition:**
 
+```secil
     (boolean boolean_id true|false)
+```
 
 **Where:**
 
@@ -46,7 +48,8 @@ Contains the run time conditional statements that are instantiated in the binary
 
 **Statement definition:**
 
-    (booleanif boolean_id | expr ...)
+```secil
+    (booleanif boolean_id | expr ...
         (true
             cil_statements
             ...)
@@ -54,6 +57,7 @@ Contains the run time conditional statements that are instantiated in the binary
             cil_statements
             ...)
     )
+```
 
 **Where:**
 
@@ -96,6 +100,7 @@ Contains the run time conditional statements that are instantiated in the binary
 
 The second example also shows the kernel policy language equivalent:
 
+```secil
     (boolean disableAudio false)
 
     (booleanif disableAudio
@@ -112,6 +117,7 @@ The second example also shows the kernel policy language equivalent:
             (allow process mediaserver.audio_capture_device (chr_file_set (rw_file_perms)))
         )
     )
+```
 
 tunable
 -------
@@ -122,7 +128,9 @@ Note that tunables can be treated as booleans by the CIL compiler command line p
 
 **Statement definition:**
 
+```secil
     (tunable tunable_id true|false)
+```
 
 **Where:**
 
@@ -158,7 +166,8 @@ Compile time conditional statement that may or may not add CIL statements to be
 
 **Statement definition:**
 
-    (tunableif tunable_id | expr ...)
+```secil
+    (tunableif tunable_id | expr ...
         (true
             cil_statements
             ...)
@@ -166,6 +175,7 @@ Compile time conditional statement that may or may not add CIL statements to be
             cil_statements
             ...)
     )
+```
 
 **Where:**
 
@@ -208,6 +218,7 @@ Compile time conditional statement that may or may not add CIL statements to be
 
 This example will not add the range transition rule to the binary policy:
 
+```secil
     (tunable range_trans_rule false)
 
     (block init
@@ -220,3 +231,4 @@ This example will not add the range transition rule to the binary policy:
             )
         ) ; End tunableif
     ) ; End block
+```

secilc/docs/cil_constraint_statements.md

@@ -8,7 +8,9 @@ Enable constraints to be placed on the specified permissions of the object class
 
 **Statement definition:**
 
+```secil
     (constrain classpermissionset_id ... expression | expr ...)
+```
 
 **Where:**
 
@@ -62,6 +64,7 @@ Enable constraints to be placed on the specified permissions of the object class
 
 Two constrain statements are shown with their equivalent kernel policy language statements:
 
+```secil
     ;; constrain { file } { write }
     ;;    (( t1 == unconfined.process  ) and ( t2 == unconfined.object  ) or ( r1 eq r2 ));
     (constrain (file (write))
@@ -87,6 +90,7 @@ Two constrain statements are shown with their equivalent kernel policy language
             )
         )
     )
+```
 
 validatetrans
 -------------
@@ -95,7 +99,9 @@ The [`validatetrans`](cil_constraint_statements.md#validatetrans) statement is o
 
 **Statement definition:**
 
+```secil
     (validatetrans class_id expression | expr ...)
+```
 
 **Where:**
 
@@ -153,9 +159,11 @@ The [`validatetrans`](cil_constraint_statements.md#validatetrans) statement is o
 
 A validate transition statement with the equivalent kernel policy language statement:
 
+```secil
     ; validatetrans { file } ( t1 == unconfined.process  );
 
     (validatetrans file (eq t1 unconfined.process))
+```
 
 mlsconstrain
 ------------
@@ -164,7 +172,9 @@ Enable MLS constraints to be placed on the specified permissions of the object c
 
 **Statement definition:**
 
+```secil
     (mlsconstrain classpermissionset_id ... expression | expr ...)
+```
 
 **Where:**
 
@@ -224,6 +234,7 @@ Enable MLS constraints to be placed on the specified permissions of the object c
 
 An MLS constrain statement with the equivalent kernel policy language statement:
 
+```secil
     ;; mlsconstrain { file } { open }
     ;;     (( l1 eq l2 ) and ( u1 == u2 ) or ( r1 != r2 ));
 
@@ -236,6 +247,7 @@ An MLS constrain statement with the equivalent kernel policy language statement:
             (neq r1 r2)
         )
     )
+```
 
 mlsvalidatetrans
 ----------------
@@ -244,7 +256,9 @@ The [`mlsvalidatetrans`](cil_constraint_statements.md#mlsvalidatetrans) statemen
 
 **Statement definition:**
 
+```secil
     (mlsvalidatetrans class_id expression | expr ...)
+```
 
 **Where:**
 
@@ -308,6 +322,8 @@ The [`mlsvalidatetrans`](cil_constraint_statements.md#mlsvalidatetrans) statemen
 
 An MLS validate transition statement with the equivalent kernel policy language statement:
 
+```secil
     ;; mlsvalidatetrans { file } ( l1 domby h2 );
 
     (mlsvalidatetrans file (domby l1 h2))
+```

secilc/docs/cil_container_statements.md

@@ -8,10 +8,12 @@ Start a new namespace where any CIL statement is valid.
 
 **Statement definition:**
 
+```secil
     (block block_id
         cil_statement
         ...
     )
+```
 
 **Where:**
 
@@ -47,11 +49,13 @@ Declares the namespace as a 'template' and does not generate code until instanti
 
 **Statement definition:**
 
+```secil
     (block block_id
         (blockabstract template_id)
         cil_statement
         ...
     )
+```
 
 **Where:**
 
@@ -95,11 +99,13 @@ Used to add common policy rules to the current namespace via a template that has
 
 **Statement definition:**
 
+```secil
     (block block_id
         (blockinherit template_id)
         cil_statement
         ...
     )
+```
 
 **Where:**
 
@@ -136,6 +142,7 @@ Used to add common policy rules to the current namespace via a template that has
 
 This example contains a template `client_server` that is instantiated in two blocks (`netserver_app` and `netclient_app`):
 
+```secil
     ; This is the template block:
     (block client_server
         (blockabstract client_server)
@@ -187,6 +194,7 @@ This example contains a template `client_server` that is instantiated in two blo
     (block ab
         (blockinherit b)
         (blockinherit a))
+```
 
 optional
 --------
@@ -203,10 +211,12 @@ Declare an [`optional`](cil_container_statements.md#optional) namespace. All CIL
 
 **Statement definition:**
 
+```secil
     (optional optional_id
         cil_statement
         ...
     )
+```
 
 **Where:**
 
@@ -235,6 +245,7 @@ Declare an [`optional`](cil_container_statements.md#optional) namespace. All CIL
 
 This example will instantiate the optional block `ext_gateway.move_file` into policy providing all optional CIL statements can be resolved:
 
+```secil
     (block ext_gateway
         ......
         (optional move_file
@@ -250,6 +261,7 @@ This example will instantiate the optional block `ext_gateway.move_file` into po
 
         .....
     ) ; End block
+```
 
 in
 --
@@ -258,10 +270,12 @@ Allows the insertion of CIL statements into a named container ([`block`](cil_con
 
 **Statement definition:**
 
+```secil
     (in container_id
         cil_statement
         ...
     )
+```
 
 **Where:**
 
@@ -290,7 +304,9 @@ Allows the insertion of CIL statements into a named container ([`block`](cil_con
 
 This will add rules to the container named `system_server`:
 
+```secil
     (in system_server
         (dontaudit process secmark_demo.dns_packet (packet (send recv)))
         (allow process secmark_demo.dns_packet (packet (send recv)))
     )
+```

secilc/docs/cil_context_statement.md

@@ -16,7 +16,9 @@ Declare an SELinux security context identifier for labeling. The range (or curre
 
 **Statement definition:**
 
+```secil
     (context context_id (user_id role_id type_id levelrange_id)))
+```
 
 **Where:**
 
@@ -57,21 +59,29 @@ Declare an SELinux security context identifier for labeling. The range (or curre
 
 This example uses a named context definition:
 
+```secil
     (context runas_exec_context (u object_r exec low_low))
 
     (filecon "/system/bin/run-as" file runas_exec_context)
+```
 
 to resolve/build a `file_contexts` entry of (assuming MLS enabled policy):
 
+```
     /system/bin/run-as  -- u:object_r:runas.exec:s0-s0
+```
 
 This example uses an anonymous context where the previously declared `user role type levelrange` identifiers are used to specify two [`portcon`](cil_network_labeling_statements.md#portcon) statements:
 
+```secil
     (portcon udp 1024 (test.user object_r test.process ((s0) (s1))))
     (portcon tcp 1024 (test.user object_r test.process (system_low system_high)))
+```
 
 This example uses an anonymous context for the first and named context for the second in a [`netifcon`](cil_network_labeling_statements.md#netifcon) statement:
 
+```secil
     (context netif_context (test.user object_r test.process ((s0 (c0)) (s1 (c0)))))
 
     (netifcon eth04 (test.user object_r test.process ((s0 (c0)) (s1 (c0)))) netif_context)
+```

secilc/docs/cil_default_object_statements.md

@@ -10,7 +10,9 @@ Allows the default user to be taken from the source or target context when compu
 
 **Statement definition:**
 
+```secil
     (defaultuser class_id default)
+```
 
 **Where:**
 
@@ -39,6 +41,7 @@ Allows the default user to be taken from the source or target context when compu
 
 When creating new `binder`, `property_service`, `zygote` or `memprotect` objects the [`user`](cil_user_statements.md#user) component of the new security context will be taken from the `source` context:
 
+```secil
     (class binder (impersonate call set_context_mgr transfer receive))
     (class property_service (set))
     (class zygote (specifyids specifyrlimits specifycapabilities specifyinvokewith specifyseinfo))
@@ -56,13 +59,16 @@ When creating new `binder`, `property_service`, `zygote` or `memprotect` objects
     ;; default_user zygote source;
     ;; default_user property_service source;
     ;; default_user memprotect source;
+```
 
 defaultrole
 -----------
 
 Allows the default role to be taken from the source or target context when computing a new context for the object [`class`](cil_class_and_permission_statements.md#class) identifier. Requires policy version 27.
 
+```secil
     (defaultrole class_id default)
+```
 
 **Where:**
 
@@ -91,6 +97,7 @@ Allows the default role to be taken from the source or target context when compu
 
 When creating new `binder`, `property_service` or `zygote` objects the [`role`](cil_role_statements.md#role) component of the new security context will be taken from the `target` context:
 
+```secil
     (class binder (impersonate call set_context_mgr transfer receive))
     (class property_service (set))
     (class zygote (specifyids specifyrlimits specifycapabilities specifyinvokewith specifyseinfo))
@@ -101,6 +108,7 @@ When creating new `binder`, `property_service` or `zygote` objects the [`role`](
     ;; default_role binder target;
     ;; default_role zygote target;
     ;; default_role property_service target;
+```
 
 defaulttype
 -----------
@@ -109,7 +117,9 @@ Allows the default type to be taken from the source or target context when compu
 
 **Statement definition:**
 
+```secil
     (defaulttype class_id default)
+```
 
 **Where:**
 
@@ -138,7 +148,9 @@ Allows the default type to be taken from the source or target context when compu
 
 When creating a new `socket` object, the [`type`](cil_type_statements.md#type) component of the new security context will be taken from the `source` context:
 
+```secil
     (defaulttype socket source)
+```
 
 defaultrange
 ------------
@@ -147,7 +159,9 @@ Allows the default level or range to be taken from the source, target, or both c
 
 **Statement definition:**
 
+```secil
     (defaultrange class_id default <range>)
+```
 
 **Where:**
 
@@ -180,8 +194,12 @@ Allows the default level or range to be taken from the source, target, or both c
 
 When creating a new `file` object, the appropriate `range` component of the new security context will be taken from the `target` context:
 
+```secil
     (defaultrange file target low_high)
+```
 
 MLS userspace object managers may need to compute the common parts of a range such that the object is created with the range common to the subject and containing object:
 
+```secil
     (defaultrange db_table glblub)
+```

secilc/docs/cil_file_labeling_statements.md

@@ -8,7 +8,9 @@ Define entries for labeling files. The compiler will produce these entries in a
 
 **Statement definition:**
 
+```secil
     (filecon "path" file_type context_id)
+```
 
 **Where:**
 
@@ -89,17 +91,21 @@ Define entries for labeling files. The compiler will produce these entries in a
 
 These examples use one named, one anonymous and one empty context definition:
 
+```secil
     (context runas_exec_context (u object_r exec low_low))
 
     (filecon "/system/bin/run-as" file runas_exec_context)
     (filecon "/dev/socket/wpa_wlan[0-9]" any u:object_r:wpa.socket:s0-s0)
     (filecon "/data/local/mine" dir ())
+```
 
 to resolve/build `file_contexts` entries of (assuming MLS enabled policy):
 
+```
     /system/bin/run-as  -- u:object_r:runas.exec:s0
     /dev/socket/wpa_wlan[0-9]   u:object_r:wpa.socket:s0
     /data/local/mine -d <<none>>
+```
 
 fsuse
 -----
@@ -108,7 +114,9 @@ Label filesystems that support SELinux security contexts.
 
 **Statement definition:**
 
+```secil
     (fsuse fstype fsname context_id)
+```
 
 **Where:**
 
@@ -147,6 +155,7 @@ Label filesystems that support SELinux security contexts.
 
 The [context](#context) identifiers are declared in the `file` namespace and the [`fsuse`](cil_file_labeling_statements.md#fsuse) statements in the global namespace:
 
+```secil
     (block file
         (type labeledfs)
         (roletype object_r labeledfs)
@@ -166,6 +175,7 @@ The [context](#context) identifiers are declared in the `file` namespace and the
 
     (fsuse trans devpts file.devpts_context)
     (fsuse trans tmpfs file.tmpfs_context)
+```
 
 genfscon
 --------
@@ -174,7 +184,9 @@ Used to allocate a security context to filesystems that cannot support any of th
 
 **Statement definition:**
 
+```secil
     (genfscon fsname path context_id)
+```
 
 **Where:**
 
@@ -207,6 +219,7 @@ Used to allocate a security context to filesystems that cannot support any of th
 
 The [context](#context) identifiers are declared in the `file` namespace and the [`genfscon`](cil_file_labeling_statements.md#genfscon) statements are then inserted using the [`in`](cil_container_statements.md#in) container statement:
 
+```secil
     (file
         (type rootfs)
         (roletype object_r rootfs)
@@ -226,3 +239,4 @@ The [context](#context) identifiers are declared in the `file` namespace and the
         (genfscon proc /sysrq-trigger sysrq_proc_context)
         (genfscon selinuxfs / selinuxfs_context)
     )
+```

secilc/docs/cil_infiniband_statements.md

@@ -10,7 +10,9 @@ Label IB partition keys. This may be a single key or a range.
 
 **Statement definition:**
 
+```secil
     (ibpkeycon subnet pkey|(pkey_low pkey_high)  context_id)
+```
 
 **Where:**
 
@@ -43,8 +45,9 @@ Label IB partition keys. This may be a single key or a range.
 
 An anonymous context for a partition key range of `0x0-0x10` assigned to an IPv6 subnet:
 
+```secil
     (ibpkeycon fe80:: (0 0x10) (system_u system_r kernel_t (low (s3 (cats01 cats02)))))
-
+```
 
 ibendportcon
 ------------
@@ -53,7 +56,9 @@ Label IB end ports.
 
 **Statement definition:**
 
+```secil
     (ibendportcon device_id port context_id)
+```
 
 **Where:**
 
@@ -86,4 +91,6 @@ Label IB end ports.
 
 A named context for device `mlx5_0` on port `1`:
 
+```secil
     (ibendportcon mlx5_0 1 system_u_bin_t_l2h)
+```

secilc/docs/cil_mls_labeling_statements.md

@@ -10,7 +10,9 @@ Declare a sensitivity identifier in the current namespace. Multiple [`sensitivit
 
 **Statement definition:**
 
+```secil
     (sensitivity sensitivity_id)
+```
 
 **Where:**
 
@@ -35,9 +37,11 @@ Declare a sensitivity identifier in the current namespace. Multiple [`sensitivit
 
 This example declares three [`sensitivity`](cil_mls_labeling_statements.md#sensitivity) identifiers:
 
+```secil
     (sensitivity s0)
     (sensitivity s1)
     (sensitivity s2)
+```
 
 sensitivityalias
 ----------------
@@ -46,7 +50,9 @@ Declares a sensitivity alias identifier in the current namespace. See the [`sens
 
 **Statement definition:**
 
+```secil
     (sensitivityalias sensitivityalias_id)
+```
 
 **Where:**
 
@@ -78,7 +84,9 @@ Associates a previously declared [`sensitivityalias`](cil_mls_labeling_statement
 
 **Statement definition:**
 
+```secil
     (sensitivityaliasactual sensitivityalias_id sensitivity_id)
+```
 
 **Where:**
 
@@ -107,11 +115,13 @@ Associates a previously declared [`sensitivityalias`](cil_mls_labeling_statement
 
 This example will associate sensitivity `s0` with two sensitivity alias's:
 
+```secil
     (sensitivity s0)
     (sensitivityalias unclassified)
     (sensitivityalias SystemLow)
     (sensitivityaliasactual unclassified s0)
     (sensitivityaliasactual SystemLow s0)
+```
 
 sensitivityorder
 ----------------
@@ -120,7 +130,9 @@ Define the sensitivity order - lowest to highest. Multiple [`sensitivityorder`](
 
 **Statement definition:**
 
+```secil
     (sensitivityorder (sensitivity_id ...))
+```
 
 **Where:**
 
@@ -145,6 +157,7 @@ Define the sensitivity order - lowest to highest. Multiple [`sensitivityorder`](
 
 This example shows two [`sensitivityorder`](cil_mls_labeling_statements.md#sensitivityorder) statements that when compiled will form an ordered list. Note however that the second [`sensitivityorder`](cil_mls_labeling_statements.md#sensitivityorder) statement starts with `s2` so that the ordered list can be built.
 
+```secil
     (sensitivity s0)
     (sensitivityalias s0 SystemLow)
     (sensitivity s1)
@@ -155,6 +168,7 @@ This example shows two [`sensitivityorder`](cil_mls_labeling_statements.md#sensi
     (sensitivity s4)
     (sensitivityalias s4 SystemHigh)
     (sensitivityorder (s2 s3 SystemHigh))
+```
 
 category
 --------
@@ -163,7 +177,9 @@ Declare a category identifier in the current namespace. Multiple category statem
 
 **Statement definition:**
 
+```secil
     (category category_id)
+```
 
 **Where:**
 
@@ -188,9 +204,11 @@ Declare a category identifier in the current namespace. Multiple category statem
 
 This example declares a three [`category`](cil_mls_labeling_statements.md#category) identifiers:
 
+```secil
     (category c0)
     (category c1)
     (category c2)
+```
 
 categoryalias
 -------------
@@ -199,7 +217,9 @@ Declares a category alias identifier in the current namespace. See the [`categor
 
 **Statement definition:**
 
+```secil
     (categoryalias categoryalias_id)
+```
 
 **Where:**
 
@@ -227,7 +247,9 @@ Associates a previously declared [`categoryalias`](cil_mls_labeling_statements.m
 
 **Statement definition:**
 
+```secil
     (categoryaliasactual categoryalias_id category_id)
+```
 
 **Where:**
 
@@ -256,9 +278,11 @@ Associates a previously declared [`categoryalias`](cil_mls_labeling_statements.m
 
 Declares a category `c0`, a category alias of `documents`, and then associates them:
 
+```secil
     (category c0)
     (categoryalias documents)
     (categoryaliasactual documents c0)
+```
 
 categoryorder
 -------------
@@ -267,7 +291,9 @@ Define the category order. Multiple [`categoryorder`](cil_mls_labeling_statement
 
 **Statement definition:**
 
+```secil
     (categoryorder (category_id ...))
+```
 
 **Where:**
 
@@ -292,7 +318,9 @@ Define the category order. Multiple [`categoryorder`](cil_mls_labeling_statement
 
 This example orders one category alias and nine categories:
 
+```secil
     (categoryorder (documents c1 c2 c3 c4 c5 c6 c7 c8 c9)
+```
 
 categoryset
 -----------
@@ -307,7 +335,9 @@ Notes:
 
 **Statement definition:**
 
+```secil
     (categoryset categoryset_id (category_id ... | expr ...))
+```
 
 **Where:**
 
@@ -347,6 +377,7 @@ Notes:
 
 These examples show a selection of [`categoryset`](cil_mls_labeling_statements.md#categoryset) statements:
 
+```secil
     ; Declare categories with two alias's:
     (category c0)
     (categoryalias documents)
@@ -372,6 +403,7 @@ These examples show a selection of [`categoryset`](cil_mls_labeling_statements.m
     (categoryset catset_3 (c4))
 
     (categoryset just_c0 (xor (c1 c2) (documents c1 c2)))
+```
 
 sensitivitycategory
 -------------------
@@ -380,7 +412,9 @@ Associate a [`sensitivity`](cil_mls_labeling_statements.md#sensitivity) identifi
 
 **Statement definition:**
 
+```secil
     (sensitivitycategory sensitivity_id categoryset_id)
+```
 
 **Where:**
 
@@ -409,11 +443,13 @@ Associate a [`sensitivity`](cil_mls_labeling_statements.md#sensitivity) identifi
 
 These [`sensitivitycategory`](cil_mls_labeling_statements.md#sensitivitycategory) examples use a selection of [`category`](cil_mls_labeling_statements.md#category), [`categoryalias`](cil_mls_labeling_statements.md#categoryalias) and [`categoryset`](cil_mls_labeling_statements.md#categoryset)'s:
 
+```secil
     (sensitivitycategory s0 catrange_1)
     (sensitivitycategory s0 catset_1)
     (sensitivitycategory s0 catset_3)
     (sensitivitycategory s0 (all))
     (sensitivitycategory unclassified (range documents c2))
+```
 
 level
 -----
@@ -422,7 +458,9 @@ Declare a [`level`](cil_mls_labeling_statements.md#level) identifier in the curr
 
 **Statement definition:**
 
-    level level_id (sensitivity_id [categoryset_id])
+```secil
+    (level level_id (sensitivity_id [categoryset_id]))
+```
 
 **Where:**
 
@@ -455,11 +493,13 @@ Declare a [`level`](cil_mls_labeling_statements.md#level) identifier in the curr
 
 These [`level`](cil_mls_labeling_statements.md#level) examples use a selection of [`category`](cil_mls_labeling_statements.md#category), [`categoryalias`](cil_mls_labeling_statements.md#categoryalias) and [`categoryset`](cil_mls_labeling_statements.md#categoryset)'s:
 
+```secil
     (level systemLow (s0))
     (level level_1 (s0))
     (level level_2 (s0 (catrange_1)))
     (level level_3 (s0 (all_cats)))
     (level level_4 (unclassified (c2 c3 c4)))
+```
 
 levelrange
 ----------
@@ -468,7 +508,9 @@ Declare a level range identifier in the current namespace and associate a curren
 
 **Statement definition:**
 
+```secil
     (levelrange levelrange_id (low_level_id high_level_id))
+```
 
 **Where:**
 
@@ -501,6 +543,7 @@ Declare a level range identifier in the current namespace and associate a curren
 
 This example policy shows [`levelrange`](cil_mls_labeling_statements.md#levelrange) statement and all the other MLS labeling statements discussed in this section and will compile as a standalone policy:
 
+```secil
     (handleunknown allow)
     (mls true)
 
@@ -581,6 +624,7 @@ This example policy shows [`levelrange`](cil_mls_labeling_statements.md#levelran
 
         (context context_1 (user object_r object low_low))
     ) ; End unconfined namespace
+```
 
 rangetransition
 ---------------
@@ -589,7 +633,9 @@ Allows an objects level to transition to a different level. Generally used to en
 
 **Statement definition:**
 
+```secil
     (rangetransition source_id target_id class_id new_range_id)
+```
 
 **Where:**
 
@@ -626,13 +672,15 @@ Allows an objects level to transition to a different level. Generally used to en
 
 This rule will transition the range of `sshd.exec` to `s0 - s1:c0.c3` on execution from the `init.process`:
 
+```secil
     (sensitivity s0)
     (sensitivity s1)
     (sensitivityorder s0 s1)
     (category c0)
     ...
-    (level systemlow (s0)
+    (level systemlow (s0))
     (level systemhigh (s1 (c0 c1 c2)))
     (levelrange low_high (systemlow systemhigh))
 
     (rangetransition init.process sshd.exec process low_high)
+```

secilc/docs/cil_network_labeling_statements.md

@@ -14,7 +14,9 @@ Notes:
 
 **Statement definition:**
 
+```secil
     (ipaddr ipaddr_id ip_address)
+```
 
 **Where:**
 
@@ -43,13 +45,15 @@ Notes:
 
 This example declares a named IP address and also passes an 'explicit anonymously declared' IP address to a macro:
 
+```secil
     (ipaddr netmask_1 255.255.255.0)
-    (context netlabel_1 (system.user object_r unconfined.object low_low)
+    (context netlabel_1 (system.user object_r unconfined.object low_low))
 
     (call build_nodecon ((192.168.1.64) netmask_1))
 
     (macro build_nodecon ((ipaddr ARG1) (ipaddr ARG2))
         (nodecon ARG1 ARG2  netlabel_1))
+```
 
 netifcon
 --------
@@ -58,7 +62,9 @@ Label network interface objects (e.g. `eth0`).
 
 **Statement definition:**
 
+```secil
     (netifcon netif_name netif_context_id packet_context_id)
+```
 
 **Where:**
 
@@ -93,12 +99,14 @@ Label network interface objects (e.g. `eth0`).
 
 These examples show named and anonymous [`netifcon`](cil_network_labeling_statements.md#netifcon) statements:
 
+```secil
     (context context_1 (unconfined.user object_r unconfined.object low_low))
     (context context_2 (unconfined.user object_r unconfined.object (systemlow level_2)))
 
     (netifcon eth0 context_1 (unconfined.user object_r unconfined.object levelrange_1))
     (netifcon eth1 context_1 (unconfined.user object_r unconfined.object ((s0) level_1)))
     (netifcon eth3 context_1 context_2)
+```
 
 nodecon
 -------
@@ -109,7 +117,9 @@ IP Addresses may be declared without a previous declaration by enclosing within
 
 **Statement definition:**
 
+```secil
     (nodecon subnet_id netmask_id context_id)
+```
 
 **Where:**
 
@@ -142,6 +152,7 @@ IP Addresses may be declared without a previous declaration by enclosing within
 
 These examples show named and anonymous [`nodecon`](cil_network_labeling_statements.md#nodecon) statements:
 
+```secil
     (context context_1 (unconfined.user object_r unconfined.object low_low))
     (context context_2 (unconfined.user object_r unconfined.object (systemlow level_2)))
 
@@ -160,6 +171,7 @@ These examples show named and anonymous [`nodecon`](cil_network_labeling_stateme
     (nodecon ipv6_2 netmask_2 context_3)
     (nodecon (2001:db8:1:0:0:0:0:0) (ffff:ffff:ffff:0:0:0:0:0) context_3)
     (nodecon (2001:db8:1:0:0:0:0:0) netmask_2 (sys.id sys.role my48prefix.node ((s0)(s0))))
+```
 
 portcon
 -------
@@ -168,7 +180,9 @@ Label a udp, tcp, dccp or sctp port.
 
 **Statement definition:**
 
+```secil
     (portcon protocol port|(port_low port_high) context_id)
+```
 
 **Where:**
 
@@ -203,6 +217,7 @@ Label a udp, tcp, dccp or sctp port.
 
 These examples show named and anonymous [`portcon`](cil_network_labeling_statements.md#portcon) statements:
 
+```secil
     (portcon tcp 1111 (unconfined.user object_r unconfined.object ((s0) (s0 (c0)))))
     (portcon tcp 2222 (unconfined.user object_r unconfined.object levelrange_2))
     (portcon tcp 3333 (unconfined.user object_r unconfined.object levelrange_1))
@@ -210,3 +225,4 @@ These examples show named and anonymous [`portcon`](cil_network_labeling_stateme
     (portcon tcp (2000 20000) (unconfined.user object_r unconfined.object (systemlow level_3)))
     (portcon dccp (6840 6880) (unconfined.user object_r unconfined.object ((s0) level_2)))
     (portcon sctp (1024 1035) (unconfined.user object_r unconfined.object ((s0) level_2)))
+```

secilc/docs/cil_policy_config_statements.md

@@ -10,7 +10,9 @@ Note that this can be over-ridden by the CIL compiler command line parameter `-M
 
 **Statement definition:**
 
+```secil
     (mls boolean)
+```
 
 **Where:**
 
@@ -33,7 +35,9 @@ Note that this can be over-ridden by the CIL compiler command line parameter `-M
 
 **Example:**
 
+```secil
     (mls true)
+```
 
 handleunknown
 -------------
@@ -44,7 +48,9 @@ Note that this can be over-ridden by the CIL compiler command line parameter `-U
 
 **Statement definition:**
 
+```secil
     (handleunknown action)
+```
 
 **Where:**
 
@@ -72,7 +78,9 @@ Note that this can be over-ridden by the CIL compiler command line parameter `-U
 
 This will allow unknown classes / permissions to be present in the policy:
 
+```secil
     (handleunknown allow)
+```
 
 policycap
 ---------
@@ -81,7 +89,9 @@ Allow policy capabilities to be enabled via policy. These should be declared in
 
 **Statement definition:**
 
+```secil
     (policycap policycap_id)
+```
 
 **Where:**
 
@@ -106,8 +116,10 @@ Allow policy capabilities to be enabled via policy. These should be declared in
 
 These set two valid policy capabilities:
 
+```secil
     ; Enable networking controls.
     (policycap network_peer_controls)
 
     ; Enable open permission check.
     (policycap open_perms)
+```

secilc/docs/cil_reference_guide.md

@@ -57,10 +57,12 @@ Declarations may be named or anonymous and have three different forms:
     ipaddr
     macro
     policycap
+
 2.  Explicit anonymous declarations - These are currently restricted to IP addresses where they can be declared directly in statements by enclosing them within parentheses e.g. `(127.0.0.1)` or `(::1)`. See the [Network Labeling Statements](#network_labeling) section for examples.
 
 3.  Anonymous declarations - These have been previously declared and the object already exists, therefore they may be referenced by their name or identifier within statements. For example the following declare all the components required to specify a context:
 
+    ```secil
         (sensitivity s0)
         (category c0)
         (role object_r)
@@ -69,10 +71,13 @@ Declarations may be named or anonymous and have three different forms:
             (user user)
             (type object)
         )
+    ```
 
     now a [`portcon`](cil_network_labeling_statements.md#portcon) statement can be defined that uses these individual components to build a context as follows:
 
+    ```secil
         (portcon udp 12345 (unconfined.user object_r unconfined.object ((s0) (s0(c0)))))
+    ```
 
 Definitions
 -----------
@@ -113,6 +118,7 @@ Namespaces
 
 CIL supports namespaces via containers such as the [`block`](cil_container_statements.md#block) statement. When a block is resolved to form the parent / child relationship a dot '`.`' is used, for example the following [`allow`](cil_access_vector_rules.md#allow) rule:
 
+```secil
     (block example_ns
         (type process)
         (type object)
@@ -120,16 +126,20 @@ CIL supports namespaces via containers such as the [`block`](cil_container_state
 
         (allow process object (file (open read getattr)))
     )
+```
 
 will resolve to the following kernel policy language statement:
 
+```
     allow example_ns.process example_ns.object : example_ns.file { open read getattr };
+```
 
 Global Namespace
 ----------------
 
 CIL has a global namespace that is always present. Any symbol that is declared outside a container is in the global namespace. To reference a symbol in global namespace, the symbol should be prefixed with a dot '`.`' as shown in the following example:
 
+```secil
     ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
     ; This example has three namespace 'tmpfs' types declared:
     ;    1) Global .tmpfs
@@ -170,6 +180,7 @@ CIL has a global namespace that is always present. Any symbol that is declared o
     (block other_ns
         (type tmpfs)
     )
+```
 
 Should the symbol not be prefixed with a dot, the current namespace would be searched first and then the global namespace (provided there is not a symbol of that name in the current namespace).
 
@@ -180,9 +191,11 @@ Expressions may occur in the following CIL statements: [`booleanif`](cil_conditi
 
 CIL expressions use the [prefix](http://www.cs.man.ac.uk/~pjj/cs212/fix.html) or Polish notation and may be nested (note that the kernel policy language uses postfix or reverse Polish notation). The syntax is as follows, where the parenthesis are part of the syntax:
 
+```
     expr_set = (name ... | expr ...)
     expr = (expr_key expr_set ...)
     expr_key = and | or | xor | not | all | eq | neq | dom | domby | incomp | range
+```
 
 The number of `expr_set`'s in an `expr` is dependent on the statement type (there are four different classes as defined below) that also influence the valid `expr_key` entries (e.g. `dom`, `domby`, `incomp` are only allowed in constraint statements).
 
@@ -204,6 +217,7 @@ The number of `expr_set`'s in an `expr` is dependent on the statement type (ther
 
     This example includes all `fs_type type` entries except `file.usermodehelper` and `file.proc_security` in the associated [`typeattribute`](cil_type_statements.md#typeattribute) identifier `all_fs_type_except_usermodehelper_and_proc_security`:
 
+    ```secil
         (typeattribute all_fs_type_except_usermodehelper_and_proc_security)
 
         (typeattributeset all_fs_type_except_usermodehelper_and_proc_security
@@ -215,17 +229,21 @@ The number of `expr_set`'s in an `expr` is dependent on the statement type (ther
                 (not file.proc_security)
             )
         )
+    ```
 
     The `cps_1 classpermissionset` identifier includes all permissions except `load_policy` and `setenforce`:
 
+    ```secil
         (class security (compute_av compute_create compute_member check_context load_policy compute_relabel compute_user setenforce setbool setsecparam setcheckreqprot read_policy))
 
         (classpermission cps_1)
 
         (classpermissionset cps_1 (security (not (load_policy setenforce))))
+    ```
 
     This example includes all permissions in the associated [`classpermissionset`](cil_class_and_permission_statements.md#classpermissionset) identifier `security_all_perms`:
 
+    ```secil
         (class security (compute_av compute_create compute_member check_context load_policy
             compute_relabel compute_user setenforce setbool setsecparam setcheckreqprot
             read_policy)
@@ -234,6 +252,7 @@ The number of `expr_set`'s in an `expr` is dependent on the statement type (ther
         (classpermission security_all_perms)
 
         (classpermissionset security_all_perms (security (all)))
+    ```
 
 2.  The [`categoryset`](cil_mls_labeling_statements.md#categoryset) statement allows `expr_set` to mix names and `expr_key` values of: `and`, `or`, `not`, `xor`, `all`, `range` as shown in the examples.
 
@@ -241,6 +260,7 @@ The number of `expr_set`'s in an `expr` is dependent on the statement type (ther
 
 3.  The [`booleanif`](cil_conditional_statements.md#booleanif) and [`tunableif`](cil_conditional_statements.md#tunableif) statements only allow an `expr_set` to have one `name` or `expr` with `expr_key` values of `and`, `or`, `xor`, `not`, `eq`, `neq` as shown in the examples:
 
+    ```secil
         (booleanif disableAudio
             (false
                 (allow process device.audio_device (chr_file_set (rw_file_perms)))
@@ -252,9 +272,11 @@ The number of `expr_set`'s in an `expr` is dependent on the statement type (ther
                 (allow process device.audio_capture_device (chr_file_set (rw_file_perms)))
             )
         )
+    ```
 
 4.  The [`constrain`](cil_constraint_statements.md#constrain), [`mlsconstrain`](cil_constraint_statements.md#mlsconstrain), [`validatetrans`](cil_constraint_statements.md#validatetrans) and [`mlsvalidatetrans`](cil_constraint_statements.md#mlsvalidatetrans) statements only allow an `expr_set` to have one `name` or `expr` with `expr_key` values of `and`, `or`, `not`, `all`, `eq`, `neq`, `dom`, `domby`, `incomp`. When `expr_key` is `dom`, `domby` or `incomp`, it must be followed by a string (e.g. `h1`, `l2`) and another string or a set of `name`s. The following examples show CIL constraint statements and their policy language equivalents:
 
+    ```secil
         ; Process transition:  Require equivalence unless the subject is trusted.
         (mlsconstrain (process (transition dyntransition))
             (or (and (eq h1 h2) (eq l1 l2)) (eq t1 mlstrustedsubject)))
@@ -270,29 +292,36 @@ The number of `expr_set`'s in an `expr` is dependent on the statement type (ther
         ; The equivalent policy language mlsconstrain statememt is:
         ;mlsconstrain process { getsched getsession getpgid getcap getattr ptrace share }
         ;    (l1 dom l2 or t1 == mlstrustedsubject);
+    ```
 
 Name String
 -----------
 
 Used to define [`macro`](cil_call_macro_statements.md#macro) statement parameter string types:
 
+```secil
     (call macro1("__kmsg__"))
 
     (macro macro1 ((string ARG1))
         (typetransition audit.process device.device chr_file ARG1 device.klog_device)
     )
+```
 
 Alternatively:
 
+```secil
     (call macro1("__kmsg__"))
 
     (macro macro1 ((name ARG1))
         (typetransition audit.process device.device chr_file ARG1 device.klog_device)
     )
+```
 
 self
 ----
 
 The [`self`](cil_reference_guide.md#self) keyword may be used as the target in AVC rule statements, and means that the target is the same as the source as shown in the following example:.
 
+```secil
     (allow unconfined.process self (file (read write)))
+```

secilc/docs/cil_role_statements.md

@@ -8,7 +8,9 @@ Declares a role identifier in the current namespace.
 
 **Statement definition:**
 
+```secil
     (role role_id)
+```
 
 **Where:**
 
@@ -33,11 +35,13 @@ Declares a role identifier in the current namespace.
 
 This example declares two roles: `object_r` in the global namespace and `unconfined.role`:
 
+```secil
     (role object_r)
 
     (block unconfined
         (role role)
     )
+```
 
 roletype
 --------
@@ -46,7 +50,9 @@ Authorises a [`role`](cil_role_statements.md#role) to access a [`type`](cil_type
 
 **Statement definition:**
 
+```secil
     (role role_id type_id)
+```
 
 **Where:**
 
@@ -75,11 +81,13 @@ Authorises a [`role`](cil_role_statements.md#role) to access a [`type`](cil_type
 
 This example will declare [`role`](cil_role_statements.md#role) and [`type`](cil_type_statements.md#type) identifiers, then associate them:
 
+```secil
     (block unconfined
         (role role)
         (type process)
         (roletype role process)
     )
+```
 
 roleattribute
 -------------
@@ -88,7 +96,9 @@ Declares a role attribute identifier in the current namespace. The identifier ma
 
 **Statement definition:**
 
+```secil
     (roleattribute roleattribute_id)
+```
 
 **Where:**
 
@@ -113,9 +123,11 @@ Declares a role attribute identifier in the current namespace. The identifier ma
 
 This example will declare a role attribute `roles.role_holder` that will have an empty set:
 
+```secil
     (block roles
         (roleattribute role_holder)
     )
+```
 
 roleattributeset
 ----------------
@@ -124,7 +136,9 @@ Allows the association of one or more previously declared [`role`](cil_role_stat
 
 **Statement definition:**
 
+```secil
     (roleattributeset roleattribute_id (role_id ... | expr ...))
+```
 
 **Where:**
 
@@ -163,6 +177,7 @@ Allows the association of one or more previously declared [`role`](cil_role_stat
 
 This example will declare three roles and two role attributes, then associate all the roles to them as shown:
 
+```secil
     (block roles
         (role role_1)
         (role role_2)
@@ -174,6 +189,7 @@ This example will declare three roles and two role attributes, then associate al
         (roleattribute role_holder_all)
         (roleattributeset role_holder_all (all))
     )
+```
 
 roleallow
 ---------
@@ -188,7 +204,9 @@ Notes:
 
 **Statement definition:**
 
+```secil
     (roleallow current_role_id new_role_id)
+```
 
 **Where:**
 
@@ -224,7 +242,9 @@ Specify a role transition from the current role to a new role when computing a c
 
 **Statement definition:**
 
+```secil
     (roletransition current_role_id target_type_id class_id new_role_id)
+```
 
 **Where:**
 
@@ -261,6 +281,7 @@ Specify a role transition from the current role to a new role when computing a c
 
 This example will authorise the `unconfined.role` to assume the `msg_filter.role` role, and then transition to that role:
 
+```secil
     (block ext_gateway
         (type process)
         (type exec)
@@ -269,6 +290,7 @@ This example will authorise the `unconfined.role` to assume the `msg_filter.role
         (roleallow unconfined.role msg_filter.role)
         (roletransition unconfined.role exec process msg_filter.role)
     )
+```
 
 rolebounds
 ----------
@@ -283,7 +305,9 @@ Notes:
 
 **Statement definition:**
 
+```secil
     (rolebounds parent_role_id child_role_id)
+```
 
 **Where:**
 
@@ -312,9 +336,11 @@ Notes:
 
 In this example the role `test` cannot have greater privileges than `unconfined.role`:
 
+```secil
     (role test)
 
     (unconfined
         (role role)
         (rolebounds role .test)
     )
+```

secilc/docs/cil_sid_statements.md

@@ -8,7 +8,9 @@ Declares a new SID identifier in the current namespace.
 
 **Statement definition:**
 
+```secil
     (sid sid_id)
+```
 
 **Where:**
 
@@ -33,9 +35,11 @@ Declares a new SID identifier in the current namespace.
 
 These examples show three [`sid`](cil_sid_statements.md#sid) declarations:
 
+```secil
     (sid kernel)
     (sid security)
     (sid igmp_packet)
+```
 
 sidorder
 --------
@@ -44,7 +48,9 @@ Defines the order of [sid](#sid)'s. This is a mandatory statement when SIDs are
 
 **Statement definition:**
 
+```secil
     (sidorder (sid_id ...))
+```
 
 **Where:**
 
@@ -69,11 +75,13 @@ Defines the order of [sid](#sid)'s. This is a mandatory statement when SIDs are
 
 This will produce an ordered list of "`kernel security unlabeled`"
 
+```secil
     (sid kernel)
     (sid security)
     (sid unlabeled)
     (sidorder (kernel security))
     (sidorder (security unlabeled))
+```
 
 sidcontext
 ----------
@@ -82,7 +90,9 @@ Associates an SELinux security [context](#context) to a previously declared [`si
 
 **Statement definition:**
 
+```secil
     (sidcontext sid_id context_id)
+```
 
 **Where:**
 
@@ -111,6 +121,7 @@ Associates an SELinux security [context](#context) to a previously declared [`si
 
 This shows two named security context examples plus an anonymous context:
 
+```secil
     ; Two named context:
     (sid kernel)
     (context kernel_context (u r process low_low))
@@ -123,3 +134,4 @@ This shows two named security context examples plus an anonymous context:
     ; An anonymous context:
     (sid unlabeled)
     (sidcontext unlabeled (u object_r ((s0) (s0))))
+```

secilc/docs/cil_type_statements.md

@@ -8,7 +8,9 @@ Declares a type identifier in the current namespace.
 
 **Statement definition:**
 
+```secil
     (type type_id)
+```
 
 **Where:**
 
@@ -33,9 +35,11 @@ Declares a type identifier in the current namespace.
 
 This example declares a type identifier `bluetooth.process`:
 
+```secil
     (block bluetooth
         (type process)
     )
+```
 
 typealias
 ---------
@@ -44,7 +48,9 @@ Declares a type alias in the current namespace.
 
 **Statement definition:**
 
+```secil
     (typealias typealias_id)
+```
 
 **Where:**
 
@@ -76,7 +82,9 @@ Associates a previously declared [`typealias`](cil_type_statements.md#typealias)
 
 **Statement definition:**
 
+```secil
     (typealiasactual typealias_id type_id)
+```
 
 **Where:**
 
@@ -105,12 +113,14 @@ Associates a previously declared [`typealias`](cil_type_statements.md#typealias)
 
 This example will alias `unconfined.process` as `unconfined_t` in the global namespace:
 
+```secil
     (typealias unconfined_t)
     (typealiasactual unconfined_t unconfined.process)
 
     (block unconfined
         (type process)
     )
+```
 
 typeattribute
 -------------
@@ -119,7 +129,9 @@ Declares a type attribute identifier in the current namespace. The identifier ma
 
 **Statement definition:**
 
+```secil
     (typeattribute typeattribute_id)
+```
 
 **Where:**
 
@@ -144,7 +156,9 @@ Declares a type attribute identifier in the current namespace. The identifier ma
 
 This example declares a type attribute `domain` in global namespace that will have an empty set:
 
+```secil
     (typeattribute domain)
+```
 
 typeattributeset
 ----------------
@@ -153,7 +167,9 @@ Allows the association of one or more previously declared [`type`](cil_type_stat
 
 **Statement definition:**
 
+```secil
     (typeattributeset typeattribute_id (type_id ... | expr ...))
+```
 
 **Where:**
 
@@ -192,12 +208,15 @@ Allows the association of one or more previously declared [`type`](cil_type_stat
 
 This example will take all the policy types and exclude those in `appdomain`. It is equivalent to `~appdomain` in the kernel policy language.
 
+```secil
     (typeattribute not_in_appdomain)
 
     (typeattributeset not_in_appdomain (not (appdomain)))
+```
 
 This example is equivalent to `{ domain -kernel.process -ueventd.process -init.process }` in the kernel policy language:
 
+```secil
     (typeattribute na_kernel_or_ueventd_or_init_in_domain)
 
     (typeattributeset na_kernel_or_ueventd_or_init_in_domain
@@ -212,6 +231,7 @@ This example is equivalent to `{ domain -kernel.process -ueventd.process -init.p
             (not (init.process))
         )
     )
+```
 
 expandtypeattribute
 -------------------
@@ -229,7 +249,9 @@ option cause the rules involving the type attribute to be expanded.
 
 **Statement definition:**
 
+```secil
     (expandtypeattribute typeattribute_id expand_value)
+```
 
 **Where:**
 
@@ -258,11 +280,15 @@ option cause the rules involving the type attribute to be expanded.
 
 This example uses the expandtypeattribute statement to forcibly expand a previously declared `domain` type attribute.
 
+```secil
     (expandtypeattribute domain true)
+```
 
 This example uses the expandtypeattribute statement to not expand previously declared `file_type` and `port_type` type attributes regardless of compiler defaults.
 
+```secil
     (expandtypeattribute (file_type port_type) false)
+```
 
 typebounds
 ----------
@@ -273,7 +299,9 @@ Requires kernel 2.6.28 and above to control the security context associated to t
 
 **Statement definition:**
 
+```secil
     (typebounds parent_type_id child_type_id)
+```
 
 **Where:**
 
@@ -302,6 +330,7 @@ Requires kernel 2.6.28 and above to control the security context associated to t
 
 In this example the `httpd.child.process` cannot have `file (write)` due to lack of permissions on `httpd.process` which is the parent. It means the child domain will always have equal or less privileges than the parent:
 
+```secil
     (class file (getattr read write))
 
     (block httpd
@@ -320,6 +349,7 @@ In this example the `httpd.child.process` cannot have `file (write)` due to lack
             (allow process httpd.object (file (read write)))
         )
     )
+```
 
 typechange
 ----------
@@ -328,7 +358,9 @@ The type change rule is used to define a different label of an object for usersp
 
 **Statement definition:**
 
+```secil
     (typechange source_type_id target_type_id class_id change_type_id)
+```
 
 **Where:**
 
@@ -371,6 +403,7 @@ the function will return a context of:
 
 `    unconfined.object:object_r:unconfined.change_label:s0`
 
+```secil
     (class file (getattr read write))
 
     (block unconfined
@@ -380,6 +413,7 @@ the function will return a context of:
 
         (typechange object object file change_label)
     )
+```
 
 typemember
 ----------
@@ -388,7 +422,9 @@ The type member rule is used to define a new polyinstantiated label of an object
 
 **Statement definition:**
 
+```secil
     (typemember source_type_id target_type_id class_id member_type_id)
+```
 
 **Where:**
 
@@ -431,6 +467,7 @@ the function will return a context of:
 
 `    unconfined.object:object_r:unconfined.member_label:s0`
 
+```secil
     (class file (getattr read write))
 
     (block unconfined
@@ -440,6 +477,7 @@ the function will return a context of:
 
         (typemember object object file member_label)
     )
+```
 
 typetransition
 --------------
@@ -448,7 +486,9 @@ The type transition rule specifies the labeling and object creation allowed betw
 
 **Statement definition:**
 
+```secil
     (typetransition source_type_id target_type_id class_id [object_name] default_type_id)
+```
 
 **Where:**
 
@@ -489,29 +529,35 @@ The type transition rule specifies the labeling and object creation allowed betw
 
 This example shows a process transition rule with its supporting [`allow`](cil_access_vector_rules.md#allow) rule:
 
+```secil
     (macro domain_auto_trans ((type ARG1) (type ARG2) (type ARG3))
         ; Allow the necessary permissions.
         (call domain_trans (ARG1 ARG2 ARG3))
         ; Make the transition occur by default.
         (typetransition ARG1 ARG2 process ARG3)
     )
+```
 
 This example shows a file object transition rule with its supporting [`allow`](cil_access_vector_rules.md#allow) rule:
 
+```secil
     (macro tmpfs_domain ((type ARG1))
         (type tmpfs)
         (typeattributeset file_type (tmpfs))
         (typetransition ARG1 file.tmpfs file tmpfs)
         (allow ARG1 tmpfs (file (read write execute execmod)))
     )
+```
 
 This example shows the 'name transition' rule with its supporting [`allow`](cil_access_vector_rules.md#allow) rule:
 
+```secil
     (macro write_klog ((type ARG1))
         (typetransition ARG1 device.device chr_file "__kmsg__" device.klog_device)
         (allow ARG1 device.klog_device (chr_file (create open write unlink)))
         (allow ARG1 device.device (dir (write add_name remove_name)))
     )
+```
 
 typepermissive
 --------------
@@ -520,7 +566,9 @@ Policy database version 23 introduced the permissive statement to allow the name
 
 **Statement definition:**
 
+```secil
     (typepermissive source_type_id)
+```
 
 **Where:**
 
@@ -545,9 +593,11 @@ Policy database version 23 introduced the permissive statement to allow the name
 
 This example will allow SELinux to run the `healthd.process` domain in permissive mode even when enforcing is enabled:
 
+```secil
     (block healthd
         (type process)
         (typepermissive process)
 
         (allow ...)
     )
+```

secilc/docs/cil_user_statements.md

@@ -8,7 +8,9 @@ Declares an SELinux user identifier in the current namespace.
 
 **Statement definition:**
 
+```secil
     (user user_id)
+```
 
 **Where:**
 
@@ -33,9 +35,11 @@ Declares an SELinux user identifier in the current namespace.
 
 This will declare an SELinux user as `unconfined.user`:
 
+```secil
     (block unconfined
         (user user)
     )
+```
 
 userrole
 --------
@@ -44,7 +48,9 @@ Associates a previously declared [`user`](cil_user_statements.md#user) identifie
 
 **Statement definition:**
 
+```secil
     (userrole user_id role_id)
+```
 
 **Where:**
 
@@ -73,11 +79,13 @@ Associates a previously declared [`user`](cil_user_statements.md#user) identifie
 
 This example will associate `unconfined.user` to `unconfined.role`:
 
+```secil
     (block unconfined
         (user user)
         (role role)
         (userrole user role)
     )
+```
 
 userattribute
 -------------
@@ -86,7 +94,9 @@ Declares a user attribute identifier in the current namespace. The identifier ma
 
 **Statement definition:**
 
+```secil
     (userattribute userattribute_id)
+```
 
 **Where:**
 
@@ -111,9 +121,11 @@ Declares a user attribute identifier in the current namespace. The identifier ma
 
 This example will declare a user attribute `users.user_holder` that will have an empty set:
 
+```secil
     (block users
         (userattribute user_holder)
     )
+```
 
 userattributeset
 ----------------
@@ -122,7 +134,9 @@ Allows the association of one or more previously declared [`user`](cil_user_stat
 
 **Statement definition:**
 
+```secil
     (userattributeset userattribute_id (user_id ... | expr ...))
+```
 
 **Where:**
 
@@ -161,6 +175,7 @@ Allows the association of one or more previously declared [`user`](cil_user_stat
 
 This example will declare three users and two user attributes, then associate all the users to them as shown:
 
+```secil
     (block users
         (user user_1)
         (user user_2)
@@ -172,6 +187,7 @@ This example will declare three users and two user attributes, then associate al
         (userattribute user_holder_all)
         (userattributeset user_holder_all (all))
     )
+```
 
 userlevel
 ---------
@@ -180,7 +196,9 @@ Associates a previously declared [`user`](cil_user_statements.md#user) identifie
 
 **Statement definition:**
 
+```secil
     (userlevel user_id level_id)
+```
 
 **Where:**
 
@@ -209,6 +227,7 @@ Associates a previously declared [`user`](cil_user_statements.md#user) identifie
 
 This example will associate `unconfined.user` with a named [`level`](cil_mls_labeling_statements.md#level) of `systemlow`:
 
+```secil
     (sensitivity s0)
     (level systemlow (s0))
 
@@ -218,6 +237,7 @@ This example will associate `unconfined.user` with a named [`level`](cil_mls_lab
         ; An anonymous example:
         ;(userlevel user (s0))
     )
+```
 
 userrange
 ---------
@@ -226,7 +246,9 @@ Associates a previously declared [`user`](cil_user_statements.md#user) identifie
 
 **Statement definition:**
 
+```secil
     (userrange user_id levelrange_id)
+```
 
 **Where:**
 
@@ -255,6 +277,7 @@ Associates a previously declared [`user`](cil_user_statements.md#user) identifie
 
 This example will associate `unconfined.user` with a named [`levelrange`](cil_mls_labeling_statements.md#levelrange) of `low_high`, other anonymous examples are also shown:
 
+```secil
     (category c0)
     (category c1)
     (categoryorder (c0 c1))
@@ -277,6 +300,7 @@ This example will associate `unconfined.user` with a named [`levelrange`](cil_ml
         ;(userrange user (systemLow (s0 (c0 c1))))
         ;(userrange user ((s0) (s0 (c0 c1))))
     )
+```
 
 userbounds
 ----------
@@ -291,7 +315,9 @@ Notes:
 
 **Statement definition:**
 
+```secil
     (userbounds parent_user_id child_user_id)
+```
 
 **Where:**
 
@@ -320,12 +346,14 @@ Notes:
 
 The user `test` cannot have greater privileges than `unconfined.user`:
 
+```secil
     (user test)
 
     (unconfined
         (user user)
         (userbounds user .test)
     )
+```
 
 userprefix
 ----------
@@ -334,7 +362,9 @@ Declare a user prefix that will be replaced by the file labeling utilities descr
 
 **Statement definition:**
 
+```secil
     (userprefix user_id prefix)
+```
 
 **Where:**
 
@@ -363,10 +393,12 @@ Declare a user prefix that will be replaced by the file labeling utilities descr
 
 This example will associate `unconfined.admin` user with a prefix of "[`user`](cil_user_statements.md#user)":
 
+```secil
     (block unconfined
-        (user admin
+        (user admin)
         (userprefix admin user)
     )
+```
 
 selinuxuser
 -----------
@@ -375,7 +407,9 @@ Associates a GNU/Linux user to a previously declared [`user`](cil_user_statement
 
 **Statement definition:**
 
+```secil
     (selinuxuser user_name user_id userrange_id)
+```
 
 **Where:**
 
@@ -408,10 +442,12 @@ Associates a GNU/Linux user to a previously declared [`user`](cil_user_statement
 
 This example will associate `unconfined.admin` user with a GNU / Linux user "`admin_1`":
 
+```secil
     (block unconfined
         (user admin)
         (selinuxuser admin_1 admin low_low)
     )
+```
 
 selinuxuserdefault
 ------------------
@@ -420,7 +456,9 @@ Declares the default SELinux user. Only one [`selinuxuserdefault`](cil_user_stat
 
 **Statement definition:**
 
+```secil
     (selinuxuserdefault user_id userrange_id)
+```
 
 **Where:**
 
@@ -449,7 +487,9 @@ Declares the default SELinux user. Only one [`selinuxuserdefault`](cil_user_stat
 
 This example will define the `unconfined.user` as the default SELinux user:
 
+```secil
     (block unconfined
         (user user)
         (selinuxuserdefault user low_low)
     )
+```

secilc/docs/cil_xen_statements.md

@@ -12,7 +12,9 @@ Label i/o memory. This may be a single memory location or a range.
 
 **Statement definition:**
 
+```secil
     (iomemcon mem_addr|(mem_low mem_high) context_id)
+```
 
 **Where:**
 
@@ -43,7 +45,9 @@ Label i/o memory. This may be a single memory location or a range.
 
 An anonymous context for a memory address range of `0xfebe0-0xfebff`:
 
+```secil
     (iomemcon (1043424 1043455) (unconfined.user object_r unconfined.object low_low))
+```
 
 ioportcon
 ---------
@@ -52,7 +56,9 @@ Label i/o ports. This may be a single port or a range.
 
 **Statement definition:**
 
+```secil
     (ioportcon port|(port_low port_high) context_id)
+```
 
 **Where:**
 
@@ -83,7 +89,9 @@ Label i/o ports. This may be a single port or a range.
 
 An anonymous context for a single port of :`0xecc0`:
 
+```secil
     (ioportcon 60608 (unconfined.user object_r unconfined.object low_low))
+```
 
 pcidevicecon
 ------------
@@ -92,7 +100,9 @@ Label a PCI device.
 
 **Statement definition:**
 
+```secil
     (pcidevicecon device context_id)
+```
 
 **Where:**
 
@@ -121,7 +131,9 @@ Label a PCI device.
 
 An anonymous context for a pci device address of `0xc800`:
 
+```secil
     (pcidevicecon 51200 (unconfined.user object_r unconfined.object low_low))
+```
 
 pirqcon
 -------
@@ -130,7 +142,9 @@ Label an interrupt level.
 
 **Statement definition:**
 
+```secil
     (pirqcon irq_level context_id)
+```
 
 **Where:**
 
@@ -159,7 +173,9 @@ Label an interrupt level.
 
 An anonymous context for IRQ 33:
 
+```secil
     (pirqcon 33 (unconfined.user object_r unconfined.object low_low))
+```
 
 devicetreecon
 -------------
@@ -168,7 +184,9 @@ Label device tree nodes.
 
 **Statement definition:**
 
+```secil
     (devicetreecon path context_id)
+```
 
 **Where:**
 
@@ -197,4 +215,6 @@ Label device tree nodes.
 
 An anonymous context for the specified path:
 
+```secil
     (devicetreecon "/this is/a/path" (unconfined.user object_r unconfined.object low_low))
+```