DOC-9636 gardening

Mostly minor formatting.

Removed 4th column, as it leads to odd line-wrapping,
and seems to be largely redundant (the Common Flag is
*always* Binary, except if an error is thrown)

Author: osfameron

modules/howtos/pages/transcoders-nonjson.adoc

@@ -143,44 +143,40 @@ include::example$Transcoding.cs[tag=string,indent=0]
 
 === RawBinaryTranscoder
 The RawBinaryTranscoder provides the ability for the user to explicitly store and retrieve raw byte data to Couchbase.
-The transcoder does not perform any form of real transcoding, and does not take a serializer, but rather passes the data through and assigns the appropriate binary Common Flag.
+The transcoder does not perform any form of real transcoding, and does not take a serializer, but rather passes the data through and assigns the appropriate `Binary` Common Flag (except in the case of an exception).
 
-[cols="4", options="header"]
+[cols="3", options="header"]
 |===
 |Item
 |Encoding Result
 |Decoding Result
-|Common Flag
 
 |String
 |InvalidArgumentException
 |InvalidArgumentException
-|-
 
 |byte[]
 |Passthrough
 |Passthrough
-|Binary
 
 |Memory<byte>
-|Passthrough (≥ 3.2.6)
+|Passthrough +
+(from 3.2.6)
 |InvalidArgumentException
-|Binary
 
 |ReadOnlyMemory<byte>
-|Passthrough (≥ 3.2.6)
+|Passthrough +
+(from 3.2.6)
 |InvalidArgumentException
-|Binary
 
 |IMemoryOwner<byte>
 |InvalidArgumentException
-|Passthrough (≥ 3.2.6)
-|Binary
+|Passthrough +
+(from 3.2.6)
 
 |Other `Object`
 |InvalidArgumentException
 |InvalidArgumentException
-|-
 |===
 
 Here’s an example of using the `RawBinaryTranscoder`:
@@ -190,9 +186,8 @@ Here’s an example of using the `RawBinaryTranscoder`:
 include::example$Transcoding.cs[tag=binary,indent=0]
 ----
 
-From version 3.2.6, the `RawBinaryTranscoder` will accept `Memory<byte>` and `ReadOnlyMemory<byte>` inputs
-and can return `IMemoryOwner<byte>` outputs. Using these types may improve performace by not allocating
-large, temporary `byte[]` arrays on the heap.
+From version 3.2.6, the `RawBinaryTranscoder` will accept `Memory<byte>` and `ReadOnlyMemory<byte>` inputs and can return `IMemoryOwner<byte>` outputs.
+Using these types may improve performance by not allocating large, temporary `byte[]` arrays on the heap.
 
 [source,csharp]
 ----