diff --git a/README.md b/README.md
index ae034f7eb..f09334c06 100644
--- a/README.md
+++ b/README.md
@@ -200,6 +200,33 @@ Check the corresponding driver's READMEs to know the list of capabilities and fe
You could find much more code examples by checking client's
[unit and integration tests](src/test/java/io/appium/java_client).
+## Troubleshooting
+
+### InaccessibleObjectException is thrown in runtime if Java 16+ is used
+
+Appium Java client uses reflective access to private members of other modules
+to ensure proper functionality of several features, like Page Object model.
+If you get a runtime exception and `InaccessibleObjectException` is present in
+the stacktrace, and your Java runtime is at version 16 or higher, then consider following
+[Oracle's tutorial](https://docs.oracle.com/en/java/javase/16/migrate/migrating-jdk-8-later-jdk-releases.html#GUID-7BB28E4D-99B3-4078-BDC4-FC24180CE82B)
+and/or checking [existing issues](https://github.com/appium/java-client/search?q=InaccessibleObjectException&type=issues)
+for possible solutions. Basically, the idea there would be to explicitly allow
+access for particular modules using `--add-exports/--add-opens` command line arguments.
+
+Another possible, but weakly advised solution, would be to downgrade Java to
+version 15 or lower.
+
+### Issues related to environment variables presence or to their values
+
+Such issues are usually the case when Appium server is started directly from your
+framework code rather than run separately by a script or manually. Depending
+on the way the server process is started it may or may not inherit the currently
+active shell environment. That is why you may still receive errors about variables
+presence even though these variables ar actually defined for your command line interpreter.
+Again, there is no universal solution to that, as there are many ways to spin up a new
+server process. Consider checking the [Appium Environment Troubleshooting](docs/environment.md)
+document for more information on how to debug and fix process environment issues.
+
## Changelog
*8.2.1*
- **[ENHANCEMENTS]**
diff --git a/docs/Installing-the-project.md b/docs/Installing-the-project.md
deleted file mode 100644
index 8417f9f79..000000000
--- a/docs/Installing-the-project.md
+++ /dev/null
@@ -1,91 +0,0 @@
-# Requirements
-
-Firstly you should install appium server. [Appium getting started](https://appium.io/docs/en/about-appium/getting-started/). The latest server version is recommended.
-
-Since version 5.x there many features based on Java 8. So we recommend to install JDK SE 8 and provide that source compatibility.
-
-# Maven
-
-Add the following to pom.xml:
-
-```
-
- io.appium
- java-client
- ${version.you.require}
- test
-
-```
-
-If you haven't already, change the Java version:
-```
-
- 1.8
- 1.8
-
-```
-
-If it is necessary to change the version of Selenium then you can configure pom.xml like following:
-
-```
-
- io.appium
- java-client
- ${version.you.require}
- test
-
-
- org.seleniumhq.selenium
- selenium-java
-
-
-
-
-
- org.seleniumhq.selenium
- selenium-java
- ${selenium.version.you.require}
-
-```
-
-# Gradle
-
-Add the following to build.gradle:
-
-```
-repositories {
- jcenter()
- maven {
- url "http://repo.maven.apache.org/maven2"
- }
-}
-
-dependencies {
- ...
- testCompile group: 'io.appium', name: 'java-client', version: requiredVersion
- ...
-}
-```
-
-If it is necessary to change the version of Selenium then you can configure build.gradle like the sample below:
-
-```
-repositories {
- jcenter()
- maven {
- url "http://repo.maven.apache.org/maven2"
- }
-}
-
-dependencies {
- ...
- testCompile group: 'io.appium', name: 'java-client', version: requiredVersion {
- exclude module: 'selenium-java'
- }
-
- testCompile group: 'org.seleniumhq.selenium', name: 'selenium-java',
- version: requiredSeleniumVersion
- ...
-}
-```
-