Remove links from user docs to contributor docs

Author: chrisseaton

README.md

@@ -33,10 +33,6 @@ There are three ways to install TruffleRuby:
 
 You can use `gem` to install Gems as normal.
 
-You can also build TruffleRuby from source, see the
-[building instructions](doc/contributor/workflow.md), and using
-[Docker](doc/contributor/docker.md).
-
 Please report any issue you might find on [GitHub](https://github.com/oracle/truffleruby/issues).
 
 ## Aim
@@ -58,18 +54,18 @@ important to understand the different configurations of TruffleRuby, as each has
 different capabilities and performance characteristics. You should pick the
 execution mode that is appropriate for your application.
 
-TruffleRuby by default runs in the *native*
-configuration. In this configuration, TruffleRuby is ahead-of-time compiled to a
-standalone native executable. This means that you don't need a JVM installed on
-your system to use it. The advantage of the native configuration is that it
-[starts about as fast as MRI](doc/contributor/native-image.md), it may use less memory,
-and it becomes fast in less time. The disadvantage of the native configuration
-is that you can't use Java tools like VisualVM, you can't use Java
-interoperability, and *peak performance may be lower than on the JVM*. The
-native configuration is used by default, but you can also request it using
-`--native`. To use polyglot programming with the *native* configuration, you
-need to use the `--polyglot` flag. To check you are using the *native*
-configuration, `ruby --version` should mention `Native`.
+TruffleRuby by default runs in the *native* configuration. In this
+configuration, TruffleRuby is ahead-of-time compiled to a standalone native
+executable. This means that you don't need a JVM installed on your system to
+use it. The advantage of the native configuration is that it starts about as
+fast as MRI, it may use less memory, and it becomes fast in less time. The
+disadvantage of the native configuration is that you can't use Java tools like
+VisualVM, you can't use Java interoperability, and *peak performance may be
+lower than on the JVM*. The native configuration is used by default, but you
+can also request it using `--native`. To use polyglot programming with the
+*native* configuration, you need to use the `--polyglot` flag. To check you
+are using the *native* configuration, `ruby --version` should mention
+`Native`.
 
 TruffleRuby can also be used in the *JVM* configuration, where it runs as a
 normal Java application on the JVM, as any other Java application would. The
@@ -150,8 +146,6 @@ should read our [migration guide](doc/user/jruby-migration.md).
 ## Documentation
 
 Extensive documentation is available in [`doc`](doc).
-[`doc/user`](doc/user) documents how to use TruffleRuby and
-[`doc/contributor`](doc/contributor) documents how to develop TruffleRuby.
 
 ## Contact
 

doc/user/deploying.md

@@ -11,17 +11,17 @@ important to understand the different configurations of TruffleRuby, as each has
 different capabilities and performance characteristics. You should pick the
 execution mode that is appropriate for your application.
 
-When distributed as part of GraalVM, TruffleRuby by default runs in the *native*
-configuration. In this configuration, TruffleRuby is ahead-of-time compiled to a
-standalone native executable. This means that you don't need a JVM installed on
-your system to use it. The advantage of the native configuration is that it
-[starts about as fast as MRI](../contributor/native-image.md), it may use less memory,
-and it becomes fast in less time than the *JVM* configuration. The disadvantage
-of the native configuration is that you can't use Java tools like VisualVM, you
-can't use Java interoperability, and *peak performance may be lower than on the
-JVM*. The native configuration is used by default, but you can also request it
-using `--native`. To use polyglot programming with the *native* configuration,
-you need to use the `--polyglot` flag.
+When distributed as part of GraalVM, TruffleRuby by default runs in the
+*native* configuration. In this configuration, TruffleRuby is ahead-of-time
+compiled to a standalone native executable. This means that you don't need a
+JVM installed on your system to use it. The advantage of the native
+configuration is that it starts about as fast as MRI, it may use less memory,
+and it becomes fast in less time than the *JVM* configuration. The
+disadvantage of the native configuration is that you can't use Java tools like
+VisualVM, you can't use Java interoperability, and *peak performance may be
+lower than on the JVM*. The native configuration is used by default, but you
+can also request it using `--native`. To use polyglot programming with the
+*native* configuration, you need to use the `--polyglot` flag.
 
 TruffleRuby can also be used in the *JVM* configuration, where it runs as a
 normal Java application on the JVM, as any other Java application would. The

doc/user/polyglot.md

@@ -12,11 +12,6 @@ If you are using the native configuration, you will need to use the `--polyglot`
 flag to get access to other languages. The JVM configuration automatically has
 access to other languages.
 
-There is also [additional documentation](../contributor/interop.md) that
-describes in more depth how polyglot programming in TruffleRuby is implemented
-using the Truffle Language Implementation Framework interop API, and exactly
-how Ruby is matched to this API.
-
 * [Loading code written in foreign languages](#loading-code-written-in-foreign-languages)
 * [Exporting Ruby objects to foreign languages](#exporting-ruby-objects-to-foreign-languages)
 * [Importing foreign objects to Ruby](#importing-foreign-objects-to-ruby)