diff --git a/docs/addingparticles.md b/docs/addingparticles.md
index 57ceb6a2d..70a184ff8 100644
--- a/docs/addingparticles.md
+++ b/docs/addingparticles.md
@@ -1,7 +1,7 @@
 # Adding particles
 Once you've created a [simulation object](simulation.md), you can add particles to it. 
 REBOUND supports several different ways to do that. 
-Also check out the [discussion on manipulating particles](manipulations.md).
+Also check out the [discussion on particle operators](particleoperators.md).
 
 ## Adding particles manually
 One way to add a particle to a simulation is to first manually create a particle object, then calling a function to add the particle to the simulation.
diff --git a/docs/chaos.md b/docs/chaos.md
index 60b3f2420..bee1dc329 100644
--- a/docs/chaos.md
+++ b/docs/chaos.md
@@ -21,7 +21,7 @@ Then, initialize the variational particles and MEGNO variables with
 REBOUND uses random numbers to initialize the variational particles.
 The initial seed is chosen based on the current time and the process id. 
 This ensures the seed if different every time you run the simulation.
-See the discussion on [random sampling](randomsampling.md) for more details.
+See the discussion on [random sampling](c_randomsamplingfunctions.md) for more details.
 
 If you want to have reproducible result, you can specify the seed manually:
 === "C"
diff --git a/docs/index.md b/docs/index.md
index d04e0c234..7a5104d5c 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -60,7 +60,9 @@ There are several papers describing the functionality of REBOUND.
 
 ## Acknowledgments
 
-If you use this code or parts of this code for results presented in a scientific publication, please send us a copy of your paper so that we can keep track of all publications that made use of the code. We would greatly appreciate a citation as well. The simplest way to find the citations relevant to the specific setup of your REBOUND simulation is: 
+If you use this code or parts of this code for results presented in a scientific publication, we would greatly appreciate a citation.
+please cite REBOUND.
+The simplest way to find the citations relevant to the specific setup of your REBOUND simulation is: 
 
 ```python
 sim = rebound.Simulation()
@@ -68,6 +70,8 @@ sim = rebound.Simulation()
 sim.cite()
 ```
 
+!!! Info
+    When you cite one of the REBOUND papers, your paper will receive an automatic shout-out from the [REBOUND Citation Bot](https://twitter.com/reboundbot). 
 
 ## License
 
diff --git a/docs/quickstart.md b/docs/quickstart.md
index 965858d7c..76b2accd7 100644
--- a/docs/quickstart.md
+++ b/docs/quickstart.md
@@ -141,5 +141,12 @@ into a terminal window while you're in the `examples/simplest/` directory. Then
 ```
 
 ## Where to go from here
-To learn more about how to use REBOUND with C, have a look at the examples in the `examples/` directory. You might also want to have a look at the `rebound.h` file in the `src/` directory which contains the API specifications. Last but not least, REBOUND is open source. If you want to know how something works, you can just look at the source code. And of course, you are welcome to [open an issue](https://github.com/hannorein/rebound/issues) on Github or e-mail any of the [contributors](/#contributors) with questions. We'll do our best to answer them quickly.
+In addition to reading the remaining sections in the documentation, you can learn most about REBOUND by looking at some of the [example problems](examples.md). 
+The C examples are located in the `examples/` directory. 
+The python and iPython examples are located in the `python_examples/` and `ipython_examples/` directories respectively. 
+
+You might also want to have a look at the `rebound.h` file in the `src/` directory which contains the precise function prototypes and structure definitions.
+
+If you run into a problem or can't find an answer in this documentation, [open an issue](https://github.com/hannorein/rebound/issues) on Github or e-mail one of the [contributors](/#contributors). 
+We'll do our best to help you quickly.