Issues on the Android TroubleShooting page

== Note: Constraints,
The value returned by LogLevel.getValue() is not the Android log level. Do not use this API call.
should read:
The value returned by LogLevel.getValue() is not useful. It is not the Android log level.

== Introduction: Console based logging
Console based logging is often used to facilitate troubleshooting during development.
should read:
Console based logging logs to Android's logcat logger and is the first choice for troubleshooting during development.

... fine-tune diagnostic output to suit specific debug scenarios, without interfering with any logging required by Couchbase Support for the investigation of issues.
should read:
fine-tune diagnostic output to suit specific debug scenarios and capture them for Couchbase Support for the investigation of issues

== Console based Logging
...Changes to console logging are independent of file logging, so you can make change without compromising any files logging streams. It is enabled by default.
should read:
Console logging is enabled by default.

You will primarily use log.getConsole() and ConsoleLogger to control console logging.
should read:
You will primarily use Database.log.getConsole() to get the ConsoleLogger used to control console logging.

Tip: It can often be more effective to just use the Console logger (which logs to logcat).
should be deleted

== Example 1. Change Console Logging Settings
1. Define the required domain;
should read
1. Set the domains to be logged

== File based logging
You will primarily use log.getFile() and FileLogger to control file-based logging.
should read:
You will primarily use Database.log.getFile() and FileLogger to control file-based logging.

== File based Logging: Configuration
With file based logging you can also use the LogFileConfiguration(String directory) class’s properties to specify the:
should read
With file based logging you can also use the LogFileConfiguration class’s properties to specify the:

Note that the use of Database.setLogLevel() is now deprecated. Further, you can no longer set a log level for a specific domain.
This is true of ALL loggers, not just file base logging. This note should be pulled up to the top level

== Decoding binary logs
Example 5 is missing a step: the zip file must be exploded

== Logging functionality prior to release 2.5
This section is both obsolete and quite incorrect. It should be removed.