From 8d9f78779ab49cc19e25729cc89e7c26d2694bc6 Mon Sep 17 00:00:00 2001
From: Jibec <jean-baptiste@holcroft.fr>
Date: Apr 19 2020 13:24:17 +0000
Subject: suppress indentation warning


---

diff --git a/modules/ROOT/pages/gsoc/2005/index.adoc b/modules/ROOT/pages/gsoc/2005/index.adoc
index 1656966..ee3f568 100644
--- a/modules/ROOT/pages/gsoc/2005/index.adoc
+++ b/modules/ROOT/pages/gsoc/2005/index.adoc
@@ -11,27 +11,27 @@ organization.
 == Selected Projects
 
 * Behdad Esfahbod <behdad@cs.toronto.edu> - intelligent readahead daemon
-http://sourceforge.net/projects/preload[project page]
-http://www.cs.toronto.edu/~behdad/blog/preload.txt[proposal]
+  http://sourceforge.net/projects/preload[project page]
+  http://www.cs.toronto.edu/~behdad/blog/preload.txt[proposal]
 
 * Ljudmila Korjukina <lrs@inbox.ru> - packetsim
-http://sourceforge.net/projects/iptview/[project page]
+  http://sourceforge.net/projects/iptview/[project page]
 
 * Praveenkumar Ponnusamy <ps.praveenkr@gmail.com> - global bash history
-https://sourceforge.net/projects/bash-gchistory/[project page]
+  https://sourceforge.net/projects/bash-gchistory/[project page]
 
 * Ulisses Furquim <ulissesf@gmail.com> - pylibparted
-http://pylibparted.tigris.org/[project page]
+  http://pylibparted.tigris.org/[project page]
 
 * Darko Ilic <darko.ilic@gmail.com> - [wiki:Self:Kadischi Kadischi]
-(live CD generator)
+  (live CD generator)
 
 * Pedro Fernandes Macedo <pmacedo@dcc.ufmg.br> - smart mirror selection
-http://www.sourceforge.net/projects/mirrorselect[project page]
+  http://www.sourceforge.net/projects/mirrorselect[project page]
 
 * Wieland Gmeiner <e8607062@student.tuwien.ac.at> - setting process
-rlimits http://stud4.tuwien.ac.at/~e8607062/studies/soc/[proposal and
-patches]
+  rlimits http://stud4.tuwien.ac.at/~e8607062/studies/soc/[proposal and
+  patches]
 
 * Dave Arter <davea@sucs.org> - user backups (work in progress is at
 https://sucs.org/~davea/trac/)
@@ -40,13 +40,12 @@ https://sucs.org/~davea/trac/)
 http://www.ath-driver.org/
 
 * Adrian Bunk <bunk@stusta.de> - Fedora Directory Server auto*-ing
-http://www.fs.tum.de/~bunk/fds/[project page] or
-http://sourceforge.net/projects/fds-build/[SourceForge page]
+  http://www.fs.tum.de/~bunk/fds/[project page] or
+  http://sourceforge.net/projects/fds-build/[SourceForge page]
 
 * Camron T. Lacy <clacy@ctltechnologies.net> -
-system-config-securitylevel
-http://www.sourceforge.net/projects/securitylevel[Sourceforge page]
+  system-config-securitylevel
+  http://www.sourceforge.net/projects/securitylevel[Sourceforge page]
 
 * Vikram Aggarwal <vikrama@gmail.com> - install coverage testing
-http://sourceforge.net/projects/pootypedia/[project page]
-
+  http://sourceforge.net/projects/pootypedia/[project page]
diff --git a/modules/ROOT/pages/gsoc/2008/ideas.adoc b/modules/ROOT/pages/gsoc/2008/ideas.adoc
index b80f9a9..dcf015f 100644
--- a/modules/ROOT/pages/gsoc/2008/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2008/ideas.adoc
@@ -68,21 +68,21 @@ package.
 _Design Requirements:_
 
 * This must integrate with the PackageDB. Therefore it will be a piece
-of a larger TurboGears application. Knowledge of TurboGears and python
-is not required but a willingness to program in them is :-)
+  of a larger TurboGears application. Knowledge of TurboGears and python
+  is not required but a willingness to program in them is :-)
 * It is meant to be task and application oriented rather than package
-oriented. The aim is to answer questions like "What application will let
-me make drawings?" "Is there a python library for formatting
-documentation?" "I don't like "deluge" but I need something that does a
-similar thing?"
+  oriented. The aim is to answer questions like "What application will let
+  me make drawings?" "Is there a python library for formatting
+  documentation?" "I don't like "deluge" but I need something that does a
+  similar thing?"
 * We already have package information in several sources. We want to
-avoid duplicating information where possible but for efficiency we may
-need to pull some of the data into our database.
+  avoid duplicating information where possible but for efficiency we may
+  need to pull some of the data into our database.
 * The interface should link back and forth with the existing PackageDB
-but it is not simply another view of the data. Additional data will be
-involved.
+  but it is not simply another view of the data. Additional data will be
+  involved.
 * Allowing the user to contribute to the knowledge about the package is
-a goal.
+  a goal.
 
 A mockup of what a page could look like is in the
 link:https://fedoraproject.org/wiki/MyFedora?action=AttachFile&do=get&target=info-mockup.png[MyFedora
@@ -138,10 +138,10 @@ pushing this request to an Audacity SoC project.
 _Status:_
 
 * _Being worked on by User:bombshelter13[Gregory Masseau]
-(gjmasseau@learn.senecac.on.ca)_
+  (gjmasseau@learn.senecac.on.ca)_
 
 * _Being worked on by User:miltonpaiva[Milton Paiva]
-(mpaivaneto@learn.senecac.on.ca)_
+  (mpaivaneto@learn.senecac.on.ca)_
 
 _Summary of idea:_ Func is a network applications framework that allows
 for powerful remote manipulation and scripting of very large numbers of
@@ -288,11 +288,11 @@ format. It would be nice to:
 * extend bootchart to collect information using SystemTap instead.
 * code the boot information in XML format.
 * explore additional metrics that would make bootchart more useful, i.e.
-finding out the working set size at various points of the boot process,
-etc.
+  finding out the working set size at various points of the boot process,
+  etc.
 * test bootchart on Fedora 8/9/rawhide dom0/domU/kvm/etc.
 * propose (and possibly implement) suggestions on how we can improve the
-boot process.
+  boot process.
 
 _Skills needed:_ Strong background in Operating Systems. Familiarity
 with Python, Java/JAXP, XML and C programming. Some experience in kernel
@@ -565,7 +565,7 @@ _Notes:_
 * Security a challenge
 * Hook-up with Pootle as a use-case scenario?
 * If the server has plugins enabled, how is this going to be implemented
-here? (Interaction with student working on extensions might be needed)
+  here? (Interaction with student working on extensions might be needed)
 * (...more ideas?)
 
 [[transifex-extension-engine-tx_ext]]
@@ -587,10 +587,10 @@ DimitrisGlezos
 _Notes:_
 
 * Student might need to work with the student working on the client to
-discuss how the client can be extended to implement these plugins.
+  discuss how the client can be extended to implement these plugins.
 * Metrics will be needed to see how good the refactoring was, and what
-opportunities it will provide -- these metrics would be good to be
-mentioned in the application itself.
+  opportunities it will provide -- these metrics would be good to be
+  mentioned in the application itself.
 * (...more ideas?)
 
 [[transifex-permission-and-authorization-layer-tx_perm]]
@@ -605,19 +605,19 @@ the workflow Transifex creates by identifying key user groups and
 implementing functionality for each one.
 
 * Developers, administrators, language leaders, editors, translators,
-anonymous users: They all have different things to do in Transifex
+  anonymous users: They all have different things to do in Transifex
 * Add OpenID support
 * Introduce string, release, translation freezes that influence what
-some users can do
+  some users can do
 * Fine-grain permissions in Tx: Language maintainers, approvals by
-proj/lang/branch, etc. Who owns what, who controls what. Add ability to
-"hold" and "release" a project/branch, like in elvis.
+  proj/lang/branch, etc. Who owns what, who controls what. Add ability to
+  "hold" and "release" a project/branch, like in elvis.
 * Requirement for this idea is to work with the creators of Vertimus.
-This idea might (or might not) have common ground with Vertimus, and we
-need to make sure that either Tx can interoperate with Vertimus, or that
-the V folks know what we are working on and see how we can work together
-(note: Vertimus is written in PHP, but some interest has been raised for
-finding ways to work with Tx).
+  This idea might (or might not) have common ground with Vertimus, and we
+  need to make sure that either Tx can interoperate with Vertimus, or that
+  the V folks know what we are working on and see how we can work together
+  (note: Vertimus is written in PHP, but some interest has been raised for
+  finding ways to work with Tx).
 
 [[transifex-add-async-repo-support-tx_async]]
 == Transifex: Add async repo support (#tx_async)
@@ -681,10 +681,10 @@ the submissions instead of giving SSH access to a downstream project.
 * Split committer into a different component
 * Move commit code outside transifex/ and into transifex-committer/
 * Practically, have it behave as a different application. First, we
-could communicate with it via an API and then via JSON to have it
-remotely.
+  could communicate with it via an API and then via JSON to have it
+  remotely.
 * Use-cases: projects behind a firewall, upsteam projects not wanting to
-give SSH access, etc.
+  give SSH access, etc.
 * Work with SELinux a plus.
 
 _Contacts:_
@@ -705,19 +705,19 @@ submissions. Eg. a Fedora user could submit something to the Debian
 server, which will wait the approval of a Debian language leader.
 
 * For a single Tx instance to scale well, one might want to split its
-functionality into (say) el.fooTx.org, pt.fooTx.org, etc.
+  functionality into (say) el.fooTx.org, pt.fooTx.org, etc.
 * This splitting/joining requires something like a server to server
-architecture/protocol and the ability to aggregate and delegate stuff on
-both sides
+   architecture/protocol and the ability to aggregate and delegate stuff on
+  both sides
 * Some projects might want to have their own Tx instance which contains
-internal projects, not publicly visible. At the same time, they might
-have public projects wanting to freely receive translations, but also
-they might want to allow their internal translators to use this instance
-as a gateway to all other Tx servers.
+  internal projects, not publicly visible. At the same time, they might
+  have public projects wanting to freely receive translations, but also
+  they might want to allow their internal translators to use this instance
+  as a gateway to all other Tx servers.
 * Minimizing the independence between the scattered Tx instances (ie.
-building bridges between the Tx "islands") will bring the whole
-"community bridging" idea of Transifex to a whole new level. This is the
-goal we want to reach in the long term.
+  building bridges between the Tx "islands") will bring the whole
+  "community bridging" idea of Transifex to a whole new level. This is the
+  goal we want to reach in the long term.
 
 The most important aspect of this idea is architecture design. The
 student will need to have a very good image of content and translation
@@ -781,12 +781,12 @@ web-based translation for some modules. Here are some details about what
 could be done:
 
 * Add necessary configuration options in Pootle to use Transifex for
-certain tasks and particular modules.
+  certain tasks and particular modules.
 * Abstract what is needed to retain compatibility with the traditional
-way of handling files in Pootle.
+  way of handling files in Pootle.
 * Extend Transifex in a way that accepts submissions without the web
-interface (might need some discussion with the student working on the
-Command Line Interface).
+  interface (might need some discussion with the student working on the
+  Command Line Interface).
 
 _Contacts:_
 
@@ -795,14 +795,14 @@ NilsPhilippsen, DimitrisGlezos
 _Notes:_
 
 * Edit translations directly in Transifex (or in a seamless, integrated
-way with Tx), operating on individual messages.
+  way with Tx), operating on individual messages.
 * Compare pootle to locally running PO editors (e.g. kbabel,
-gtranslator, poedit), check if essential functionality is missing and
-eventually implement it (e.g. does it display eventually included source
-code comments which help translating the message, cf. "xgettext
---add-comments ...").
+  gtranslator, poedit), check if essential functionality is missing and
+  eventually implement it (e.g. does it display eventually included source
+  code comments which help translating the message, cf. "xgettext
+  --add-comments ...").
 * Evaluate whether certain Pootle functionality (e.g. translation
-suggestions) is needed or can be disabled for Transifex.
+  suggestions) is needed or can be disabled for Transifex.
 
 [[smolt-pretty-web-2.0-interfaces]]
 == Smolt: Pretty Web 2.0 Interfaces
@@ -826,11 +826,11 @@ This also does not inform people about any known issues about their
 machine. Two classic examples of what we are looking for are these:
 
 * Joe wants to know how many machines running Fedora 9 Betas have
-SELinux enabled
+  SELinux enabled
 * Fred needs to know that there is new eratta for his soundcard, perhaps
-we can make sound work on his new machine finally!
+  we can make sound work on his new machine finally!
 * Tim's machine works perfectly, how can he tell us this, so that we can
-mark our stamp of approval
+  mark our stamp of approval
 
 These are only guidelines of the things we are looking for. This project
 is very open ended, and you can do what you feel like. New Ideas are
diff --git a/modules/ROOT/pages/gsoc/2009/ideas.adoc b/modules/ROOT/pages/gsoc/2009/ideas.adoc
index 8daeb16..4cd1cc1 100644
--- a/modules/ROOT/pages/gsoc/2009/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2009/ideas.adoc
@@ -100,7 +100,7 @@ We also want to add a few features that aren't in other systems.
 * The ability to filter these as applications instead of packages,
 * Letting end users comment on the applications to help other end users
 * Letting end users tag the packages with keywords to make searching
-easier
+  easier
 
 More details here:
 
@@ -173,7 +173,7 @@ It allows you to:
 * Inventory your systems (hardware and software information)
 * Install and update software on your systems
 * Collect and distribute your custom software packages into manageable
-groups
+  groups
 * Provision (Kickstart) your systems
 * Manage and deploy configuration files to your systems
 * Monitor your systems
@@ -226,7 +226,7 @@ review request about problems expressed.
 At least the following problems are addressed:
 
 * Layout of app-install metadata and application icons inside of
-repository,
+  repository,
 * Pregenerating of app-install metadata and icons,
 * Change app-install to download metadata from repository,
 * Learn app-install to download icons on demand.
diff --git a/modules/ROOT/pages/gsoc/2010/ideas.adoc b/modules/ROOT/pages/gsoc/2010/ideas.adoc
index 137f386..3891f7a 100644
--- a/modules/ROOT/pages/gsoc/2010/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2010/ideas.adoc
@@ -293,7 +293,7 @@ _Notes:_ Ideas are
 * Errai (GWT) integration with CDI events
 * Errai (GWT) integration with Seam Security
 * Extensible project management tooling environment (based on Maven and
-Maven Archetypes)
+  Maven Archetypes)
 * Conversations with remote EJBs
 
 Please check details at the Student Projects wiki page at
@@ -336,7 +336,7 @@ _Summary of idea:_ Handy graphical tool for archiving settings of
 desktop applications. This tool will be useful for users who:
 
 * want to simply backup / restore look-and-feel and settings of desktop
-applications;
+  applications;
 * frequently migrate from one distribution to another;
 * have more then one device and want to sync settings.
 
@@ -351,17 +351,17 @@ and enable support for certain application.
 Proposed features:
 
 * Easy search and select installed applications for backup / restore /
-sync
+  sync
 * Can work as application or as daemon
 * Has scheduler and backup / restore / sync settings (archive type,
-passwords, compression rate, additive/solid, etc.)
+  passwords, compression rate, additive/solid, etc.)
 * Custom selection of applications for archiving (one, group, all, etc.)
 * Restoring data from archive with tracking of current application,
-nonexistent on target machine applications should be reinstalled from
-PackageKit
+  nonexistent on target machine applications should be reinstalled from
+  PackageKit
 * Including user selected files in archive for restoring on target
-machine (possibly searching and automatic including configuration files
-or files of specified types).
+  machine (possibly searching and automatic including configuration files
+  or files of specified types).
 
 
 [[unified-mobile-sync]]
@@ -389,18 +389,18 @@ _Mentor(s):_ For the moment link:https://fedoraproject.org/wiki/User:Anganar[Ale
 _Notes:_ Proposed features:
 
 * Synchronization of contacts and calendar (required), tasks and
-messages (desired)
+  messages (desired)
 * Support for popular mobile devices, simple extensibility for new
-gadgets via plugins
+  gadgets via plugins
 * Support for popular desktop applications, simple extensibility for
-other via plugins
+  other via plugins
 * Simple graphical synchronization tuning tool – what to synchronize,
-scheduling, rules (filters, conflict resolution, etc.)
+  scheduling, rules (filters, conflict resolution, etc.)
 * Enabling mobile device backup and restore
 * Desirably running not only on Linux, but also on Windows and MacOS
-(TBD)
+  (TBD)
 * Think about future integration with open source collaboration suites
-and unified communication systems.
+  and unified communication systems.
 
 _Current state_
 
@@ -416,40 +416,40 @@ implementation.
 The tasks for current stage:
 
 * Find out how to upload/download to/from popular mobile devices
-(Android, iPhone, Symbian, PalmOS, Win Mobile, BB, etc) contacts,
-messages, calendars, todos, media content, etc. It includes studying
-what data is accessible, in what format we are to process it, what
-protocols-libraries-APIs should be used. As a result we should get clear
-understanding what and how can be synced for different devices. This
-task will require gathering and reading tons of technical documentation
-and writing code to check if documentation is really true. I can not
-predict what programming languages, libraries, standards and protocols
-you will encounter.
+  (Android, iPhone, Symbian, PalmOS, Win Mobile, BB, etc) contacts,
+  messages, calendars, todos, media content, etc. It includes studying
+  what data is accessible, in what format we are to process it, what
+  protocols-libraries-APIs should be used. As a result we should get clear
+  understanding what and how can be synced for different devices. This
+  task will require gathering and reading tons of technical documentation
+  and writing code to check if documentation is really true. I can not
+  predict what programming languages, libraries, standards and protocols
+  you will encounter.
 
 * Find out how to upload/download to/from popular desktop apps
-(Evolution, Thunderbird, KDE PIM, Outlook, etc) contacts, messages,
-calendars, todos, media content, etc. Once again, it includes studing
-what is accessible, in what format, via which channels. As a result we
-should get clear understanding what and how can be synced with different
-apps. This task will require, similarly with the previous one, reading
-documentation and writing tests. Once again, I can not predict what
-programming languages, libraries, standards and protocols you will
-encounter.
+  (Evolution, Thunderbird, KDE PIM, Outlook, etc) contacts, messages,
+  calendars, todos, media content, etc. Once again, it includes studing
+  what is accessible, in what format, via which channels. As a result we
+  should get clear understanding what and how can be synced with different
+  apps. This task will require, similarly with the previous one, reading
+  documentation and writing tests. Once again, I can not predict what
+  programming languages, libraries, standards and protocols you will
+  encounter.
 
 * Find out how to integrate mobile sync into current system
-infrastructure for Linux desktop (dbus, udev, PackageKit, etc) and,
-probably, Windows desktop (???). This task will require very good
-knowledge of system design.
+  infrastructure for Linux desktop (dbus, udev, PackageKit, etc) and,
+  probably, Windows desktop (???). This task will require very good
+  knowledge of system design.
 
 * Prepare concept of GUI application and implement the first version
-(with placeholders instead of real sync plugins). This task will require
-knowledge of cross-platform programming with Python or C/C++ and
-GTK/Qt/etc. Knowledge of GUI design and usability will be a big
-advantage.
+  (with placeholders instead of real sync plugins). This task will require
+  knowledge of cross-platform programming with Python or C/C++ and
+  GTK/Qt/etc. Knowledge of GUI design and usability will be a big
+  advantage.
 
 * Prepare the architecture based on the results of tasks #1-4. The
-architecture should meet the requirements [1]. Determine tasks for
-complete UMS implementation.
+  architecture should meet the requirements [1]. Determine tasks for
+  complete UMS implementation.
 
 From my point of view each of the tasks #1-4 will require few
 person-months. Task #5 will be solved collaboratively.
diff --git a/modules/ROOT/pages/gsoc/2010/index.adoc b/modules/ROOT/pages/gsoc/2010/index.adoc
index 3e9c78b..c4ddd76 100644
--- a/modules/ROOT/pages/gsoc/2010/index.adoc
+++ b/modules/ROOT/pages/gsoc/2010/index.adoc
@@ -48,15 +48,15 @@ Working in FOSS gives you a chance to:
 * Work with real world large codebases.
 * Collaborate with real engineers and other professional experts.
 * Contribute to something meaningful while learning and earning student
-value.
+  value.
 * Learn tools and processes that are just like what you are going to use
-if you work in technology after graduation.
+  if you work in technology after graduation.
 * Make friends and contacts around the globe.
 * Possibly attract attention that gets you an internship or job after
-graduation.
+  graduation.
 * Earn while you learn. We are planning to sponsor $5000 for full
-projects and $2500 for half projects. Check out Summer_Coding_FAQ for
-more details.
+  projects and $2500 for half projects. Check out Summer_Coding_FAQ for
+  more details.
 
 [[why-work-with-fedora-and-jboss.org]]
 === Why work with Fedora and JBoss.org?
@@ -112,15 +112,15 @@ the mentoring group for your idea?
 You need to do these things:
 
 1.  Contact the relevant sub-project for your idea or contact
-http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss[the
-discussion group].
+    http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss[the
+    discussion group].
 2.  Be prepared to explain your idea, receive input and criticism, and
-grow (or reduce) the idea so it has the best chance of being accepted
-for Fedora Summer Coding.
+    grow (or reduce) the idea so it has the best chance of being accepted
+    for Fedora Summer Coding.
 3.  Create an idea page, noting in the section for mentors that you are
-looking for a mentor. Use
-link:https://fedoraproject.org/wiki/How_to_create_an_idea_page_for_Summer_Coding[How to create an idea
-page for Summer Coding] to make the page.
+    looking for a mentor. Use
+    link:https://fedoraproject.org/wiki/How_to_create_an_idea_page_for_Summer_Coding[How to create an idea
+    page for Summer Coding] to make the page.
 
 [[are-you-already-working-in-the-fedora-or-jboss-communities]]
 === Are you already working in the Fedora or JBoss communities?
@@ -220,11 +220,11 @@ JBoss.org, or another).
 Your responsibilities include:
 
 * Being an interface for an identified sub-project or SIG in Fedora or
-JBoss.org.
+  JBoss.org.
 * Helping students communicate with the overall project and any
-upstreams.
+  upstreams.
 * Be the final, accountable person for deciding if the student is
-successful or not, which affects payment.
+  successful or not, which affects payment.
 
 [[are-you-committed-to-working-with-all-parties]]
 === Are you committed to working with all parties?
@@ -308,10 +308,10 @@ What do you get out of it?
 * Positively impact FOSS projects.
 * Get your brand in front of smart students who want to work on FOSS.
 * Potentially end up
-link:https://fedoraproject.org/wiki/GSoC_report_2009#Recruiting_new_Red_Hat_associates[hiring great
-developers through the program].
+  link:https://fedoraproject.org/wiki/GSoC_report_2009#Recruiting_new_Red_Hat_associates[hiring great
+  developers through the program].
 * Work on a community program that demonstrates how open source business
-is done.
+  is done.
 * See something you’d like coded be completed.
 * Other positive brand associations.
 
@@ -321,18 +321,18 @@ is done.
 We need to start talking, soon.
 
 * Open by default on the discuss list -
-http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss
+  http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss
 * Private via direct email to project leadership - link:https://fedoraproject.org/wiki/User:Quaid[Karsten
-Wade], ...
+  Wade], ...
 
 What are the resources you can supply?
 
 1.  Money to pay stipends to students for spending focused time on these
-FOSS projects. This is a cross between a summer job and an internship.
+    FOSS projects. This is a cross between a summer job and an internship.
 2.  Someone to help coordinate and to contribute as part of the Fedora
-Summer Coding special interest group (SIG).
+    Summer Coding special interest group (SIG).
 3.  Mentors, especially if they work actively in sub-project or area the
-sponsor is supporting.
+    sponsor is supporting.
 
 [[what-does-the-summer-coding-program-do]]
 === What does the Summer Coding program do?
diff --git a/modules/ROOT/pages/gsoc/2011/ideas.adoc b/modules/ROOT/pages/gsoc/2011/ideas.adoc
index 329480b..895e22e 100644
--- a/modules/ROOT/pages/gsoc/2011/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2011/ideas.adoc
@@ -151,9 +151,9 @@ systems. In addition to porting to TG2 (see above), several enhancements
 would be welcome:
 
 * Simplify creation of new MirrorManager instances (non-Fedora users,
-such as CentOS)
+  such as CentOS)
 * Simplify selection of mirrors within Cloud Providers on granularity
-other than netblocks and ASNs
+  other than netblocks and ASNs
 * Other items on the
 http://git.fedorahosted.org/git/mirrormanager?p=mirrormanager;a=blob;f=TODO;hb=HEAD[TODO
 list]
@@ -287,8 +287,8 @@ other Linux distributions.
 
 * _Status:_ Proposed
 * _Summary of idea:_ Currently, the System Security Services Daemon
-supports only LDAP for network user identity. Support for NIS identities
-has been requested several times by end-users.
+  supports only LDAP for network user identity. Support for NIS identities
+  has been requested several times by end-users.
 * _Contacts:_ link:https://fedoraproject.org/wiki/User:Sgallagh[Stephen Gallagher]
 * _Mentor(s):_ link:https://fedoraproject.org/wiki/User:Sgallagh[Stephen Gallagher]
 
@@ -297,10 +297,10 @@ has been requested several times by end-users.
 
 * _Status:_ Proposed
 * _Summary of idea:_ Sudo 1.8.0 will support a plugin interface for sudo
-authorization decisions. It would be excellent for SSSD to provide such
-a plugin to provide cached access to sudo information stored in the sudo
-LDAP schema. This would make it easier to maintain centralized sudo
-rules that also function while offline.
+  authorization decisions. It would be excellent for SSSD to provide such
+  a plugin to provide cached access to sudo information stored in the sudo
+  LDAP schema. This would make it easier to maintain centralized sudo
+  rules that also function while offline.
 * _Contacts:_ link:https://fedoraproject.org/wiki/User:Sgallagh[Stephen Gallagher]
 * _Mentor(s):_ link:https://fedoraproject.org/wiki/User:Sgallagh[Stephen Gallagher]
 * _Notes:_ http://www.sudo.ws/sudo_plugin.man.html
diff --git a/modules/ROOT/pages/gsoc/2012/ideas.adoc b/modules/ROOT/pages/gsoc/2012/ideas.adoc
index 896656b..4c29e20 100644
--- a/modules/ROOT/pages/gsoc/2012/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2012/ideas.adoc
@@ -394,20 +394,20 @@ towards fixing that. We have some disparate ideas / tools that we'd like
 to be integrated:
 
 * http://sparkleshare.org[Sparkleshare] - a git-backed, Dropbox like
-system that will automatically check in and push files in project
-directly to a shared git repo
+  system that will automatically check in and push files in project
+  directly to a shared git repo
 * https://github.com/garrett/magicmockup[Magic Mockup] - a
-coffeescript/javascript you can insert into an SVG of mockups to enable
-interactive, click-through mockups
-(http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/[see
-a demo here]
+  coffeescript/javascript you can insert into an SVG of mockups to enable
+  interactive, click-through mockups
+  (http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/[see
+  a demo here]
 * http://blog.linuxgrrl.com/category/design-hub/[Design Hub] - an idea
-and a ruby on rails prototype of a web front end that could potentially
-serve as a front end to git repos with design assets *and* serve as well
-as a front end to magic mockup mockups in said repos
+  and a ruby on rails prototype of a web front end that could potentially
+  serve as a front end to git repos with design assets *and* serve as well
+  as a front end to magic mockup mockups in said repos
 * http://inkscape.org[Inkscape] is our preferred design tool of choice;
-it would be great if it had some GUI integration with Magic Mockup,
-Sparkleshare, and Design Hub
+  it would be great if it had some GUI integration with Magic Mockup,
+  Sparkleshare, and Design Hub
 
 _Knowledge prerequisite:_ Ruby on Rails, web development, some UI design
 chops
@@ -683,10 +683,10 @@ can compile packages on the user side, and installed locally.
 The benefit of this method is:
 
 1.  No need to host the entire packages (saving space on servers hosting
-the RPMs)
+    the RPMs)
 2.  Make changes to the buildfile, and not compile the package
 3.  Can pull sources from any version control system/stored tarballs to
-make a very upto-date package. (See blog entry for an example)
+    make a very upto-date package. (See blog entry for an example)
 
 _Contacts:_ link:https://fedoraproject.org/wiki/User:Anujmore[Anuj More]
 
@@ -760,13 +760,13 @@ to):
 * packaging open source audio projects
 * porting certain packages from the PlanetCCRMA repository into Fedora
 * working/communicating with the Fedora Audio community to determine the
-final make-up of the spin
+  final make-up of the spin
 * help coordinate pushing the spin through the Spins Review process
 * creating/testing kickstart files
 * developing small applications/scripts to help solve hardware and audio
-system configuration requirements
+  system configuration requirements
 * communicating with Fedora Audio SIG, Fedora Desktop team and other
-Fedora teams
+  Fedora teams
 * organizing QA testcases and test days
 
 Ideally, interested candidates will have a passion for Music/Audio
diff --git a/modules/ROOT/pages/gsoc/2012/index.adoc b/modules/ROOT/pages/gsoc/2012/index.adoc
index 47728a8..7f9c144 100644
--- a/modules/ROOT/pages/gsoc/2012/index.adoc
+++ b/modules/ROOT/pages/gsoc/2012/index.adoc
@@ -32,12 +32,12 @@ Working in FOSS gives you a chance to:
 * Work with real world large codebases.
 * Collaborate with real engineers and other professional experts.
 * Contribute to something meaningful while learning and earning student
-value.
+  value.
 * Learn tools and processes that are just like what you are going to use
-if you work in technology after graduation.
+  if you work in technology after graduation.
 * Make friends and contacts around the globe.
 * Possibly attract attention that gets you an internship or job after
-graduation.
+  graduation.
 * Create life time connections.
 
 [[why-work-with-fedora]]
@@ -106,22 +106,22 @@ students' idea page and pick one as per your interest.
 === How to work with students
 
 * One way is to provide an idea for students to work on. This idea might
-be very well planned out, in which case you may need a high-level of
-contact with the student to get it implemented correctly.
+  be very well planned out, in which case you may need a high-level of
+  contact with the student to get it implemented correctly.
 
 * It is harder to find success where you are completely certain of how
-an idea needs to be implemented; finding a student with the skills and
-interest to implement a specific solution is a lot harder than finding a
-student with enough skills to respond to a use case need.
+  an idea needs to be implemented; finding a student with the skills and
+  interest to implement a specific solution is a lot harder than finding a
+  student with enough skills to respond to a use case need.
 
 * Where you can have looser ideas, you may be able to find a student who
-works as a sort-of intern who can implement a solution to a use case you
-have. In past experiences, students going after a use case are more
-likely to get somewhere with self-direction.
+  works as a sort-of intern who can implement a solution to a use case you
+  have. In past experiences, students going after a use case are more
+  likely to get somewhere with self-direction.
 
 * You may also want to work with a student who brings an idea to your
-sub-project. This requires a different level of communication throughout
-the project, but can be the most rewarding.
+  sub-project. This requires a different level of communication throughout
+  the project, but can be the most rewarding.
 
 [[mentor-responsibilities]]
 === Mentor responsibilities
@@ -134,9 +134,9 @@ Your responsibilities include:
 
 * Being an interface for an identified sub-project or SIG in Fedora.
 * Helping students communicate with the overall project and any
-upstreams.
+  upstreams.
 * Be the final, accountable person for deciding if the student is
-successful or not, which affects payment.
+  successful or not, which affects payment.
 
 [[list-of-mentors]]
 === List of Mentors
@@ -186,11 +186,11 @@ http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/faqs#ti
 
 * March 9: Mentoring organization application deadline.
 * March 12-15: Google program administrators review organization
-applications.
+  applications.
 * March 16: List of accepted mentoring organizations published on the
-Google Summer of Code 2012 site.
+  Google Summer of Code 2012 site.
 * March 17-25: Would-be student participants discuss application ideas
-with mentoring organizations.
+  with mentoring organizations.
 * March 26: Student application period opens.
 * April 6: Student application deadline.
 
@@ -199,21 +199,21 @@ proposals; where necessary, mentoring organizations may request further
 proposal detail from the student applicant.
 
 * April 20: All mentors must be signed up and all student proposals
-matched with a mentor. Student ranking/scoring deadline.
+  matched with a mentor. Student ranking/scoring deadline.
 * April 23: Accepted student proposals announced on the Google Summer of
-Code 2012 site.
+  Code 2012 site.
 
 Community Bonding Period: Students get to know mentors, read
 documentation, get up to speed to begin working on their projects.
 
 * May 21: Students begin coding for their Google Summer of Code
-projects;
+  projects;
 
 Interim Period: Mentors give students a helping hand and guidance on
 their projects.
 
 * July 9: Mentors and students can begin submitting mid-term
-evaluations.
+  evaluations.
 * July 13: Mid-term evaluations deadline;
 
 Google begins issuing mid-term student payments provided passing student
@@ -221,14 +221,14 @@ survey is on file. Interim Period: Mentors give students a helping hand
 and guidance on their projects.
 
 * August 13: Suggested 'pencils down' date. Take a week to scrub code,
-write tests, improve documentation, etc.
+  write tests, improve documentation, etc.
 * August 20: Mentors, students and organization administrators can begin
-submitting final evaluations to Google.
+  submitting final evaluations to Google.
 
 * August 24: Final evaluation deadline
 * August 27: Final results of Google Summer of Code 2012 announced
 * August 31: Students can begin submitting required code samples to
-Google
+  Google
 * October 20 - 21: Mentor Summit at Google.
 
 [[organization-application]]
diff --git a/modules/ROOT/pages/gsoc/2013/ideas.adoc b/modules/ROOT/pages/gsoc/2013/ideas.adoc
index 1fe1134..5d699f2 100644
--- a/modules/ROOT/pages/gsoc/2013/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2013/ideas.adoc
@@ -489,20 +489,20 @@ towards fixing that. We have some disparate ideas / tools that we'd like
 to be integrated:
 
 * http://sparkleshare.org[Sparkleshare] - a git-backed, Dropbox like
-system that will automatically check in and push files in project
-directly to a shared git repo
+  system that will automatically check in and push files in project
+  directly to a shared git repo
 * https://github.com/garrett/magicmockup[Magic Mockup] - a
-coffeescript/javascript you can insert into an SVG of mockups to enable
-interactive, click-through mockups
-(http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/[see
-a demo here]
+  coffeescript/javascript you can insert into an SVG of mockups to enable
+  interactive, click-through mockups
+  (http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/[see
+  a demo here]
 * http://blog.linuxgrrl.com/category/design-hub/[Design Hub] - an idea
-and a ruby on rails prototype of a web front end that could potentially
-serve as a front end to git repos with design assets *and* serve as well
-as a front end to magic mockup mockups in said repos
+  and a ruby on rails prototype of a web front end that could potentially
+  serve as a front end to git repos with design assets *and* serve as well
+  as a front end to magic mockup mockups in said repos
 * http://inkscape.org[Inkscape] is our preferred design tool of choice;
-it would be great if it had some GUI integration with Magic Mockup,
-Sparkleshare, and Design Hub
+  it would be great if it had some GUI integration with Magic Mockup,
+  Sparkleshare, and Design Hub
 
 _Knowledge prerequisite:_ Ruby on Rails, web development, some UI design
 chops _Skill level:_ Intermediate _Contacts:_ edirsh at redhat dot com
@@ -613,8 +613,8 @@ if you are interested to contribute.
 
 * Status: Proposed
 * Summary of idea: Contribute to the fedpkg project, enabling the
-building of a series of interdependent packages in a single action for
-released Fedora branches
+  building of a series of interdependent packages in a single action for
+  released Fedora branches
 * Knowledge Prerequisite: Python, Fedora Packaging
 * Skill Level: Low - Medium
 * Contacts: link:https://fedoraproject.org/wiki/User:sgallagh[Stephen Gallagher]
@@ -626,9 +626,9 @@ released Fedora branches
 
 * Status: Proposed
 * Summary of idea: There is a need of an information system where it can
-be used with in the project to track and analyse the finacial
-activities. It may be a customiztion of a open source solution or a
-solution from scratch.
+  be used with in the project to track and analyse the finacial
+  activities. It may be a customiztion of a open source solution or a
+  solution from scratch.
 * Skill Level: Medium
 
 * Mentor : link:https://fedoraproject.org/wiki/User:Charindu100[Charindu Thiwanka] - Technical
@@ -640,11 +640,11 @@ solution from scratch.
 
 * Status: Proposed
 * Summary of idea: Fedora contributors organize lot of events. We need a
-system to manage them. This sounds like a project management utility.
-You can either build from scratch or customize an available free
-software. This can be used to small event and as well as large event
-like FUDcons. The main advantage to use such system is to organize tasks
-and manage the cost. If you are interested contact me with a proposal.
+  system to manage them. This sounds like a project management utility.
+  You can either build from scratch or customize an available free
+  software. This can be used to small event and as well as large event
+  like FUDcons. The main advantage to use such system is to organize tasks
+  and manage the cost. If you are interested contact me with a proposal.
 * Skill Level: Medium
 * Contacts: link:https://fedoraproject.org/wiki/User:Bckurera[Buddhike Kurera]
 * Mentor(s): link:https://fedoraproject.org/wiki/User:Bckurera[Buddhike Kurera])
@@ -656,7 +656,7 @@ and manage the cost. If you are interested contact me with a proposal.
 * Status: Proposed
 
 * Summary of idea: http://darkserver.fedoraproject.org/[Darkserver] now
-only supports primary koji instance of Fedora. We need support
+  only supports primary koji instance of Fedora. We need support
 
 other secondary architectures and distributions. Different workers
 should use different job queues and they all should work independently.
@@ -673,8 +673,8 @@ becomes more test friendly.
 * Mentor(s): link:https://fedoraproject.org/wiki/User:Kushal[Kushal Das]
 
 * Notes: Join the
-https://lists.fedorahosted.org/mailman/listinfo/darkserver[mailing list]
-and also #dgplug on freenode.
+  https://lists.fedorahosted.org/mailman/listinfo/darkserver[mailing list]
+  and also #dgplug on freenode.
 
 [[linux-system-services]]
 === Linux system services
@@ -684,12 +684,12 @@ and also #dgplug on freenode.
 
 * Status: Proposed
 * Summary of idea: The purpose of this project is to develop a suite of
-unit tests for the SSSD. The unit tests would leverage mock objects to
-be able to exercise code that is otherwise only ever reachable when the
-SSSD is connected to the network. Contributing the set of unit tests to
-the SSSD would greatly improve its stability long-term and would help
-raise confidence when pushing new SSSD versions into Fedora or other
-distributions.
+  unit tests for the SSSD. The unit tests would leverage mock objects to
+  be able to exercise code that is otherwise only ever reachable when the
+  SSSD is connected to the network. Contributing the set of unit tests to
+  the SSSD would greatly improve its stability long-term and would help
+  raise confidence when pushing new SSSD versions into Fedora or other
+  distributions.
 * Knowledge prerequisite: C programming
 * Skill level: intermediate to high
 * Contacts: link:https://fedoraproject.org/wiki/User:jhrozek[Jakub Hrozek]
@@ -710,10 +710,10 @@ can compile packages on the user side, and installed locally.
 The benefit of this method is:
 
 1.  No need to host the entire packages (saving space on servers hosting
-the RPMs)
+    the RPMs)
 2.  Make changes to the buildfile, and not compile the package
 3.  Can pull sources from any version control system/stored tarballs to
-make a very upto-date package. (See blog entry for an example)
+    make a very upto-date package. (See blog entry for an example)
 
 _Contacts:_ link:https://fedoraproject.org/wiki/User:Anujmore[Anuj More]
 
@@ -908,7 +908,7 @@ Possible project components:
 
 * side repository management
 * better integration with bodhi and working based on updates instead of
-just package envrs
+  just package envrs
 * tree replication
 * integration with blockerbugs app
 * deltaiso creation
diff --git a/modules/ROOT/pages/gsoc/2013/index.adoc b/modules/ROOT/pages/gsoc/2013/index.adoc
index 82b11eb..9802b86 100644
--- a/modules/ROOT/pages/gsoc/2013/index.adoc
+++ b/modules/ROOT/pages/gsoc/2013/index.adoc
@@ -32,12 +32,12 @@ Working in FOSS gives you a chance to:
 * Work with real world large codebases.
 * Collaborate with real engineers and other professional experts.
 * Contribute to something meaningful while learning and earning student
-value.
+  value.
 * Learn tools and processes that are just like what you are going to use
-if you work in technology after graduation.
+  if you work in technology after graduation.
 * Make friends and contacts around the globe.
 * Possibly attract attention that gets you an internship or job after
-graduation.
+  graduation.
 * Create life time connections.
 
 [[why-work-with-fedora]]
@@ -105,22 +105,22 @@ students' idea page and pick one as per your interest.
 
 
 * One way is to provide an idea for students to work on. This idea might
-be very well planned out, in which case you may need a high-level of
-contact with the student to get it implemented correctly.
+  be very well planned out, in which case you may need a high-level of
+  contact with the student to get it implemented correctly.
 
 * It is harder to find success where you are completely certain of how
-an idea needs to be implemented; finding a student with the skills and
-interest to implement a specific solution is a lot harder than finding a
-student with enough skills to respond to a use case need.
+  an idea needs to be implemented; finding a student with the skills and
+  interest to implement a specific solution is a lot harder than finding a
+  student with enough skills to respond to a use case need.
 
 * Where you can have looser ideas, you may be able to find a student who
-works as a sort-of intern who can implement a solution to a use case you
-have. In past experiences, students going after a use case are more
-likely to get somewhere with self-direction.
+  works as a sort-of intern who can implement a solution to a use case you
+  have. In past experiences, students going after a use case are more
+  likely to get somewhere with self-direction.
 
 * You may also want to work with a student who brings an idea to your
-sub-project. This requires a different level of communication throughout
-the project, but can be the most rewarding.
+  sub-project. This requires a different level of communication throughout
+  the project, but can be the most rewarding.
 
 [[mentor-responsibilities]]
 === Mentor responsibilities
@@ -133,9 +133,9 @@ Your responsibilities include:
 
 * Being an interface for an identified sub-project or SIG in Fedora.
 * Helping students communicate with the overall project and any
-upstream.
+  upstream.
 * Be the final, accountable person for deciding if the student is
-successful or not, which affects payment.
+  successful or not, which affects payment.
 
 [[list-of-mentors]]
 === List of Mentors
@@ -162,9 +162,9 @@ Reference :
 http://www.google-melange.com/gsoc/events/google/gsoc2013[Full timeline]
 
 * April 8: 19:00 UTC List of accepted mentoring organizations published
-on the Google Summer of Code 2013 site.
+  on the Google Summer of Code 2013 site.
 * April 9 - 21: Would-be student participants discuss application ideas
-with mentoring organizations.
+  with mentoring organizations.
 * April 22: 19:00 UTC Student application period opens.
 * May 3: 19:00 UTC Student application deadline.
 
@@ -173,7 +173,7 @@ proposals; where necessary, mentoring organizations may request further
 proposal detail from the student applicant.
 
 * May 6: Mentoring organizations should have requested slots via their
-profile in Melange by this point.
+  profile in Melange by this point.
 * May 8: Slot allocations published to mentoring organizations
 
 Interim Period: Slot allocation trades happen amongst organizations.
@@ -182,13 +182,13 @@ necessary, mentoring organizations may request further proposal detail
 from the student applicant.
 
 * May 27: 19:00 UTC Accepted student proposals announced on the Google
-Summer of Code 2013 site.
+  Summer of Code 2013 site.
 
 Community Bonding Period: Students get to know mentors, read
 documentation, get up to speed to begin working on their projects.
 
 * June 17: Students begin coding for their Google Summer of Code
-projects;
+  projects;
 
 Google begins issuing initial student payments provided tax forms are on
 file and students are in good standing with their communities. Work
@@ -196,22 +196,22 @@ Period: Mentors give students a helping hand and guidance on their
 projects.
 
 * July 29: 19:00 UTC Mentors and students can begin submitting mid-term
-evaluations.
+  evaluations.
 * August 2: 19:00 UTC Mid-term evaluations deadline;
 * Work Period: Mentors give students a helping hand and guidance on
-their projects.
+  their projects.
 * September 16: Suggested 'pencils down' date. Take a week to scrub
-code, write tests, improve documentation, etc.
+  code, write tests, improve documentation, etc.
 * September 23: 19:00 UTC Firm 'pencils down' date. Mentors, students
-and organization administrators can begin submitting final evaluations
-to Google.
+  and organization administrators can begin submitting final evaluations
+  to Google.
 * September 27: 19:00 UTC Final evaluation deadline
 
 Google begins issuing student and mentoring organization payments
 provided forms and evaluations are on file.
 
 * September 27: Students can begin submitting required code samples to
-Google
+  Google
 * October 1: Final results of Google Summer of Code 2013 announced
 * October 19 & 20: Mentor Summit at Google
 
@@ -241,7 +241,7 @@ the idea is picked by a mentor.
 
 1.  link:https://fedoraproject.org/wiki/Foundation[The Foundation]
 2.  http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2016/help_page[GSoC
-FAQ]
+    FAQ]
 3.  http://docs.fedoraproject.org/en-US/index.html[Fedora Documentation]
 4.  link:https://fedoraproject.org/wiki/Communicate/IRCHowTo[IRC]
 5.  link:https://fedoraproject.org/wiki/Development[Development]
diff --git a/modules/ROOT/pages/gsoc/2013/student_application_process.adoc b/modules/ROOT/pages/gsoc/2013/student_application_process.adoc
index 1417d5d..a1c2b10 100644
--- a/modules/ROOT/pages/gsoc/2013/student_application_process.adoc
+++ b/modules/ROOT/pages/gsoc/2013/student_application_process.adoc
@@ -10,13 +10,13 @@ followed.
 
 .  link:https://fedoraproject.org/wiki/GSOC_Guide_students#Set_up_an_account[Create a FAS account]
 .  link:https://fedoraproject.org/wiki/GSOC_Guide_students#Start_communicating[Join with
-fedora-summer-coding mailing list]
+   fedora-summer-coding mailing list]
 .  Submit application on
-https://google-melange.appspot.com/gsoc/proposal/submit/google/gsoc2013/fedora[Google-Melange]
+   https://google-melange.appspot.com/gsoc/proposal/submit/google/gsoc2013/fedora[Google-Melange]
 .  link:https://fedoraproject.org/wiki/GSOC_2013/Student_Application_Template/Common[Application is
-filled] and available on Fedora Wiki -
-link:https://fedoraproject.org/wiki/GSOC_Guide_students#Create_your_Application[How to fill the
-application]
+   filled] and available on Fedora Wiki -
+   link:https://fedoraproject.org/wiki/GSOC_Guide_students#Create_your_Application[How to fill the
+   application]
 .  CV highlighting your activities with Information Technology
 .  A recommendation from (highlighting your fitness)
     .  A member of a Free Software Organization you have contributed earlier OR
@@ -83,7 +83,7 @@ one from the project who see your great contribution. That can be
 considered as a recommendation.
 
 * *I dont get a reply from Org Admins after sending documents, is it
-normal?*
+  normal?*
 
 You should get a reply with in 24 hours, if not please immediately
 contact Org Admin.
diff --git a/modules/ROOT/pages/gsoc/2014/ideas.adoc b/modules/ROOT/pages/gsoc/2014/ideas.adoc
index 0aef207..4938702 100644
--- a/modules/ROOT/pages/gsoc/2014/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2014/ideas.adoc
@@ -32,7 +32,7 @@ channel can be used to get instant support.
 
 1.  link:https://fedoraproject.org/wiki/Foundation[The Foundation]
 2.  http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2016/help_page[GSoC
-FAQ]
+    FAQ]
 3.  http://docs.fedoraproject.org/en-US/index.html[Fedora Documentation]
 4.  link:https://fedoraproject.org/wiki/Communicate/IRCHowTo[IRC]
 5.  link:https://fedoraproject.org/wiki/Development[Development]
@@ -134,7 +134,7 @@ http://bugspad.readthedocs.org/en/latest/
 Minimal required TODO
 
 * Fully working frontend, primary idea is to go fully selfhosted. All
-bugs should be filed in that instance against Bugspad.
+  bugs should be filed in that instance against Bugspad.
 
 _Knowledge prerequisite:_
 
@@ -167,16 +167,16 @@ A demo instance of Waartaa is hosted at https://try.waartaa.com.
 Roadmap:
 
 * Build a central hub for searching/reading channel logs for Open Source
-communities and projects.
+  communities and projects.
 * Build a faster and scalable backend.
 * Freedom of choice: Expose an API so that users can use their existing
-IRC clients with waartaa.
+  IRC clients with waartaa.
 * Find a secure way to authenticate with IRC services without storing
-RAW passwords.
+  RAW passwords.
 * Respect user privacy: user personal messages should be stored in an
-encrypted format in the server.
+  encrypted format in the server.
 * Allow users to download chat logs in various formats compatible with
-popular IRC clients.
+  popular IRC clients.
 * HTML5 mobile app
 * VCS, Bugzilla and other task management tools integration.
 * Video/audio conference facility on top of HTML5 and JS technologies.
@@ -283,13 +283,13 @@ collaborate, backed by Git for version control, and intended to be part
 of a FLOSS design suite that includes
 
 * http://sparkleshare.org[Sparkleshare] - a git-backed, Dropbox like
-system that will automatically check in and push files in project
-directly to a shared git repo
+  system that will automatically check in and push files in project
+  directly to a shared git repo
 * https://github.com/garrett/magicmockup[Magic Mockup] - a
-coffeescript/javascript you can insert into an SVG of mockups to enable
-interactive, click-through mockups
-(http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/[see
-a demo here] )
+  coffeescript/javascript you can insert into an SVG of mockups to enable
+  interactive, click-through mockups
+  (http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/[see
+  a demo here] )
 * http://inkscape.org[Inkscape] is our preferred design tool of choice
 
 Last year, a successful GSoC took Glitter Gallery from a prototype to a
@@ -297,22 +297,22 @@ fully featured web app, but there are still plenty of features to be
 added, and improvements to be made. Some things that still need work:
 
 * Transitioning to test-driven development, which means writing unit and
-integration tests for all of the components
+  integration tests for all of the components
 * Better design suite integration, which could mean better support for
-local editing with SparkleShare; Inkscape integration through an
-extension; and/or support for creating and sharing interactive SVGs with
-Magic Mockup
+  local editing with SparkleShare; Inkscape integration through an
+  extension; and/or support for creating and sharing interactive SVGs with
+  Magic Mockup
 * UI improvements - the current UI is functional and pretty nice
-looking, but it could be more responsive and polished
+  looking, but it could be more responsive and polished
 * Better commenting - the current commenting system is basic, and
-there's lots of ways it could be improved, including thread support,
-pingback support, the ability to reference a specific region of a design
-in a comment
+  there's lots of ways it could be improved, including thread support,
+  pingback support, the ability to reference a specific region of a design
+  in a comment
 * Issue tracking - allow the designer to track requested changes as
-issues
+  issues
 * More social features - such as the ability to follow a
-file/project/user, an activity feed, private messaging, easy sharing
-outside the application
+  file/project/user, an activity feed, private messaging, easy sharing
+  outside the application
 * Your own ideas
 
 _Knowledge prerequisite:_ git, Ruby on Rails, front-end (HTML/CSS/JS)
@@ -589,7 +589,7 @@ The plugin should:
 * implement Java model(s) for XMvn configuration
 * allow reading and writing model(s) as XML files
 * implement configuration editor providing raw XML view and one or more
-high-level views
+  high-level views
 * allow converting configuration to sequence of RPM macro calls
 
 XMvn plugin should integrate with Eclipse Linux Tools and/or Fedora
@@ -926,8 +926,8 @@ if you are interested to contribute.
 
 * Status: Proposed
 * Summary of idea: Contribute to the fedpkg project, enabling the
-building of a series of interdependent packages in a single action for
-released Fedora branches
+  building of a series of interdependent packages in a single action for
+  released Fedora branches
 * Knowledge Prerequisite: Python, Fedora Packaging
 * Skill Level: Low - Medium
 * Contacts: link:https://fedoraproject.org/wiki/User:sgallagh[Stephen Gallagher]
@@ -940,9 +940,9 @@ released Fedora branches
 
 * Status: Proposed
 * Summary of idea: There is a need of an information system where it can
-be used with in the project to track and analyse the financial
-activities. It may be a customization of a open source solution or a
-solution from scratch.
+  be used with in the project to track and analyse the financial
+  activities. It may be a customization of a open source solution or a
+  solution from scratch.
 
 * Skill Level: Medium
 
@@ -960,12 +960,12 @@ solution from scratch.
 
 * Status: Proposed
 * Summary of idea: The purpose of this project is to develop a suite of
-unit tests for the SSSD. The unit tests would leverage mock objects to
-be able to exercise code that is otherwise only ever reachable when the
-SSSD is connected to the network. Contributing the set of unit tests to
-the SSSD would greatly improve its stability long-term and would help
-raise confidence when pushing new SSSD versions into Fedora or other
-distributions.
+  unit tests for the SSSD. The unit tests would leverage mock objects to
+  be able to exercise code that is otherwise only ever reachable when the
+  SSSD is connected to the network. Contributing the set of unit tests to
+  the SSSD would greatly improve its stability long-term and would help
+  raise confidence when pushing new SSSD versions into Fedora or other
+  distributions.
 * Knowledge prerequisite: C programming
 * Skill level: intermediate to high
 * Contacts: link:https://fedoraproject.org/wiki/User:jhrozek[Jakub Hrozek]
@@ -988,7 +988,7 @@ can compile packages on the user side, and installed locally.
 The benefit of this method is:
 
 1.  No need to host the entire packages (saving space on servers hosting
-the RPMs)
+    the RPMs)
 2.  Make changes to the buildfile, and not compile the package
 3.  Can pull sources from any version control system/stored tarballs to
 make a very upto-date package. (See blog entry for an example)
diff --git a/modules/ROOT/pages/gsoc/2014/index.adoc b/modules/ROOT/pages/gsoc/2014/index.adoc
index 5be451f..0ab7add 100644
--- a/modules/ROOT/pages/gsoc/2014/index.adoc
+++ b/modules/ROOT/pages/gsoc/2014/index.adoc
@@ -32,12 +32,12 @@ Working in FOSS gives you a chance to:
 * Work with real world large codebases.
 * Collaborate with real engineers and other professional experts.
 * Contribute to something meaningful while learning and earning student
-value.
+  value.
 * Learn tools and processes that are just like what you are going to use
-if you work in technology after graduation.
+  if you work in technology after graduation.
 * Make friends and contacts around the globe.
 * Possibly attract attention that gets you an internship or job after
-graduation.
+  graduation.
 * Create life time connections.
 
 [[why-work-with-fedora]]
@@ -108,22 +108,22 @@ students' idea page and pick one as per your interest.
 
 
 * One way is to provide an idea for students to work on. This idea might
-be very well planned out, in which case you may need a high-level of
-contact with the student to get it implemented correctly.
+  be very well planned out, in which case you may need a high-level of
+  contact with the student to get it implemented correctly.
 
 * It is harder to find success where you are completely certain of how
-an idea needs to be implemented; finding a student with the skills and
-interest to implement a specific solution is a lot harder than finding a
-student with enough skills to respond to a use case need.
+  an idea needs to be implemented; finding a student with the skills and
+  interest to implement a specific solution is a lot harder than finding a
+  student with enough skills to respond to a use case need.
 
 * Where you can have looser ideas, you may be able to find a student who
-works as a sort-of intern who can implement a solution to a use case you
-have. In past experiences, students going after a use case are more
-likely to get somewhere with self-direction.
+  works as a sort-of intern who can implement a solution to a use case you
+  have. In past experiences, students going after a use case are more
+  likely to get somewhere with self-direction.
 
 * You may also want to work with a student who brings an idea to your
-sub-project. This requires a different level of communication throughout
-the project, but can be the most rewarding.
+  sub-project. This requires a different level of communication throughout
+  the project, but can be the most rewarding.
 
 [[mentor-responsibilities]]
 === Mentor responsibilities
@@ -137,9 +137,9 @@ Your responsibilities include:
 
 * Being an interface for an identified sub-project or SIG in Fedora.
 * Helping students communicate with the overall project and any
-upstream.
+  upstream.
 * Be the final, accountable person for deciding if the student is
-successful or not, which affects payment.
+  successful or not, which affects payment.
 
 [[list-of-mentors]]
 === List of Mentors
@@ -169,9 +169,9 @@ Reference :
 http://www.google-melange.com/gsoc/events/google/gsoc2014[Full timeline]
 
 * 24 February:19:00 UTC List of accepted mentoring organizations
-published on the Google Summer of Code 2014 site.
+  published on the Google Summer of Code 2014 site.
 * February 24 - March 10: Would-be student participants discuss
-application ideas with mentoring organizations.
+  application ideas with mentoring organizations.
 * 10 March:19:00 UTC Student application period opens.
 * 21 March:19:00 UTC Student application deadline.
 
@@ -180,7 +180,7 @@ proposals; where necessary, mentoring organizations may request further
 proposal detail from the student applicant.
 
 * 7 April: Mentoring organizations should have requested slots via their
-profile in Melange by this point.
+  profile in Melange by this point.
 * 9 April: Slot allocations published to mentoring organizations
 
 Interim Period: Slot allocation trades happen amongst organizations.
@@ -189,13 +189,13 @@ necessary, mentoring organizations may request further proposal detail
 from the student applicant.
 
 * 21 April: 19:00 UTC Accepted student proposals announced on the Google
-Summer of Code 2014 site.
+  Summer of Code 2014 site.
 
 Community Bonding Period: Students get to know mentors, read
 documentation, get up to speed to begin working on their projects.
 
 * 19 May: Students begin coding for their Google Summer of Code
-projects;
+  projects;
 
 Google begins issuing initial student payments provided tax forms are on
 file and students are in good standing with their communities. Work
@@ -203,22 +203,22 @@ Period: Mentors give students a helping hand and guidance on their
 projects.
 
 * 23 June: 19:00 UTC Mentors and students can begin submitting mid-term
-evaluations.
+  evaluations.
 * 27 June: 19:00 UTC Mid-term evaluations deadline;
 * Work Period: Mentors give students a helping hand and guidance on
-their projects.
+  their projects.
 * 11 August: Suggested 'pencils down' date. Take a week to scrub code,
-write tests, improve documentation, etc.
+  write tests, improve documentation, etc.
 * 18 August: 19:00 UTC Firm 'pencils down' date. Mentors, students and
-organization administrators can begin submitting final evaluations to
-Google.
+  organization administrators can begin submitting final evaluations to
+  Google.
 * 22 August: 19:00 UTC Final evaluation deadline
 
 Google begins issuing student and mentoring organization payments
 provided forms and evaluations are on file.
 
 * 22 August: 20:00 UTC Students can begin submitting required code
-samples to Google
+  samples to Google
 * 25 August: Final results of Google Summer of Code 2014 announced
 * 25 & 26 October: Mentor Summit at Google
 
@@ -261,7 +261,7 @@ note the mentors' contact details.
 
 1.  link:https://fedoraproject.org/wiki/Foundation[The Foundation]
 2.  http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2016/help_page[GSoC
-FAQ]
+    FAQ]
 3.  http://docs.fedoraproject.org/en-US/index.html[Fedora Documentation]
 4.  link:https://fedoraproject.org/wiki/Communicate/IRCHowTo[IRC]
 5.  link:https://fedoraproject.org/wiki/Development[Development]
diff --git a/modules/ROOT/pages/gsoc/2014/student_application_process.adoc b/modules/ROOT/pages/gsoc/2014/student_application_process.adoc
index fa2e64b..337d45b 100644
--- a/modules/ROOT/pages/gsoc/2014/student_application_process.adoc
+++ b/modules/ROOT/pages/gsoc/2014/student_application_process.adoc
@@ -88,7 +88,7 @@ one from the project who see your great contribution. That can be
 considered as a recommendation.
 
 * *I dont get a reply from Org Admins after sending documents, is it
-normal?*
+  normal?*
 
 You should get a reply with in 24 hours, if not please immediately
 contact Org Admin.
diff --git a/modules/ROOT/pages/gsoc/2015/ideas.adoc b/modules/ROOT/pages/gsoc/2015/ideas.adoc
index 3cdaae3..aca87c3 100644
--- a/modules/ROOT/pages/gsoc/2015/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2015/ideas.adoc
@@ -23,10 +23,10 @@ support.
 
 1.  link:https://fedoraproject.org/wiki/Foundation[The Foundation]
 2.  http://docs.fedoraproject.org/en-US/index.html[Fedora Documentation
-(Users/ Contributors)]
+    (Users/ Contributors)]
 3.  link:https://fedoraproject.org/wiki/Communicate/IRCHowTo[How to work with IRC?]
-https://fedoramagazine.org/begginers-guide-to-irc[Beginner's Guide to
-IRC]
+    https://fedoramagazine.org/begginers-guide-to-irc[Beginner's Guide to
+    IRC]
 4.  link:https://fedoraproject.org/wiki/FAS[Fedora Account System]
 5.  link:https://fedoraproject.org/wiki/Development[Development]
 
@@ -98,10 +98,10 @@ _Notes:_ Rough roadmap:
 
 * Implement tinykdump daemon to be included in Fedora.
 * Submit kernel patches for reserving kdump memory at run-time for
-community review and inclusion.
+  community review and inclusion.
 * Currently, pstore only log kernel messages for panic and Oops. Patches
-are needed to support logging of kdump kernel and initramfs console
-output.
+  are needed to support logging of kdump kernel and initramfs console
+  output.
 
 [[improve-fedora-review]]
 === Improve Fedora Review
@@ -128,13 +128,13 @@ _Notes:_ Possible tasks:
 
 * Make Fedora Review PEP8 compliant, fix its current test cases
 * Help running Fedora Review regularly for existing packages e.g.,
-updating the Jenkins continuous builds and/or integrate it into
-Taskotron
+  updating the Jenkins continuous builds and/or integrate it into
+  Taskotron
 * Add static code checker support to Fedora Review (e.g. with
-https://git.fedorahosted.org/git/csmock.git[csmock])
+  https://git.fedorahosted.org/git/csmock.git[csmock])
 * Build a web service mockup supporting the review process
-http://fedoraproject.org/wiki/Package_Review_Process[1] replacing
-current bugzilla workflow.
+  http://fedoraproject.org/wiki/Package_Review_Process[1] replacing
+  current bugzilla workflow.
 
 [[enhance-fedora-build-setup]]
 === Enhance Fedora build setup
@@ -159,21 +159,21 @@ __Mentor(s):__link:https://fedoraproject.org/wiki/User:Till[Till Maas], link:htt
 _Notes:_ Rough roadmap:
 
 * Make select https://fedorahosted.org/rel-eng/[releng scripts] PEP8
-compliant/python3 ready
+  compliant/python3 ready
 * Make other python tools PEP8 compliant, python3 ready:
 ** https://fedorahosted.org/fedpkg/[fedpkg]
 ** https://git.fedorahosted.org/cgit/mash/[mash]
 ** https://fedorahosted.org/rpkg/[rpkg]
 * Become familiar with the Fedora packaging workflow, maybe by packaging
-some software
+  some software
 * Learn how to interface koji and write a script to get a mapping of git
-commit ID to package build (name, version, release)
+  commit ID to package build (name, version, release)
 * Write a koji plugin to enforce that pkgs can be only built from the
-right GIT branch for each build target (might need improvements to
-koji's plugin interface as well):
-https://fedorahosted.org/rel-eng/ticket/5843
+  right GIT branch for each build target (might need improvements to
+  koji's plugin interface as well):
+  https://fedorahosted.org/rel-eng/ticket/5843
 * Write a fedmsg service/cronjob to regularly tag sucessful builds in
-GIT: https://fedorahosted.org/rel-eng/ticket/5856
+  GIT: https://fedorahosted.org/rel-eng/ticket/5856
 * Help with koji2
 
 [[improve-sigul-signing-server]]
@@ -203,30 +203,30 @@ link:https://fedoraproject.org/wiki/User:ralph[Ralph Bean]
 _Notes:_ Rough roadmap:
 
 * To test whether everything works, a test instance needs to be setup.
-This is rather complex because it requires interaction with koji. Maybe
-it is possible to add a test instance to Infrastructure that can use the
-koji staging system, but the latter is not fully functional right now.
+  This is rather complex because it requires interaction with koji. Maybe
+  it is possible to add a test instance to Infrastructure that can use the
+  koji staging system, but the latter is not fully functional right now.
 * Debug why sigul hangs sometimes when using the
-https://git.fedorahosted.org/cgit/sigul.git/tree/src/client.py#n1090[sign-rpms]
-command (called by `--batch-size` greater than one with
-`sigulsign_unsigned.py`
+  https://git.fedorahosted.org/cgit/sigul.git/tree/src/client.py#n1090[sign-rpms]
+  command (called by `--batch-size` greater than one with
+  `sigulsign_unsigned.py`
 * Enable sigul to process multiple tasks at once, e.g. sign for multiple
-releases or architectures at once.
+  releases or architectures at once.
 * Fix other bugs/issues, examples:
 ** Currently http://linux.die.net/man/8/logrotate[logrotate] does not
-make sigul properly re-open its logfiles, which is why sigul does not
-log to the new logfile after rotation. This needs to be fixed in sigul
+   make sigul properly re-open its logfiles, which is why sigul does not
+   log to the new logfile after rotation. This needs to be fixed in sigul
 ** The GPG defaults in sigul might not be up-to-date, they should be
-reviewed and improved if necessary
+   reviewed and improved if necessary
 ** Add support for e.g. signing and revoking GPG keys, to build a local
-web of trust between https://getfedora.org/keys/[Fedora release keys]
+   web of trust between https://getfedora.org/keys/[Fedora release keys]
 
 Ressources:
 
 * https://git.fedorahosted.org/cgit/releng/tree/scripts/sigulsign_unsigned.py[Script
-used by rel-eng to run sigul]
+  used by rel-eng to run sigul]
 * https://git.fedorahosted.org/cgit/sigul.git/tree/doc/protocol-design.txt[Protocol
-description]
+  description]
 
 [[askfedora-uxui-functionality-overhaul]]
 === AskFedora UX/UI & Functionality Overhaul
@@ -292,35 +292,35 @@ artists to create, share, and collaborate, backed by Git for version
 control, and intended to be part of a FLOSS design suite that includes
 
 * http://sparkleshare.org[Sparkleshare] - a git-backed, Dropbox like
-system that will automatically check in and push files in project
-directly to a shared git repo
+  system that will automatically check in and push files in project
+  directly to a shared git repo
 * https://github.com/garrett/magicmockup[Magic Mockup] - a javascript
-library you can insert into an SVG of mockups to enable interactive,
-click-through mockups
-(http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/[see
-a demo here]
+  library you can insert into an SVG of mockups to enable interactive,
+  click-through mockups
+  (http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/[see
+  a demo here]
 * http://inkscape.org[Inkscape] is our preferred design tool of choice
 
 Last year, two GSoC students worked on a number of critical improvements
 to GlitterGallery, but there is still plenty of work to be done.
 
 * Public gallery of works; currently the app requires a user to login
-and to follow other users before they can see work other than their own.
-They can also view direct links to works. A public gallery can be used
-to browse and explore works without having to be logged in.
+  and to follow other users before they can see work other than their own.
+  They can also view direct links to works. A public gallery can be used
+  to browse and explore works without having to be logged in.
 * Better design suite integration, which could mean better support for
-local editing with SparkleShare; Inkscape integration through an
-extension; and/or support for creating and sharing interactive SVGs with
-Magic Mockup
+  local editing with SparkleShare; Inkscape integration through an
+  extension; and/or support for creating and sharing interactive SVGs with
+  Magic Mockup
 * Better commenting - the current commenting system is basic, and
-there's lots of ways it could be improved, including thread support,
-pingback support, the ability to reference a specific region of a design
-in a comment
+  there's lots of ways it could be improved, including thread support,
+  pingback support, the ability to reference a specific region of a design
+  in a comment
 * External issue tracking - Glitter Gallery has an integrated issue
-tracker, but it would be useful to also be able to integrate with
-external bug/issue trackers such as GitHub and Bugzilla.
+  tracker, but it would be useful to also be able to integrate with
+  external bug/issue trackers such as GitHub and Bugzilla.
 * Enhanced history view - (see
-https://github.com/glittergallery/GlitterGallery/issues/187)
+  https://github.com/glittergallery/GlitterGallery/issues/187)
 * Your own ideas
 
 _Knowledge prerequisites:_ git, Ruby on Rails, front-end (HTML/CSS/JS)
@@ -537,17 +537,17 @@ _Notes:_ Potential features:
 
 * Show a clear overview for patches in Fedora for a certain package
 ** Link to bugs that were mentioned, extract key information from the
-bug
+   bug
 * Allow to get notifications for new patches, e.g. via fedmsg
 * Allow to get information about patches for the package in other
-distros
+  distros
 * Try to figure out if patches are already upstream
 * ...
 
 Rough potential roadmap:
 
 * Get the debian patch tracker running on a test system, maybe with some
-example debian packages
+  example debian packages
 * Port it for one example Fedora package
 * Port it to a modern web framework such as Flask or Pyramid
 * Make sure it is PEP8 compliant
@@ -560,14 +560,14 @@ Basic requirements:
 
 * Target platform is RHEL/CentOS7 with EPEL
 * All dependencies should be available on the target platform as RPM
-packages or possible to be packaged (e.g. requiring newer versions of
-packages already included in the target platform might not be easily
-possible)
+  packages or possible to be packaged (e.g. requiring newer versions of
+  packages already included in the target platform might not be easily
+  possible)
 * It needs to be possible to package the final project for Fedora/EPEL,
-i.e. there may not be bundled libraries included
+  i.e. there may not be bundled libraries included
 * The code needs to be PEP8 compliant and contain proper docstrings
 * Proper automtatic tests should be included to allow meaningful
-continuous integration
+  continuous integration
 
 Recommended basic knowledge:
 
@@ -655,7 +655,7 @@ flags:
 Helpful documentation:
 
 * link:https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds[Using Mock to test package
-builds]
+  builds]
 
 [[enhance-postgresql-gssapi-support]]
 === Enhance PostgreSQL GSSAPI Support
diff --git a/modules/ROOT/pages/gsoc/2015/index.adoc b/modules/ROOT/pages/gsoc/2015/index.adoc
index 665aea6..79b20c9 100644
--- a/modules/ROOT/pages/gsoc/2015/index.adoc
+++ b/modules/ROOT/pages/gsoc/2015/index.adoc
@@ -32,12 +32,12 @@ Working in FOSS gives you a chance to:
 * Work with real world large codebases.
 * Collaborate with real engineers and other professional experts.
 * Contribute to something meaningful while learning and earning student
-value.
+  value.
 * Learn tools and processes that are just like what you are going to use
-if you work in technology after graduation.
+  if you work in technology after graduation.
 * Make friends and contacts around the globe.
 * Possibly attract attention that gets you an internship or job after
-graduation.
+  graduation.
 * Create life time connections.
 
 [[why-work-with-fedora]]
@@ -107,22 +107,22 @@ students' idea page and pick one as per your interest.
 === How to work with students
 
 * One way is to provide an idea for students to work on. This idea might
-be very well planned out, in which case you may need a high-level of
-contact with the student to get it implemented correctly.
+  be very well planned out, in which case you may need a high-level of
+  contact with the student to get it implemented correctly.
 
 * It is harder to find success where you are completely certain of how
-an idea needs to be implemented; finding a student with the skills and
-interest to implement a specific solution is a lot harder than finding a
-student with enough skills to respond to a use case need.
+  an idea needs to be implemented; finding a student with the skills and
+  interest to implement a specific solution is a lot harder than finding a
+  student with enough skills to respond to a use case need.
 
 * Where you can have looser ideas, you may be able to find a student who
-works as a sort-of intern who can implement a solution to a use case you
-have. In past experiences, students going after a use case are more
-likely to get somewhere with self-direction.
+  works as a sort-of intern who can implement a solution to a use case you
+  have. In past experiences, students going after a use case are more
+  likely to get somewhere with self-direction.
 
 * You may also want to work with a student who brings an idea to your
-sub-project. This requires a different level of communication throughout
-the project, but can be the most rewarding.
+  sub-project. This requires a different level of communication throughout
+  the project, but can be the most rewarding.
 
 [[mentor-responsibilities]]
 === Mentor responsibilities
@@ -136,9 +136,9 @@ Your responsibilities include:
 
 * Being an interface for an identified sub-project or SIG in Fedora.
 * Helping students communicate with the overall project and any
-upstream.
+  upstream.
 * Be the final, accountable person for deciding if the student is
-successful or not, which affects payment.
+  successful or not, which affects payment.
 
 [[list-of-mentors]]
 === List of Mentors
@@ -168,46 +168,46 @@ http://www.google-melange.com/gsoc/events/google/gsoc2016[Full timeline]
 
 * 6 October, 2014: Program announced.
 * 9 February, 2015: 19:00 UTC Mentoring organizations can begin
-submitting applications to Google.
+  submitting applications to Google.
 * 20 February: 19:00 UTC Mentoring organization application deadline.
 * 23 - 27 February: Google program administrators review organization
-applications.
+  applications.
 * 2 March: 19:00 UTC List of accepted mentoring organizations published
-on the Google Summer of Code 2015 site.
+  on the Google Summer of Code 2015 site.
 * Interim Period: Would-be students discuss project ideas with potential
-mentoring organizations.
+  mentoring organizations.
 * 6 March 16:00 UTC: IRC feedback meeting for rejected organizations for
-Google Summer of Code 2015. #gsoc on freenode.net. Rejected
-organizations may also choose to email the administrators directly for
-feedback.
+  Google Summer of Code 2015. #gsoc on freenode.net. Rejected
+  organizations may also choose to email the administrators directly for
+  feedback.
 * 14 March: 19:00 UTC Student application period opens.
 * 27 March: 19:00 UTC Student application deadline.
 * Interim Period: Mentoring organizations review and rank student
-proposals; where necessary, mentoring organizations may request further
-proposal detail from the student applicant.
+  proposals; where necessary, mentoring organizations may request further
+  proposal detail from the student applicant.
 * 13 April: Mentoring organizations should have requested slots via
-their profile in Melange by this point.
+  their profile in Melange by this point.
 * 15 April: Slot allocations published to mentoring organizations.
 * Interim Period: Slot allocation trades happen amongst organizations.
-Mentoring organizations review and rank student proposals; where
-necessary, mentoring organizations may request further proposal detail
-from the student applicant.
+  Mentoring organizations review and rank student proposals; where
+  necessary, mentoring organizations may request further proposal detail
+  from the student applicant.
 * 21 April: First round of de-duplication checks happens; organizations
-work together to try to resolve as many duplicates as possible.
+  work together to try to resolve as many duplicates as possible.
 * 24 April: All mentors must be signed up and all student proposals
-matched with a mentor -07:00 UTC. Student acceptance choice deadline.IRC
-meeting to resolve any outstanding duplicate accepted students - 19:00
-UTC #gsoc (organizations must send a delegate to represent them in this
-meeting regardless of if they are in a duplicate situation before the
-meeting.)
+  matched with a mentor -07:00 UTC. Student acceptance choice deadline.IRC
+  meeting to resolve any outstanding duplicate accepted students - 19:00
+  UTC #gsoc (organizations must send a delegate to represent them in this
+  meeting regardless of if they are in a duplicate situation before the
+  meeting.)
 * 27 April: 19:00 UTC Accepted student proposals announced on the Google
-Summer of Code 2015 site.
+  Summer of Code 2015 site.
 
 Community Bonding Period: Students get to know mentors, read
 documentation, get up to speed to begin working on their projects.
 
 * 25 May: Students begin coding for their Google Summer of Code
-projects;
+  projects;
 
 Google begins issuing initial student payments provided tax forms are on
 file and students are in good standing with their communities. Work
@@ -215,7 +215,7 @@ Period: Mentors give students a helping hand and guidance on their
 projects.
 
 * 26 June: 19:00 UTCMentors and students can begin submitting mid-term
-evaluations.
+  evaluations.
 * 3 July: 19:00 UTC Mid-term evaluations deadline;
 
 Google begins issuing mid-term student payments provided passing student
@@ -223,25 +223,25 @@ survey is on file. Work Period: Mentors give students a helping hand and
 guidance on their projects.
 
 * 17 August: Suggested 'pencils down' date. Take a week to scrub code,
-write tests, improve documentation, etc.
+  write tests, improve documentation, etc.
 * 21 August: 19:00 UTC Firm 'pencils down' date. Mentors, students and
-organization administrators can begin submitting final evaluations to
-Google.
+  organization administrators can begin submitting final evaluations to
+  Google.
 * 28 August: 19:00 UTC Final evaluation deadline
 
 Google begins issuing student and mentoring organization payments
 provided forms and evaluations are on file.
 
 * 28 August: 19:30 UTC Students can begin submitting required code
-samples to Google
+  samples to Google
 * 31 August: Final results of Google Summer of Code 2015 announced
 * 25 September: 19:00 UTC "Soft" deadline for student code sample
-submission. Students who want their t-shirts and certificates in the
-first wave of shipments must submit their code sample by this date.
+  submission. Students who want their t-shirts and certificates in the
+  first wave of shipments must submit their code sample by this date.
 * 6 - 8 November: Mentor Summit at Google: Delegates from each
-successfully participating organization are invited to Google to greet,
-collaborate and code. Our mission for the weekend: make the program even
-better, have fun and make new friends.
+  successfully participating organization are invited to Google to greet,
+  collaborate and code. Our mission for the weekend: make the program even
+  better, have fun and make new friends.
 
 [[ideas-page]]
 == Ideas Page
@@ -282,7 +282,7 @@ note the mentors' contact details.
 
 1.  link:https://fedoraproject.org/wiki/Foundation[The Foundation]
 2.  http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2016/help_page[GSoC
-FAQ]
+    FAQ]
 3.  http://docs.fedoraproject.org/en-US/index.html[Fedora Documentation]
 4.  link:https://fedoraproject.org/wiki/Communicate/IRCHowTo[IRC]
 5.  link:https://fedoraproject.org/wiki/Development[Development]
diff --git a/modules/ROOT/pages/gsoc/2015/student_application_process.adoc b/modules/ROOT/pages/gsoc/2015/student_application_process.adoc
index 01815e0..89e1d7e 100644
--- a/modules/ROOT/pages/gsoc/2015/student_application_process.adoc
+++ b/modules/ROOT/pages/gsoc/2015/student_application_process.adoc
@@ -22,28 +22,28 @@ Following criterion should be fulfilled on or before the application
 deadline unless otherwise specifically noted.
 
 * Create a FAS account link:https://admin.fedoraproject.org/accounts[FAS
-Account Signup / Login Page]
+  Account Signup / Login Page]
 
 * Join with fedora-summer-coding mailing list
-link:https://lists.fedoraproject.org/admin/lists/summer-coding[Fedora Summer
-Coding Mailing List]
+  link:https://lists.fedoraproject.org/admin/lists/summer-coding[Fedora Summer
+  Coding Mailing List]
 
 * Join with devel mailing list
-link:https://admin.fedoraproject.org/mailman/devel[Devel Mailing List]
+  link:https://admin.fedoraproject.org/mailman/devel[Devel Mailing List]
 
 * Chose a project for proposal from
-xref:ideas.adoc[Summer_coding_ideas_for_2016]
+  xref:ideas.adoc[Summer_coding_ideas_for_2016]
 
 * Submit application/proposal on Google-Melange
-link:https://summerofcode.withgoogle.com/get-started/[Google Melange
-Submission Page]
+  link:https://summerofcode.withgoogle.com/get-started/[Google Melange
+  Submission Page]
 
 ''_'What to write about in your proposal / application._
 
 * Details on your previous FOSS contributions (if any).
 
 * A detailed plan with your planned activities in May to September (eg:
-Exams in university, internships, vacations..etc)
+  Exams in university, internships, vacations..etc)
 
 * Bare mind - Remember to contact your mentor before you submit the
 application.
diff --git a/modules/ROOT/pages/gsoc/2016/ideas.adoc b/modules/ROOT/pages/gsoc/2016/ideas.adoc
index 1e12633..21df445 100644
--- a/modules/ROOT/pages/gsoc/2016/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2016/ideas.adoc
@@ -18,7 +18,7 @@ help with programming problems.
 
 1.  link:https://docs.fedoraproject.org/fedora-project/project/fedora-overview.html[The Four Foundations of Fedora]
 2.  link:https://developers.google.com/open-source/gsoc/resources/[Official
-GSoC Resources]
+    GSoC Resources]
 3.  link:http://docs.fedoraproject.org/en-US/index.html[Fedora Documentation]
 4.  link:https://fedoraproject.org/wiki/How_to_use_IRC?rd=Communicate/IRCHowTo[IRC]
 5.  link:https://fedoraproject.org/wiki/Development[Development]
@@ -80,10 +80,10 @@ _Notes_: Rough roadmap:
 
 * Implement tinykdump daemon to be included in Fedora.
 * Submit kernel patches for reserving kdump memory at run-time for
-community review and inclusion.
+  community review and inclusion.
 * Currently, pstore only log kernel messages for panic and Oops. Patches
-are needed to support logging of kdump kernel and initramfs console
-output.
+  are needed to support logging of kdump kernel and initramfs console
+  output.
 
 [[implement-mips-bits-to-packages]]
 === Implement MIPS bits to packages
@@ -110,7 +110,7 @@ _Notes_: The following packages are in question:
 * *redhat-lsb* - misses assembly bits for MIPS
 * *anaconda/blivet* - completely MIPS unaware
 * *valgrind* - no FPXX support on 32-bit MIPS, builds on mips64el but
-does not work
+  does not work
 * *elfutils* - unwinding is not supported on MIPS
 * *u-boot* - build working MIPS images
 * ... there are more but these are the most painful
diff --git a/modules/ROOT/pages/gsoc/2017/application_process.adoc b/modules/ROOT/pages/gsoc/2017/application_process.adoc
index 4be4d74..5876aab 100644
--- a/modules/ROOT/pages/gsoc/2017/application_process.adoc
+++ b/modules/ROOT/pages/gsoc/2017/application_process.adoc
@@ -43,9 +43,9 @@ this is a great way to understand the needs of the project and find a
 mentor.
 
 * link:https://lists.fedoraproject.org/admin/lists/summer-coding.lists.fedoraproject.org[the
-summer-coding list]
+  summer-coding list]
 * link:https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org[the
-development list].
+  development list].
 
 Don't forget to contact mentors on projects that interest you to learn
 more. If you're going to propose a project you must have a mentor at the
@@ -105,36 +105,36 @@ background, etc. The following format provides some guidance:
 
 * Contact Information
 ** List your Name, Email Address, Blog URL, and any additional contact
-information you think we need. We tend to email so be sure you're
-reading your email.
+   information you think we need. We tend to email so be sure you're
+   reading your email.
 * About You - Consider these questions
 ** Do you have any past involvement with the Fedora Project or another
-open-source project as a contributor? What kind of contributions have
-you made (code and non-code)? Please share any public contributions you
-have made (urls, etc.)
+   open-source project as a contributor? What kind of contributions have
+   you made (code and non-code)? Please share any public contributions you
+   have made (urls, etc.)
 ** What are you studying? Why?
 ** What motivates you to do your best? How do you stay focused? Briefly
-describe how you organize your work.
+   describe how you organize your work.
 * Why Us? - Consider these questions
 ** Why do you want to work with the Fedora Project?
 ** Do you plan to continue contributing to the Fedora Project after
-GSoC? If yes, what sub-project(s) are you interested with?
+   GSoC? If yes, what sub-project(s) are you interested with?
 * Why This Project? - Consider these questions
 ** Which specific project interests you? If you are proposing your own
-project, do it here. If you are proposing the project, explain why it
-benefits the community.
+   project, do it here. If you are proposing the project, explain why it
+   benefits the community.
 ** Have you contacted the mentor(s) listed for the project?
 ** What relevant experience do you have for this project?
 ** What do you want to gain from this project?
 ** Describe this project in your own words. What does it mean to you?
-What do you think the final deliverable is?
+   What do you think the final deliverable is?
 * Why should we choose you over other applicants?
 * Propose a rough schedule for this project. Ideally you will have
-regular deliverables throughout the entire period.
+  regular deliverables throughout the entire period.
 * What are you specific plans from May to September (eg: Exams in
-university, internships, vacations..etc). We need to know if there are
-periods of time where you are likely to be unavailable. We are better at
-accommodating these periods if we know of them in advance.
+  university, internships, vacations..etc). We need to know if there are
+  periods of time where you are likely to be unavailable. We are better at
+  accommodating these periods if we know of them in advance.
 
 [[additional-fedora-requirements]]
 ==== Additional Fedora Requirements
@@ -142,35 +142,35 @@ accommodating these periods if we know of them in advance.
 Students need to do the following as part of the application process:
 
 * Create a FAS account link:https://admin.fedoraproject.org/accounts[FAS
-Account Signup / Login Page]
+  Account Signup / Login Page]
 * If you can't edit the wiki (see next step), email link:https://fedoraproject.org/wiki/User:Bex[Brian (bex)
-Exelbierd], the primary administrator with your FAS ID and request
-access.
+  Exelbierd], the primary administrator with your FAS ID and request
+  access.
 * On the project wiki link:https://fedoraproject.org/wiki, create a user
-page. Do this by opening a new web browser tab and going to
-link:https://fedoraproject.org/wiki/User:Yourusername[`https://fedoraproject.org/wiki/User:Yourusername`],
-replacing `Yourusername` with your actual Fedora Account System
-username.
+  page. Do this by opening a new web browser tab and going to
+  link:https://fedoraproject.org/wiki/User:Yourusername[`https://fedoraproject.org/wiki/User:Yourusername`],
+  replacing `Yourusername` with your actual Fedora Account System
+  username.
 ** This link:https://fedoraproject.org/wiki/Template:Userpage[user page template] provides a basic layout
-that you can copy. You can also look at the markup for other users'
-pages. Here's a selection of some nice user pages:
+   that you can copy. You can also look at the markup for other users'
+   pages. Here's a selection of some nice user pages:
 *** link:https://fedoraproject.org/wiki/User:Jsimon[Joerg Simon]
 *** link:https://fedoraproject.org/wiki/User:Ilianaw?rd=User:Ianweller[Iliana Weller]
 *** link:https://fedoraproject.org/wiki/User:Pfrields[Paul W. Frields]
 *** link:https://fedoraproject.org/wiki/Kaio2012?rd=User:Kaio[Caius C. Chance]
 ** Do not forget to add the Summer coding category to your page, for
-example for 2017: `[[category:Summer_coding_2017]]`
+   example for 2017: `[[category:Summer_coding_2017]]`
 ** When you save the page, remember to click 'watch this page' at the
-top.
+   top.
 * Join the fedora-summer-coding mailing list
-link:https://lists.fedoraproject.org/admin/lists/summer-coding.lists.fedoraproject.org[Fedora
-Summer Coding Mailing List] - This list is fairly low volume.
+  link:https://lists.fedoraproject.org/admin/lists/summer-coding.lists.fedoraproject.org[Fedora
+  Summer Coding Mailing List] - This list is fairly low volume.
 * Join the devel mailing list
-link:https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org[Devel
-Mailing List] - this list can be higher volume you may wish to use mail
-filters appropriately.
+  link:https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org[Devel
+  Mailing List] - this list can be higher volume you may wish to use mail
+  filters appropriately.
 * Sign the FPCA by following the directions
-link:https://fedoraproject.org/wiki/Account_System/CompleteFPCA[here]
+  link:https://fedoraproject.org/wiki/Account_System/CompleteFPCA[here]
 
 [[let-others-know]]
 === Let others know
diff --git a/modules/ROOT/pages/gsoc/2017/ideas.adoc b/modules/ROOT/pages/gsoc/2017/ideas.adoc
index 047cd01..1229c60 100644
--- a/modules/ROOT/pages/gsoc/2017/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2017/ideas.adoc
@@ -26,7 +26,7 @@ xref:application_process.adoc[student application process]
 
 * link:https://docs.fedoraproject.org/fedora-project/project/fedora-overview.html[The Four Foundations of Fedora]
 * link:https://developers.google.com/open-source/gsoc/resources/[Official
-GSoC Resources]
+  GSoC Resources]
 * link:http://docs.fedoraproject.org/en-US/index.html[Fedora Documentation]
 * link:https://fedoraproject.org/wiki/How_to_use_IRC?rd=Communicate/IRCHowTo[IRC]
 * link:https://fedoraproject.org/wiki/Development[Development]
@@ -41,22 +41,22 @@ busy, you can contact one of the people below for short-term help on
 your project or task.
 
 * link:https://fedoraproject.org/wiki/User:Bex[Brian (bex) Exelbierd] (Fedora Community Action and Impact
-Coordinator, FCAIC, 🎂, containers, general development, general Linux)
+  Coordinator, FCAIC, 🎂, containers, general development, general Linux)
 * link:https://fedoraproject.org/wiki/User:Jflory7[Justin W. Flory] (General development, general Linux,
-Fedora community, GSoC alumnus, questions about program, misc. advice)
+  Fedora community, GSoC alumnus, questions about program, misc. advice)
 * link:https://fedoraproject.org/wiki/User:Rhea[Radka (rhea) Janek] (C#, webserver or dotnet related stuff
-on Linux, general support and help with the program)
+  on Linux, general support and help with the program)
 * link:https://fedoraproject.org/wiki/User:Linuxmodder[Corey Sheldon] (Python, 2Factor/Multi-Factor Auth, QA
-Testing, general mentoring, security, 2nd year mentor)
+  Testing, general mentoring, security, 2nd year mentor)
 * link:https://fedoraproject.org/wiki/User:Skamath[Sachin S. Kamath] (General Linux, Fedora community,
-Metrics, GSoC alumnus, Help with program)
+  Metrics, GSoC alumnus, Help with program)
 * link:https://fedoraproject.org/wiki/User:Bee2502[Bhagyashree(Bee)] ( Fedora community, Metrics, Python,
-past GSoC mentor, Support related to GSoC)
+  past GSoC mentor, Support related to GSoC)
 * link:https://fedoraproject.org/wiki/User:Lsd[Lali Devamanthri] (General development,
-Middleware/Integration, general Linux, Fedora community, GSoC alumnus,
-past GSoC mentor)
+  Middleware/Integration, general Linux, Fedora community, GSoC alumnus,
+  past GSoC mentor)
 * link:https://fedoraproject.org/wiki/User:Devyani7[Devyani Kota] (Fedora community, GSoC Alumnus, General
-Linux, Python, questions related to GSoC)
+  Linux, Python, questions related to GSoC)
 
 [[draft-of-an-idea]]
 === Draft of an idea
diff --git a/modules/ROOT/pages/gsoc/2017/index.adoc b/modules/ROOT/pages/gsoc/2017/index.adoc
index 01ff36a..a4622e9 100644
--- a/modules/ROOT/pages/gsoc/2017/index.adoc
+++ b/modules/ROOT/pages/gsoc/2017/index.adoc
@@ -17,12 +17,12 @@ applications open on 20 March.
 
 * Students
 ** If you're interested in working on an existing project, read up on
-the project and the related technology. There is no need to contact the
-mentor unless you have a specific question about the project. Don't send
-"I'm interested" email.
+   the project and the related technology. There is no need to contact the
+   mentor unless you have a specific question about the project. Don't send
+   "I'm interested" email.
 ** If you're interested in proposing your own project start looking
-around the Fedora Project for a mentor and send your idea to the mailing
-list or post it on the wiki.
+   around the Fedora Project for a mentor and send your idea to the mailing
+   list or post it on the wiki.
 
 Students may also wish to start working on the Fedora specific parts of
 the application (see the application section)
@@ -56,10 +56,10 @@ Working in FOSS gives you a chance to:
 * Collaborate with real engineers and other professionals.
 * Contribute to something meaningful while learning and earning.
 * Learn tools and processes that are just like what you are going to use
-if you work in technology after graduation.
+  if you work in technology after graduation.
 * Make friends and contacts around the globe.
 * Attract attention that can lead to an internship or job after
-graduation.
+  graduation.
 * Create lifetime connections and associations.
 
 [[why-work-with-fedora]]
@@ -97,10 +97,10 @@ Your responsibilities include:
 
 * Communicating early and often with your mentor.
 * Blogging every week about what you're learning, how you're doing,
-challenges and successes. This is key way to keep the entire Fedora
-Community informed.
+  challenges and successes. This is key way to keep the entire Fedora
+  Community informed.
 * Working with your mentor on realistic achievable milestones that
-provide for regular deliverables and feedback.
+  provide for regular deliverables and feedback.
 * Attending a brief monthly student call
 * Being accountable for your success and your actions
 
@@ -126,34 +126,34 @@ consider becoming a Supporting Mentor and helping students across
 projects.
 
 1.  link:http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor[Manual
-on Mentoring]
+    on Mentoring]
 2.  xref:ideas.adoc[Main Idea Page and Supporting
-Mentor List]
+    Mentor List]
 
 [[how-to-work-with-students]]
 === How to work with students
 
 * One way is to provide an idea for students to work on. This idea might
-be very well planned out, in which case you may need a high-level of
-contact with the student to get it implemented correctly. Other ideas
-may be more general and require more planning during onboarding.
+  be very well planned out, in which case you may need a high-level of
+  contact with the student to get it implemented correctly. Other ideas
+  may be more general and require more planning during onboarding.
 
 * It is harder to find success when you are completely certain of how an
-idea needs to be implemented; finding a student with the skills and
-interest to implement a specific solution is a lot harder than finding a
-student with enough skills to respond to a use case need. Also, students
-learn more when they help design and guide the project. In other words,
-provide guidance and direction but let the student do some of the
-"driving."
+  idea needs to be implemented; finding a student with the skills and
+  interest to implement a specific solution is a lot harder than finding a
+  student with enough skills to respond to a use case need. Also, students
+  learn more when they help design and guide the project. In other words,
+  provide guidance and direction but let the student do some of the
+  "driving."
 
 * Where you can have looser ideas, you may be able to find a student who
-works as a sort-of intern who can implement a solution to a use case you
-have. In past experiences, students going after a use case are more
-likely to get somewhere with self-direction and support from you.
+  works as a sort-of intern who can implement a solution to a use case you
+  have. In past experiences, students going after a use case are more
+  likely to get somewhere with self-direction and support from you.
 
 * You may also want to work with a student who brings an idea to your
-sub-project. This requires a different level of communication throughout
-the project, but can be the most rewarding.
+  sub-project. This requires a different level of communication throughout
+  the project, but can be the most rewarding.
 
 [[mentor-responsibilities]]
 === Mentor responsibilities
@@ -165,17 +165,17 @@ Your responsibilities include:
 
 * Being an interface for an identified sub-project or SIG in Fedora.
 * Helping students communicate with the overall project and any
-upstream.
+  upstream.
 * Helping the student plan realistic achievable milestones that provide
-for regular deliverables and feedback.
+  for regular deliverables and feedback.
 * Regular communication with your student. This means you must be
-regularly available for the entire project. If you take a holiday you
-need to know early and help your student be ready for your brief
-absence.
+  regularly available for the entire project. If you take a holiday you
+  need to know early and help your student be ready for your brief
+  absence.
 * Attend a brief monthly mentors call.
 * Be the final, accountable person for deciding if the student is
-successful or not. This is responsibility akin to being a professor or
-boss.
+  successful or not. This is responsibility akin to being a professor or
+  boss.
 
 [[list-of-mentors]]
 === List of Mentors
@@ -195,16 +195,16 @@ Mentors are listed on the xref:ideas.adoc[Main Idea Page and Supporting Mentor L
 == Timeline (Abbreviated)
 
 * Reference:
-https://developers.google.com/open-source/gsoc/timeline[Full Timeline]
+  https://developers.google.com/open-source/gsoc/timeline[Full Timeline]
 
 * *10 October, 2016*: Program announced.
 * *19 January, 2017: 16:00 UTC* Mentoring organizations can begin
-submitting applications to Google.
+  submitting applications to Google.
 * *09 February: 16:00 UTC* Mentoring organization application deadline.
 * *10 - 26 February*: Google program administrators review organization
-applications.
+  applications.
 * *27 February 16:00 UTC* List of accepted mentoring organizations
-published on the Google Summer of Code site.
+  published on the Google Summer of Code site.
 
 Interim Period: Would-be students discuss project ideas with potential
 mentoring organizations.
@@ -232,39 +232,38 @@ Work Period: Mentors give students a helping hand and guidance on their
 projects.
 
 * *26 June: 16:00 UTC* Mentors and students can begin submitting Phase 1
-evaluations.
+  evaluations.
 * *30 June: 16:00 UTC* Phase 1 evaluations deadline; Google begins
-issuing mid-term student payments provided passing student survey is on
-file.
+  issuing mid-term student payments provided passing student survey is on
+  file.
 
 Work Period: Mentors give students a helping hand and guidance on their
 projects.
 
 * *28 July: 16:00 UTC* Phase 2 evaluations deadline.
 * *21 to 29 August: 16:00 UTC*: Final week: Students tidy code, write
-tests, improve documentation and submit their code sample. Students also
-submit their final mentor evaluation.
+  tests, improve documentation and submit their code sample. Students also
+  submit their final mentor evaluation.
 * *29 August*: Mentors can start submitting final student evaluations.
 * *05 September: 16:00 UTC*: Final evaluation deadline
 * *06 September*: Final results of Google Summer of Code 2017 announced
 * *Late October*: Mentor Summit at Google. Mentors and Organization
-Administrators from each participating organization are invited to
-Google for an unconference to collaborate on ideas to make the program
-better and to make new friends too!
+  Administrators from each participating organization are invited to
+  Google for an unconference to collaborate on ideas to make the program
+  better and to make new friends too!
 
 [[ideas-page]]
 == Ideas Page
 
 * *Status :* Open for Ideas +
-* *Link :* xref:ideas.adoc[Summer coding ideas for
-2017]
+* *Link :* xref:ideas.adoc[Summer coding ideas for 2017]
 
 [[links]]
 == Links
 
 1.  link:https://docs.fedoraproject.org/fedora-project/project/fedora-overview.html[The Four Foundations of Fedora]
 2.  link:https://developers.google.com/open-source/gsoc/resources/[Official
-GSoC Resources]
+    GSoC Resources]
 3.  link:http://docs.fedoraproject.org/en-US/index.html[Fedora Documentation]
 4.  link:https://fedoraproject.org/wiki/Communicate/IRCHowTo[IRC]
 5.  link:https://fedoraproject.org/wiki/Development[Development]
diff --git a/modules/ROOT/pages/gsoc/2018/application.adoc b/modules/ROOT/pages/gsoc/2018/application.adoc
index cc1d6d8..73035df 100644
--- a/modules/ROOT/pages/gsoc/2018/application.adoc
+++ b/modules/ROOT/pages/gsoc/2018/application.adoc
@@ -12,9 +12,9 @@ by the deadline. Late applications cannot be accepted.
 
 * Timelines are set by Google for the entire program.  Follow the timeline.
 * Applications are due in Google's system by March 27, 2018 18:00
-(CEST).
+  (CEST).
 * Applications Must be filed in the Google system.  No other
-material can be read or accepted.
+  material can be read or accepted.
 * The final application is required to be submitted as a PDF.
 
 == Student Application Process
@@ -36,9 +36,9 @@ this is a great way to understand the needs of the project and find a
 mentor.
 
 * https://lists.fedoraproject.org/admin/lists/summer-coding.lists.fedoraproject.org[the
-summer-coding list]
+  summer-coding list]
 * https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org[the
-development list].
+  development list].
 
 Don't forget to contact mentors on projects that interest you to learn
 more. If you're going to propose a project you must have a mentor at the
@@ -73,48 +73,48 @@ In addition to the information Google requests, the Fedora Project
 requires you to submit the following information:
 
 * What project are you applying to? Seriously consider choosing a
-project for proposal from xref:ideas.adoc[ideas list].  While it is
-possible to propose your own project, it is often more successful for
-you to select one that is already proposed by a mentor.
+  project for proposal from xref:ideas.adoc[ideas list].  While it is
+  possible to propose your own project, it is often more successful for
+  you to select one that is already proposed by a mentor.
 
 * Contact Information
 ** List your Name, Email Address, Blog URL, and any additional contact
-information you think we need. We tend to email so be sure you're
-reading your email.
+   information you think we need. We tend to email so be sure you're
+   reading your email.
 
 * About You - Consider these questions
 ** Do you have any past involvement with the Fedora Project or another
-open-source project as a contributor? What kind of contributions have
-you made (code and non-code)? Please share any public contributions you
-have made (urls, etc.)
+   open-source project as a contributor? What kind of contributions have
+   you made (code and non-code)? Please share any public contributions you
+   have made (urls, etc.)
 ** What are you studying? Why?
 ** What motivates you to do your best? How do you stay focused? Briefly
-describe how you organize your work.
+   describe how you organize your work.
 
 * Why Us? - Consider these questions
 ** Why do you want to work with the Fedora Project?
 ** Do you plan to continue contributing to the Fedora Project after
-GSoC? If yes, what sub-project(s) are you interested with?
+   GSoC? If yes, what sub-project(s) are you interested with?
 
 * Why This Project? - Consider these questions
 ** Which specific project interests you? If you are proposing your own
-project, do it here. If you are proposing the project, explain why it
-benefits the community.
+   project, do it here. If you are proposing the project, explain why it
+   benefits the community.
 ** Have you contacted the mentor(s) listed for the project?
 ** What relevant experience do you have for this project?
 ** What do you want to gain from this project?
 ** Describe this project in your own words. What does it mean to you?
-What do you think the final deliverable is?
+   What do you think the final deliverable is?
 
 * Why should we choose you over other applicants?
 
 * Propose a rough schedule for this project. Ideally you will have
-regular deliverables throughout the entire period.
+  regular deliverables throughout the entire period.
 
 * What are you specific plans from May to September (eg: Exams in
-university, internships, vacations..etc). We need to know if there are
-periods of time where you are likely to be unavailable. We are better at
-accommodating these periods if we know of them in advance.
+  university, internships, vacations..etc). We need to know if there are
+  periods of time where you are likely to be unavailable. We are better at
+  accommodating these periods if we know of them in advance.
 
 [NOTE]
 --
diff --git a/modules/ROOT/pages/gsoc/2018/ideas.adoc b/modules/ROOT/pages/gsoc/2018/ideas.adoc
index 20dec6b..fe834cb 100644
--- a/modules/ROOT/pages/gsoc/2018/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2018/ideas.adoc
@@ -25,11 +25,11 @@ or task.
 add yourselves and your wiki page).
 
 * link:https://fedoraproject.org/wiki/User:Bex[Brian (bex) Exelbierd] (Fedora Community Action and Impact
-Coordinator, FCAIC, 🎂, containers, general development, general Linux)
+  Coordinator, FCAIC, 🎂, containers, general development, general Linux)
 * link:https://fedoraproject.org/wiki/User:Jflory7[Justin W. Flory] (General development, general Linux,
-Fedora community, GSoC alumnus, questions about program, misc. advice)
+  Fedora community, GSoC alumnus, questions about program, misc. advice)
 * link:https://fedoraproject.org/wiki/User:Skamath[Sachin S. Kamath] (Python Dev, General Linux, Fedora community,
-Metrics, GSoC alumnus, Help with program)
+  Metrics, GSoC alumnus, Help with program)
 * link:https://fedoraproject.org/wiki/User:Mbriza[Martin Bříza]
 
 == Idea list
@@ -243,7 +243,7 @@ A daemon to manage this state is required. The daemon would need to be able to d
 There needs to be a means of specifying what components are critical to the successful operation of the device. Some components will be the same across all types of device such as the ability to check network interfaces are operating, to check an update service is available, to check services are available etc but some might be plugins eg to check GPIO is working, specific IIO sensors, cameras or other such things are seen as expected.
 
 - What are we looking for:
-An initial daemon with basic functionality with good design that can be extended. Integration with atomic updates etc.
+  An initial daemon with basic functionality with good design that can be extended. Integration with atomic updates etc.
 
 '''
 
diff --git a/modules/ROOT/pages/gsoc/2018/index.adoc b/modules/ROOT/pages/gsoc/2018/index.adoc
index da73787..013892d 100644
--- a/modules/ROOT/pages/gsoc/2018/index.adoc
+++ b/modules/ROOT/pages/gsoc/2018/index.adoc
@@ -38,13 +38,13 @@ NOTE: Student applications **are not yet open**.
 ////
 
 * If you're interested in working on an existing project, read up on
-the project and the related technology. There is no need to contact the
-mentor unless you have a specific question about the project. Don't send
-an "I'm interested" email.
+  the project and the related technology. There is no need to contact the
+  mentor unless you have a specific question about the project. Don't send
+  an "I'm interested" email.
 
 * If you're interested in proposing your own project start looking
-around the Fedora Project for a mentor and send your idea to the mailing
-list or post it on the wiki.
+  around the Fedora Project for a mentor and send your idea to the mailing
+  list or post it on the wiki.
 
 ////
 * If you're interested in working on a mentor-submitted idea, read
@@ -60,8 +60,8 @@ xref:ideas.adoc[ideas page].
 
 
 * You may also wish to start working on the Fedora specific parts of
-the application, see below for more information. Carefully review the
-student responsibilities section.
+  the application, see below for more information. Carefully review the
+  student responsibilities section.
 
 [[why-spend-your-summer-working-on-foss]]
 === Why spend your summer working on FOSS?
@@ -78,10 +78,10 @@ Working in FOSS gives you a chance to:
 * Collaborate with real engineers and other professionals.
 * Contribute to something meaningful while learning and earning.
 * Learn tools and processes that are just like what you are going to use
-if you work in technology after graduation.
+  if you work in technology after graduation.
 * Make friends and contacts around the globe.
 * Attract attention that can lead to an internship or job after
-graduation.
+  graduation.
 * Create lifetime connections and associations.
 
 [[why-work-with-fedora]]
@@ -127,10 +127,10 @@ Your responsibilities include:
 
 * Communicating early and often with your mentor.
 * Blogging every week about what you're learning, how you're doing,
-challenges and successes. This is key way to keep the entire Fedora
-Community informed.
+  challenges and successes. This is key way to keep the entire Fedora
+  Community informed.
 * Working with your mentor on realistic achievable milestones that
-provide for regular deliverables and feedback.
+  provide for regular deliverables and feedback.
 * Attending the brief student calls, as announced
 * Being accountable for your success and your actions
 
@@ -157,21 +157,21 @@ more people than just you.
 If you want to mentor a specific project, think carefully about several things:
 
 1. Do you have enough time to work on this with the student during the
-entire project.  You will be helping someone else when they get stuck.
-You don't want to become a blocker because you're busy.
+   entire project.  You will be helping someone else when they get stuck.
+   You don't want to become a blocker because you're busy.
 
 2. It is harder to find success when you are completely certain of how an
-idea needs to be implemented; finding a student with the skills and
-interest to implement a specific solution is a lot harder than finding
-a student with enough skills to respond to a use case need. Also,
-students learn more when they help design and guide the project. In
-other words, provide guidance and direction but let the student do
-some of the "driving."
+   idea needs to be implemented; finding a student with the skills and
+   interest to implement a specific solution is a lot harder than finding
+   a student with enough skills to respond to a use case need. Also,
+   students learn more when they help design and guide the project. In
+   other words, provide guidance and direction but let the student do
+   some of the "driving."
 
 3. Where you can have looser ideas, you may be able to find a student
-who works as a sort-of intern who can implement a solution to a use
-case you have. In past experiences, students going after a use case are
-more likely to get somewhere with self-direction and support from you.
+   who works as a sort-of intern who can implement a solution to a use
+   case you have. In past experiences, students going after a use case are
+   more likely to get somewhere with self-direction and support from you.
 
 4. Who can help you?  Try to find a second mentor for the project.
 
@@ -187,21 +187,21 @@ to help with mentoring and to solicit feedback on your proposal
 Yes!  You can either:
 
 * Work with a student who brings an idea to your sub-project. This
-requires a different level of communication throughout the project,
-but can be the most rewarding.
+  requires a different level of communication throughout the project,
+  but can be the most rewarding.
 
 * Be a general mentor.  This is a person who works with all students
-regardless of their project.  To become a general mentor please open
-an issue in the https://pagure.io/mentored-projects/issues[Mentored
-Projects Issue Tracker] offering your help.  Please tag the issue with
-the *GSoC* tag.
+  regardless of their project.  To become a general mentor please open
+  an issue in the https://pagure.io/mentored-projects/issues[Mentored
+  Projects Issue Tracker] offering your help.  Please tag the issue with
+  the *GSoC* tag.
 
 [[how-to-work-with-students]]
 === How to work with students
 
 * Read about good mentoring in the
-link:http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor[Manual
-on Mentoring]
+  link:http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor[Manual
+  on Mentoring]
 
 [[mentor-responsibilities]]
 Mentor responsibilities
@@ -214,17 +214,17 @@ Your responsibilities include:
 
 * Being an interface for an identified sub-project or SIG in Fedora.
 * Helping students communicate with the overall project and any
-upstream.
+  upstream.
 * Helping the student plan realistic achievable milestones that provide
-for regular deliverables and feedback.
+  for regular deliverables and feedback.
 * Regular communication with your student. This means you must be
-regularly available for the entire project. If you take a holiday you
-need to know early and help your student be ready for your brief
-absence.
+  regularly available for the entire project. If you take a holiday you
+  need to know early and help your student be ready for your brief
+  absence.
 * Attending a brief mentors call, as scheduled.
 * Be the final, accountable person for deciding if the student is
-successful or not. This is responsibility akin to being a professor or
-boss.
+  successful or not. This is responsibility akin to being a professor or
+  boss.
 
 [[communication]]
 == Communication
diff --git a/modules/ROOT/pages/gsoc/2019/application.adoc b/modules/ROOT/pages/gsoc/2019/application.adoc
index 5101f28..d8a6121 100644
--- a/modules/ROOT/pages/gsoc/2019/application.adoc
+++ b/modules/ROOT/pages/gsoc/2019/application.adoc
@@ -18,9 +18,9 @@ by the deadline. Late applications cannot be accepted.
 
 * Timelines are set by Google for the entire program.  Follow the timeline.
 * Applications are due in Google's system by April 9th, 2019 18:00
-(CEST).
+  (CEST).
 * Applications Must be filed in the Google system.  No other
-material can be read or accepted.
+  material can be read or accepted.
 * The final application is required to be submitted as a PDF.
 
 == Student Application Process
@@ -42,9 +42,9 @@ this is a great way to understand the needs of the project and find a
 mentor.
 
 * https://lists.fedoraproject.org/admin/lists/summer-coding.lists.fedoraproject.org[the
-summer-coding list]
+  summer-coding list]
 * https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org[the
-development list].
+  development list].
 
 Don't forget to contact mentors on projects that interest you to learn
 more. If you're going to propose a project you must have a mentor at the
@@ -81,48 +81,48 @@ In addition to the information Google requests, the Fedora Project
 requires you to submit the following information:
 
 * What project are you applying to? Seriously consider choosing a
-project for proposal from xref:gsoc/2019/ideas.adoc[ideas list].  While it is
-possible to propose your own project, it is often more successful for
-you to select one that is already proposed by a mentor.
+  project for proposal from xref:gsoc/2019/ideas.adoc[ideas list].  While it is
+  possible to propose your own project, it is often more successful for
+  you to select one that is already proposed by a mentor.
 
 * Contact Information
 ** List your Name, Email Address, Blog URL, and any additional contact
-information you think we need. We tend to email so be sure you're
-reading your email.
+   information you think we need. We tend to email so be sure you're
+   reading your email.
 
 * About You - Consider these questions
 ** Do you have any past involvement with the Fedora Project or another
-open-source project as a contributor? What kind of contributions have
-you made (code and non-code)? Please share any public contributions you
-have made (urls, etc.)
+   open-source project as a contributor? What kind of contributions have
+   you made (code and non-code)? Please share any public contributions you
+   have made (urls, etc.)
 ** What are you studying? Why?
 ** What motivates you to do your best? How do you stay focused? Briefly
-describe how you organize your work.
+   describe how you organize your work.
 
 * Why Us? - Consider these questions
 ** Why do you want to work with the Fedora Project?
 ** Do you plan to continue contributing to the Fedora Project after
-GSoC? If yes, what sub-project(s) are you interested with?
+   GSoC? If yes, what sub-project(s) are you interested with?
 
 * Why This Project? - Consider these questions
 ** Which specific project interests you? If you are proposing your own
-project, do it here. If you are proposing the project, explain why it
-benefits the community.
+   project, do it here. If you are proposing the project, explain why it
+   benefits the community.
 ** Have you contacted the mentor(s) listed for the project?
 ** What relevant experience do you have for this project?
 ** What do you want to gain from this project?
 ** Describe this project in your own words. What does it mean to you?
-What do you think the final deliverable is?
+   What do you think the final deliverable is?
 
 * Why should we choose you over other applicants?
 
 * Propose a rough schedule for this project. Ideally you will have
-regular deliverables throughout the entire period.
+  regular deliverables throughout the entire period.
 
 * What are you specific plans from May to September (eg: Exams in
-university, internships, vacations..etc). We need to know if there are
-periods of time where you are likely to be unavailable. We are better at
-accommodating these periods if we know of them in advance.
+  university, internships, vacations..etc). We need to know if there are
+  periods of time where you are likely to be unavailable. We are better at
+  accommodating these periods if we know of them in advance.
 
 [NOTE]
 --
diff --git a/modules/ROOT/pages/gsoc/2019/ideas.adoc b/modules/ROOT/pages/gsoc/2019/ideas.adoc
index 2443135..f502b55 100644
--- a/modules/ROOT/pages/gsoc/2019/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2019/ideas.adoc
@@ -28,9 +28,9 @@ or task.
 add yourselves and your wiki page).
 
 * link:https://fedoraproject.org/wiki/User:Bex[Brian (bex) Exelbierd] (Fedora Community Action and Impact
-Coordinator, FCAIC, 🎂, containers, general development, general Linux)
+  Coordinator, FCAIC, 🎂, containers, general development, general Linux)
 * link:https://fedoraproject.org/wiki/User:Sumantrom[Sumantro Mukherjee] (General development, general Linux,
-Fedora community, GSoC alumnus, questions about program, misc. advice)
+  Fedora community, GSoC alumnus, questions about program, misc. advice)
 * link:https://fedoraproject.org/wiki/User:Bt0dotninja[Alberto] (Commops/Fedora-Join/Marketing teams)
 
 == Idea list
@@ -49,7 +49,7 @@ NOTE: Ideas are subject to change as additional mentors are onboarded.
 - Technology : HTML5, CSS3, Angular, Javascript, TBD.
 - Mentor :  https://fedoraproject.org/wiki/User:Bstinson[Brian Stinson], https://fedoraproject.org/wiki/User:Siddharthvipul1[Vipul Siddharth]
 - IRC & Email : Brian Stinson [IRC: bstinson, bstinson@redhat.com],
-Vipul Siddharth [IRC: siddharthvipul, vsiddhar@redhat.com]
+  Vipul Siddharth [IRC: siddharthvipul, vsiddhar@redhat.com]
 
 
 ==== Description
@@ -185,7 +185,7 @@ As a GSoC intern you will be responsible for :
 - Difficulty : Intermediate
 - Technology :   Python
 - Mentor :  Rado Pitonak [IRC rpitonak, mail: rpitonak@redhat.com] ,
-Tomas Tomecek [IRC ttomecek, mail: ttomecek@redhat.com]
+  Tomas Tomecek [IRC ttomecek, mail: ttomecek@redhat.com]
 
 ==== Description
 
diff --git a/modules/ROOT/pages/gsoc/2019/index.adoc b/modules/ROOT/pages/gsoc/2019/index.adoc
index 0fbbf08..03a0fa6 100644
--- a/modules/ROOT/pages/gsoc/2019/index.adoc
+++ b/modules/ROOT/pages/gsoc/2019/index.adoc
@@ -36,18 +36,18 @@ distributions? GSoC could be your chance. Please refer to the information
 below.
 
 * If you're interested in working on a mentor-submitted idea, read
-the xref:gsoc/2019/ideas.adoc[ideas page] and about the project and the related
-technology. There is no need to contact the mentor unless you have a
-specific question about the project. Don't send an "I'm interested" email.
+  the xref:gsoc/2019/ideas.adoc[ideas page] and about the project and the related
+  technology. There is no need to contact the mentor unless you have a
+  specific question about the project. Don't send an "I'm interested" email.
 
 * If you're interested in proposing your own project start looking
-around the Fedora Project for a mentor and send your idea to the mailing
-list or post it on the wiki. A list of potential mentors is also on the
-xref:gsoc/2019/ideas.adoc[ideas page].
+  around the Fedora Project for a mentor and send your idea to the mailing
+  list or post it on the wiki. A list of potential mentors is also on the
+  xref:gsoc/2019/ideas.adoc[ideas page].
 
 * You may also wish to start working on the Fedora specific parts of
-the application, see below for more information. Carefully review the
-student responsibilities section.
+  the application, see below for more information. Carefully review the
+  student responsibilities section.
 
 [[why-spend-your-summer-working-on-foss]]
 === Why spend your summer working on FOSS?
@@ -64,10 +64,10 @@ Working in FOSS gives you a chance to:
 * Collaborate with real engineers and other professionals.
 * Contribute to something meaningful while learning and earning.
 * Learn tools and processes that are just like what you are going to use
-if you work in technology after graduation.
+  if you work in technology after graduation.
 * Make friends and contacts around the globe.
 * Attract attention that can lead to an internship or job after
-graduation.
+  graduation.
 * Create lifetime connections and associations.
 
 [[why-work-with-fedora]]
@@ -113,10 +113,10 @@ Your responsibilities include:
 
 * Communicating early and often with your mentor.
 * Blogging every week about what you're learning, how you're doing,
-challenges and successes. This is key way to keep the entire Fedora
-Community informed.
+  challenges and successes. This is key way to keep the entire Fedora
+  Community informed.
 * Working with your mentor on realistic achievable milestones that
-provide for regular deliverables and feedback.
+  provide for regular deliverables and feedback.
 * Attending the brief student calls, as announced
 * Being accountable for your success and your actions
 
@@ -143,21 +143,21 @@ more people than just you.
 If you want to mentor a specific project, think carefully about several things:
 
 1. Do you have enough time to work on this with the student during the
-entire project.  You will be helping someone else when they get stuck.
-You don't want to become a blocker because you're busy.
+   entire project.  You will be helping someone else when they get stuck.
+   You don't want to become a blocker because you're busy.
 
 2. It is harder to find success when you are completely certain of how an
-idea needs to be implemented; finding a student with the skills and
-interest to implement a specific solution is a lot harder than finding
-a student with enough skills to respond to a use case need. Also,
-students learn more when they help design and guide the project. In
-other words, provide guidance and direction but let the student do
-some of the "driving."
+   idea needs to be implemented; finding a student with the skills and
+   interest to implement a specific solution is a lot harder than finding
+   a student with enough skills to respond to a use case need. Also,
+   students learn more when they help design and guide the project. In
+   other words, provide guidance and direction but let the student do
+   some of the "driving."
 
 3. Where you can have looser ideas, you may be able to find a student
-who works as a sort-of intern who can implement a solution to a use
-case you have. In past experiences, students going after a use case are
-more likely to get somewhere with self-direction and support from you.
+   who works as a sort-of intern who can implement a solution to a use
+   case you have. In past experiences, students going after a use case are
+   more likely to get somewhere with self-direction and support from you.
 
 4. Who can help you?  Try to find a second mentor for the project.
 
@@ -173,21 +173,21 @@ to help with mentoring and to solicit feedback on your proposal
 Yes!  You can either:
 
 * Work with a student who brings an idea to your sub-project. This
-requires a different level of communication throughout the project,
-but can be the most rewarding.
+  requires a different level of communication throughout the project,
+  but can be the most rewarding.
 
 * Be a general mentor.  This is a person who works with all students
-regardless of their project.  To become a general mentor please open
-an issue in the https://pagure.io/mentored-projects/issues[Mentored
-Projects Issue Tracker] offering your help.  Please tag the issue with
-the *GSoC* tag.
+  regardless of their project.  To become a general mentor please open
+  an issue in the https://pagure.io/mentored-projects/issues[Mentored
+  Projects Issue Tracker] offering your help.  Please tag the issue with
+  the *GSoC* tag.
 
 [[how-to-work-with-students]]
 === How to work with students
 
 * Read about good mentoring in the
-link:http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor[Manual
-on Mentoring]
+  link:http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor[Manual
+  on Mentoring]
 
 [[mentor-responsibilities]]
 Mentor responsibilities
@@ -200,17 +200,17 @@ Your responsibilities include:
 
 * Being an interface for an identified sub-project or SIG in Fedora.
 * Helping students communicate with the overall project and any
-upstream.
+  upstream.
 * Helping the student plan realistic achievable milestones that provide
-for regular deliverables and feedback.
+  for regular deliverables and feedback.
 * Regular communication with your student. This means you must be
-regularly available for the entire project. If you take a holiday you
-need to know early and help your student be ready for your brief
-absence.
+  regularly available for the entire project. If you take a holiday you
+  need to know early and help your student be ready for your brief
+  absence.
 * Attending a brief mentors call, as scheduled.
 * Be the final, accountable person for deciding if the student is
-successful or not. This is responsibility akin to being a professor or
-boss.
+  successful or not. This is responsibility akin to being a professor or
+  boss.
 
 [[communication]]
 == Communication
diff --git a/modules/ROOT/pages/gsoc/2020/application.adoc b/modules/ROOT/pages/gsoc/2020/application.adoc
index 5ee79d6..4be39b0 100644
--- a/modules/ROOT/pages/gsoc/2020/application.adoc
+++ b/modules/ROOT/pages/gsoc/2020/application.adoc
@@ -15,9 +15,9 @@ by the deadline. Late applications cannot be accepted.
 
 * Timelines are set by Google for the entire program.  Follow the timeline.
 * Applications are due in Google's system by March 31st, 2020 18:00
-(UTC).
+  (UTC).
 * Applications Must be filed in the Google system.  No other
-material can be read or accepted.
+  material can be read or accepted.
 * The final application is required to be submitted as a PDF.
 
 == Student Application Process
@@ -39,9 +39,9 @@ this is a great way to understand the needs of the project and find a
 mentor.
 
 * https://lists.fedoraproject.org/admin/lists/summer-coding.lists.fedoraproject.org[the
-summer-coding list]
+  summer-coding list]
 * https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org[the
-development list].
+  development list].
 
 Don't forget to contact mentors on projects that interest you to learn
 more. If you're going to propose a project you must have a mentor at the
@@ -78,48 +78,48 @@ In addition to the information Google requests, the Fedora Project
 requires you to submit the following information:
 
 * What project are you applying to? Seriously consider choosing a
-project for proposal from xref:gsoc/2020/ideas.adoc[ideas list].  While it is
-possible to propose your own project, it is often more successful for
-you to select one that is already proposed by a mentor.
+  project for proposal from xref:gsoc/2020/ideas.adoc[ideas list].  While it is
+  possible to propose your own project, it is often more successful for
+  you to select one that is already proposed by a mentor.
 
 * Contact Information
 ** List your Name, Email Address, Blog URL, and any additional contact
-information you think we need. We tend to email so be sure you're
-reading your email.
+   information you think we need. We tend to email so be sure you're
+   reading your email.
 
 * About You - Consider these questions
 ** Do you have any past involvement with the Fedora Project or another
-open-source project as a contributor? What kind of contributions have
-you made (code and non-code)? Please share any public contributions you
-have made (urls, etc.)
+   open-source project as a contributor? What kind of contributions have
+   you made (code and non-code)? Please share any public contributions you
+   have made (urls, etc.)
 ** What are you studying? Why?
 ** What motivates you to do your best? How do you stay focused? Briefly
-describe how you organize your work.
+   describe how you organize your work.
 
 * Why Us? - Consider these questions
 ** Why do you want to work with the Fedora Project?
 ** Do you plan to continue contributing to the Fedora Project after
-GSoC? If yes, what sub-project(s) are you interested with?
+   GSoC? If yes, what sub-project(s) are you interested with?
 
 * Why This Project? - Consider these questions
 ** Which specific project interests you? If you are proposing your own
-project, do it here. If you are proposing the project, explain why it
-benefits the community.
+   project, do it here. If you are proposing the project, explain why it
+   benefits the community.
 ** Have you contacted the mentor(s) listed for the project?
 ** What relevant experience do you have for this project?
 ** What do you want to gain from this project?
 ** Describe this project in your own words. What does it mean to you?
-What do you think the final deliverable is?
+   What do you think the final deliverable is?
 
 * Why should we choose you over other applicants?
 
 * Propose a rough schedule for this project. Ideally you will have
-regular deliverables throughout the entire period.
+  regular deliverables throughout the entire period.
 
 * What are you specific plans from May to September (eg: Exams in
-university, internships, vacations..etc). We need to know if there are
-periods of time where you are likely to be unavailable. We are better at
-accommodating these periods if we know of them in advance.
+  university, internships, vacations..etc). We need to know if there are
+  periods of time where you are likely to be unavailable. We are better at
+  accommodating these periods if we know of them in advance.
 
 [NOTE]
 --
diff --git a/modules/ROOT/pages/gsoc/2020/ideas.adoc b/modules/ROOT/pages/gsoc/2020/ideas.adoc
index 59fdadf..913e397 100644
--- a/modules/ROOT/pages/gsoc/2020/ideas.adoc
+++ b/modules/ROOT/pages/gsoc/2020/ideas.adoc
@@ -29,7 +29,7 @@ add yourselves and your wiki page).
 
 
 * link:https://fedoraproject.org/wiki/User:Sumantrom[Sumantro Mukherjee] (General development, general Linux,
-Fedora community, GSoC alumnus, questions about program, misc. advice)
+  Fedora community, GSoC alumnus, questions about program, misc. advice)
 * link:https://fedoraproject.org/wiki/User:Siddharthvipul1[Vipul Siddharth] (Fedora CI,GCI,GSoC,general linux,Fedora community, misc.)
 
 == Idea list
diff --git a/modules/ROOT/pages/gsoc/2020/index.adoc b/modules/ROOT/pages/gsoc/2020/index.adoc
index 2c3ef3a..909cede 100644
--- a/modules/ROOT/pages/gsoc/2020/index.adoc
+++ b/modules/ROOT/pages/gsoc/2020/index.adoc
@@ -37,18 +37,18 @@ distributions? GSoC could be your chance. Please refer to the information
 below.
 
 * If you're interested in working on a mentor-submitted idea, read
-the xref:gsoc/2020/ideas.adoc[ideas page] and about the project and the related
-technology. There is no need to contact the mentor unless you have a
-specific question about the project. Don't send an "I'm interested" email.
+  the xref:gsoc/2020/ideas.adoc[ideas page] and about the project and the related
+  technology. There is no need to contact the mentor unless you have a
+  specific question about the project. Don't send an "I'm interested" email.
 
 * If you're interested in proposing your own project start looking
-around the Fedora Project for a mentor and send your idea to the mailing
-list or post it on the wiki. A list of potential mentors is also on the
-xref:gsoc/2019/ideas.adoc[ideas page].
+  around the Fedora Project for a mentor and send your idea to the mailing
+  list or post it on the wiki. A list of potential mentors is also on the
+  xref:gsoc/2019/ideas.adoc[ideas page].
 
 * You may also wish to start working on the Fedora specific parts of
-the application, see below for more information. Carefully review the
-student responsibilities section.
+  the application, see below for more information. Carefully review the
+  student responsibilities section.
 
 [[why-spend-your-summer-working-on-foss]]
 === Why spend your summer working on FOSS?
@@ -65,10 +65,10 @@ Working in FOSS gives you a chance to:
 * Collaborate with real engineers and other professionals.
 * Contribute to something meaningful while learning and earning.
 * Learn tools and processes that are just like what you are going to use
-if you work in technology after graduation.
+  if you work in technology after graduation.
 * Make friends and contacts around the globe.
 * Attract attention that can lead to an internship or job after
-graduation.
+  graduation.
 * Create lifetime connections and associations.
 
 [[why-work-with-fedora]]
@@ -114,10 +114,10 @@ Your responsibilities include:
 
 * Communicating early and often with your mentor.
 * Blogging every week about what you're learning, how you're doing,
-challenges and successes. This is key way to keep the entire Fedora
-Community informed.
+  challenges and successes. This is key way to keep the entire Fedora
+  Community informed.
 * Working with your mentor on realistic achievable milestones that
-provide for regular deliverables and feedback.
+  provide for regular deliverables and feedback.
 * Attending the brief student calls, as announced
 * Being accountable for your success and your actions
 
@@ -144,21 +144,21 @@ more people than just you.
 If you want to mentor a specific project, think carefully about several things:
 
 1. Do you have enough time to work on this with the student during the
-entire project.  You will be helping someone else when they get stuck.
-You don't want to become a blocker because you're busy.
+   entire project.  You will be helping someone else when they get stuck.
+   You don't want to become a blocker because you're busy.
 
 2. It is harder to find success when you are completely certain of how an
-idea needs to be implemented; finding a student with the skills and
-interest to implement a specific solution is a lot harder than finding
-a student with enough skills to respond to a use case need. Also,
-students learn more when they help design and guide the project. In
-other words, provide guidance and direction but let the student do
-some of the "driving."
+   idea needs to be implemented; finding a student with the skills and
+   interest to implement a specific solution is a lot harder than finding
+   a student with enough skills to respond to a use case need. Also,
+   students learn more when they help design and guide the project. In
+   other words, provide guidance and direction but let the student do
+   some of the "driving."
 
 3. Where you can have looser ideas, you may be able to find a student
-who works as a sort-of intern who can implement a solution to a use
-case you have. In past experiences, students going after a use case are
-more likely to get somewhere with self-direction and support from you.
+   who works as a sort-of intern who can implement a solution to a use
+   case you have. In past experiences, students going after a use case are
+   more likely to get somewhere with self-direction and support from you.
 
 4. Who can help you?  Try to find a second mentor for the project.
 
@@ -174,21 +174,21 @@ to help with mentoring and to solicit feedback on your proposal
 Yes!  You can either:
 
 * Work with a student who brings an idea to your sub-project. This
-requires a different level of communication throughout the project,
-but can be the most rewarding.
+  requires a different level of communication throughout the project,
+  but can be the most rewarding.
 
 * Be a general mentor.  This is a person who works with all students
-regardless of their project.  To become a general mentor please open
-an issue in the https://pagure.io/mentored-projects/issues[Mentored
-Projects Issue Tracker] offering your help.  Please tag the issue with
-the *GSoC* tag.
+  regardless of their project.  To become a general mentor please open
+  an issue in the https://pagure.io/mentored-projects/issues[Mentored
+  Projects Issue Tracker] offering your help.  Please tag the issue with
+  the *GSoC* tag.
 
 [[how-to-work-with-students]]
 === How to work with students
 
 * Read about good mentoring in the
-link:http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor[Manual
-on Mentoring]
+  link:http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor[Manual
+  on Mentoring]
 
 [[mentor-responsibilities]]
 Mentor responsibilities
@@ -201,17 +201,17 @@ Your responsibilities include:
 
 * Being an interface for an identified sub-project or SIG in Fedora.
 * Helping students communicate with the overall project and any
-upstream.
+  upstream.
 * Helping the student plan realistic achievable milestones that provide
-for regular deliverables and feedback.
+  for regular deliverables and feedback.
 * Regular communication with your student. This means you must be
-regularly available for the entire project. If you take a holiday you
-need to know early and help your student be ready for your brief
-absence.
+  regularly available for the entire project. If you take a holiday you
+  need to know early and help your student be ready for your brief
+  absence.
 * Attending a brief mentors call, as scheduled.
 * Be the final, accountable person for deciding if the student is
-successful or not. This is responsibility akin to being a professor or
-boss.
+  successful or not. This is responsibility akin to being a professor or
+  boss.
 
 [[communication]]
 == Communication

