diff --git a/wiki/Quickstart.wiki b/wiki/Quickstart.wiki
index a54fa2d5..20c1c088 100644
--- a/wiki/Quickstart.wiki
+++ b/wiki/Quickstart.wiki
@@ -4,23 +4,25 @@
 
 This is the quickstart guide; for full installation instructions, refer to the [http://pf.itd.nrl.navy.mil/core/core-html/install.html CORE manual].
 
-CORE 4.4 packages are available for Ubuntu 12.04 (precise) or 11.10 (oneiric), Fedora 17 or 16, and rhel6. If you want to run a different Linux distribution, make sure the kernel is at least 2.6.27 to support [Namespaces network namespaces]. Released packages are generally more stable and tested to work properly on the given platform. See the [Upgrading upgrading] page for help choosing a release or for upgrade instructions.
+CORE 4.5 packages are available for Ubuntu 12.04 (precise) or 12.10 (quantal), Fedora 17 or 18, and rhel6. If you want to run a different Linux distribution, make sure the kernel is at least 2.6.27 to support [Namespaces network namespaces]. Released packages are generally more stable and tested to work properly on the given platform. See the [Upgrading upgrading] page for help choosing a release or for upgrade instructions.
 
 == Step 1. Install CORE package ==
 
 Get the Ubuntu (deb) or Fedora (rpm) package for your architecture (64-bit or 32-bit) from here:<br>
-[http://downloads.pf.itd.nrl.navy.mil/core/packages/4.4/]
+[http://downloads.pf.itd.nrl.navy.mil/core/packages/4.5/]
 
 Use your package manager to automatically install dependencies:<br>
 {{{
   # Ubuntu users (specify entire path)
-  software-center /home/user/Downloads/core_4.4-0ubuntu1_precise_amd64.deb
+  software-center /home/user/Downloads/core-daemon_4.5-0ubuntu1_precise_amd64.deb
+  software-center /home/user/Downloads/core-gui_4.5-0ubuntu1_precise_all.deb
   # Fedora users
   su
-  yum localinstall core-4.4-1.fc17.x86_64.rpm --nogpgcheck
+  yum localinstall core-daemon-4.5-1.fc18.x86_64.rpm --nogpgcheck
+  yum localinstall core-gui-4.5-1.fc18.noarch.rpm --nogpgcheck
 }}}
 
-Virtual networks usually require routing software. CORE automatically builds configs for the [http://www.quagga.net Quagga] routing suite. For wireless networks, CORE will generate OSPF MDR configs, a modified version of Quagga available from [http://cs.itd.nrl.navy.mil/work/ospf-manet/ here].
+Virtual networks usually require routing software. CORE automatically builds configs for the [http://www.quagga.net Quagga] routing suite. For wireless networks, CORE will generate OSPF MDR configs, for a modified version of Quagga available from [http://cs.itd.nrl.navy.mil/work/ospf-manet/ here].
 {{{
   # Ubuntu - vanilla Quagga
   sudo apt-get install quagga
@@ -34,17 +36,18 @@ Virtual networks usually require routing software. CORE automatically builds con
   yum localinstall quagga-0.99.21mr2.2-1.fc16.x86_64.rpm --nogpgcheck
 }}}
 
-*Fedora users:* check the full [http://pf.itd.nrl.navy.mil/core/core-html/install.html#installing-from-packages-on-fedora-centos installation instructions], you need to also disable SELINUX, sandbox, and iptables.
+*Fedora users:* check the full [http://pf.itd.nrl.navy.mil/core/core-html/install.html#installing-from-packages-on-fedora-centos installation instructions], you need to also disable (or configure) SELINUX, sandbox, and iptables.
 
 == Step 2. Start the CORE daemon ==
 {{{
   # for Ubuntu/CentOS
   sudo /etc/init.d/core start
   # for Fedora
+  su
   systemctl start core-emulator.service
 }}}
 
-To view the CORE daemon log file, look at `/var/log/coredpy.log`.
+To view the CORE daemon log file, look at `/var/log/cored.log`.
 
 == Step 3. Run CORE ==
 {{{
@@ -53,7 +56,7 @@ To view the CORE daemon log file, look at `/var/log/coredpy.log`.
 
 You'll see warnings about missing conf files the first time you run the CORE GUI.
 
-The sample topology `/etc/core/configs/sample1.imn` will test that CORE and OSPF MDR Quagga are correctly installed.
+The sample topology `~/.core/configs/sample1.imn` will test that CORE and OSPF MDR Quagga are correctly installed.
 
 = Quickstart: Installation from source =
 Follow these instructions to build CORE from source. Dependencies are automatically resolved when you use your package manager with the CORE packages shown above, but not when compiling from source. The source used could be a released version (see above) or the bleeding-edge [http://downloads.pf.itd.nrl.navy.mil/core/source/nightly_snapshots/ nightly SVN snapshot].