GitBook: [master] 3 pages modified

Author: damianlegawiec

customization/authentication.md

@@ -81,12 +81,11 @@ module Spree
 end
 ```
 
-In your `ApplicationController` add those lines:
+In your `ApplicationController` add these lines:
 
 ```ruby
 include Spree::AuthenticationHelpers
 include Spree::Core::ControllerHelpers::Auth
-include Spree::Core::ControllerHelpers::Common
 include Spree::Core::ControllerHelpers::Order
 include Spree::Core::ControllerHelpers::Store
 include Spree::Core::ControllerHelpers::Currency
@@ -96,8 +95,6 @@ helper 'spree/base'
 helper 'spree/locale', 'spree/currency', 'spree/store'
 ```
 
-Please note that including `Spree::Core::ControllerHelpers::Common` will replace your application layout with [Spree layout](https://github.com/spree/spree/blob/master/frontend/app/views/spree/layouts/spree_application.html.erb). For applications not wanting to use Spree layout omit the `Spree::Core::ControllerHelpers::Common` module.
-
 Each of the methods defined in this module return values that are the most common in Rails applications today, but you may need to customize them. In order, they are:
 
 * `spree_current_user` Used to tell Spree what the current user
@@ -172,7 +169,7 @@ Finally, if you are using the API component of Spree, there are more methods add
 
  This is only applicable for Spree 4.0 and older. Spree 4.1 and newer releases handle this out of the box.
 
-To make the login link appear on Spree pages, you will need to modify `spree/shared/_nav_bar.html.erb` file which you can copy over from Spree codebase to your project \(detailed in [View Customization section](/developer/customization/view.html)\).
+To make the login link appear on Spree pages, you will need to modify `spree/shared/_nav_bar.html.erb` file which you can copy over from Spree codebase to your project \(detailed in [Storefront Customization section](storefront.md)\).
 
 You will need to add this code:
 

customization/checkout.md

@@ -45,7 +45,7 @@ def check_registration
 end
 ```
 
-The configuration of the guest checkout option is done via [Preferences](/developer/internals/preferences.html). Spree will allow guest checkout by default. Use the `allow_guest_checkout` preference to change the default setting.
+The configuration of the guest checkout option is done via [Preferences](../internals/preferences.md). Spree will allow guest checkout by default. Use the `allow_guest_checkout` preference to change the default setting.
 
 ### Address Information
 
@@ -75,7 +75,7 @@ If you do not want to use a gateway with payment profiles then you will need to
 
  Spree discards the credit card number after this step is processed. If you do not have a gateway with payment profiles enabled then your card information will be lost before it's time to authorize the card.
 
-For more information about payments, please see the [Payments guide](/developer/internals/payments.html).
+For more information about payments, please see the [Payments guide](../internals/payments.md).
 
 ### Confirmation
 
@@ -249,7 +249,7 @@ en:
 
 ## Payment Profiles
 
-The default checkout process in Spree assumes a gateway that allows for some form of third party support for payment profiles. An example of such a service would be [Authorize.net CIM](https://www.authorize.net/our-features/secure-customer-data.html) Such a service allows for a secure and PCI compliant means of storing the users credit card information. This allows merchants to issue refunds to the credit card or to make changes to an existing order without having to leave Spree and use the gateway provider's website. More importantly, it allows us to have a final "confirmation" step before the order is processed since the number is stored securely on the payment step and can still be used to perform the standard authorization/capture via the secure token provided by the gateway.
+The default checkout process in Spree assumes a gateway that allows for some form of third-party support for payment profiles. An example of such a service would be [Authorize.net CIM](https://www.authorize.net/our-features/secure-customer-data.html) Such a service allows for a secure and PCI-compliant means of storing the user's credit card information. This allows merchants to issue refunds to the credit card or to make changes to an existing order without having to leave Spree and use the gateway provider's website. More importantly, it allows us to have a final "confirmation" step before the order is processed since the number is stored securely on the payment step and can still be used to perform the standard authorization/capture via the secure token provided by the gateway.
 
 Spree provides a wrapper around the standard active merchant API in order to provide a common abstraction for dealing with payment profiles. All `Gateway` classes now have a `payment_profiles_supported?` method which indicates whether or not payment profiles are supported. If you are adding Spree support to a `Gateway` you should also implement the `create_profile` method. The following is an example of the implementation of `create_profile` used in the `AuthorizeNetCim` class:
 

customization/logic.md

@@ -123,5 +123,5 @@ end
 
 ## Replacing Models or Controllers
 
-If your customizations are so large that you overwrite majority of a given Model or Controller we recommend to drop the `_decorator` pattern and overwrite the Model or Controller completely in your project. This will make future Spree upgrades easier.
+If your customizations are so large that you overwrite the majority of a given Model or Controller we recommend to drop the `_decorator` pattern and overwrite the Model or Controller completely in your project. This will make future Spree upgrades easier.