Convert a few notes to tip

Author: browniebroke

docs/api-guide/generic-views.md

@@ -96,8 +96,8 @@ For example:
         user = self.request.user
         return user.accounts.all()
 
-!!! note
-    If the `serializer_class` used in the generic view spans orm relations, leading to an n+1 problem, you could optimize your queryset in this method using `select_related` and `prefetch_related`. To get more information about n+1 problem and use cases of the mentioned methods refer to related section in [django documentation][django-docs-select-related].
+!!! tip
+    If the `serializer_class` used in the generic view spans ORM relations, leading to an N+1 problem, you could optimize your queryset in this method using `select_related` and `prefetch_related`. To get more information about N+1 problem and use cases of the mentioned methods refer to related section in [django documentation][django-docs-select-related].
 
 ### Avoiding N+1 Queries
 

docs/api-guide/parsers.md

@@ -20,7 +20,7 @@ The set of valid parsers for a view is always defined as a list of classes.  Whe
 !!! note
     When developing client applications always remember to make sure you're setting the `Content-Type` header when sending data in an HTTP request.
 
-    If you don't set the content type, most clients will default to using `'application/x-www-form-urlencoded'`, which may not be what you wanted.
+    If you don't set the content type, most clients will default to using `'application/x-www-form-urlencoded'`, which may not be what you want.
 
     As an example, if you are sending `json` encoded data using jQuery with the [.ajax() method][jquery-ajax], you should make sure to include the `contentType: 'application/json'` setting.
 

docs/api-guide/relations.md

@@ -15,7 +15,7 @@ Relational fields are used to represent model relationships.  They can be applie
     The relational fields are declared in `relations.py`, but by convention you should import them from the `serializers` module, using `from rest_framework import serializers` and refer to fields as `serializers.<FieldName>`.
 
 !!! note
-    REST Framework does not attempt to automatically optimize querysets passed to serializers in terms of `select_related` and `prefetch_related` since it would be too much magic. A serializer with a field spanning an orm relation through its source attribute could require an additional database hit to fetch related objects from the database. It is the programmer's responsibility to optimize queries to avoid additional database hits which could occur while using such a serializer.
+    REST Framework does not attempt to automatically optimize querysets passed to serializers in terms of `select_related` and `prefetch_related` since it would be too much magic. A serializer with a field spanning an ORM relation through its source attribute could require an additional database hit to fetch related objects from the database. It is the programmer's responsibility to optimize queries to avoid additional database hits which could occur while using such a serializer.
 
     For example, the following serializer would lead to a database hit each time evaluating the tracks field if it is not prefetched:
 

docs/tutorial/1-serialization.md

@@ -26,7 +26,7 @@ pip install djangorestframework
 pip install pygments  # We'll be using this for the code highlighting
 ```
 
-!!! note
+!!! tip
     To exit the virtual environment at any time, just type `deactivate`.  For more information see the [venv documentation][venv].
 
 ## Getting started