[[ Java FFI ]] Fix styling in release notes

livecodeali · livecodeali · commit cbd0834b4ba6 · 2017-02-27T16:02:03.000Z
diff --git a/docs/lcb/notes/feature-java.md b/docs/lcb/notes/feature-java.md
@@ -3,13 +3,13 @@
 ## Java utilities
 
 There is now a utility library for manipulating java objects. It contains
-a type JObject which wraps a java object, some type conversion operations:
+a type `JObject` which wraps a Java object, some type conversion operations:
 
-* StringFromJString - converts a Java string to an LCB String
-* StringToJString - converts an LCB String to a Java string
-* DataFromJByteArray - converts a Java byte array to LCB Data
-* DataToJByteArray - converts LCB Data to a Java byte array
+* `StringFromJString` - converts a Java string to an LCB String
+* `StringToJString` - converts an LCB String to a Java string
+* `DataFromJByteArray` - converts a Java byte array to LCB Data
+* `DataToJByteArray` - converts LCB Data to a Java byte array
 
 and a utility for determining the class of a given java object:
 
-* GetJavaClassName - return an LCB String containing the class name of the given JObject
+* `GetJavaClassName` - return an LCB String containing the class name of the given `JObject`
diff --git a/docs/notes/feature-java_ffi_bindings.md b/docs/notes/feature-java_ffi_bindings.md
@@ -22,12 +22,12 @@ when calling the JNI.
 
 *calling* specifies the calling convention which can be one of:
 
- - instance
- - static
- - nonvirtual
+ - `instance`
+ - `static`
+ - `nonvirtual`
  
- Instance and nonvirtual calling conventions require instances of the given
-java class, so the foreign handler declaration will always require a Java
+Instance and nonvirtual calling conventions require instances of the given
+Java class, so the foreign handler declaration will always require a Java
 object parameter.
 
 ### Examples
