Fix inline code

Author: ben221199

bip-0040.mediawiki

@@ -36,9 +36,9 @@ Later in 2012, Marek Palatinus introduced Stratum also for mining pools: The Str
 
 Stratum leverages [https://www.jsonrpc.org/ JSON-RPC]. Both versions 1.0 and 2.0 are allowed. Rules of that version apply accordingly.
 
-Additionally, it is a convention to give all Stratum methods in the `method` property a name in the following form: `<service>.<method>`, where `<service>` is allowed to have dots and `<method>` isn't. For example, the the value `blockchain.block.subscribe`.
+Additionally, it is a convention to give all Stratum methods in the <code>method</code> property a name in the following form: <code><service>.<method></code>, where <code><service></code> is allowed to have dots and <code><method></code> isn't. For example, the the value <code>blockchain.block.subscribe</code>.
 
-Note: In JSON-RPC 1.0, the `param` property is an array, so everything should be passed in the right order. In JSON-RPC 2.0, also named parameters are allowed. In that case, the parameter names that are documented should be used. If not, the method can fail. It is maybe also possible that a specific method (or server) only does support `params` being an array, because it doesn't know how to handle the named ones, even if it supports JSON-RPC 2.0.
+Note: In JSON-RPC 1.0, the <code>param</code> property is an array, so everything should be passed in the right order. In JSON-RPC 2.0, also named parameters are allowed. In that case, the parameter names that are documented should be used. If not, the method can fail. It is maybe also possible that a specific method (or server) only does support <code>params</code> being an array, because it doesn't know how to handle the named ones, even if it supports JSON-RPC 2.0.
 
 ==Specification: Transport Protocols==