Update NOTE and IMPORTANT quotes to be multi-line

nahk-ivanov · nahk-ivanov · commit f624af8f0ab9 · 2020-01-23T21:52:19.000-08:00
diff --git a/docs/ssma/db2/messages/db22ss0573.md b/docs/ssma/db2/messages/db22ss0573.md
@@ -70,4 +70,5 @@ GO
 CREATE UNIQUE INDEX [CUST_CID_XMLIDX] ON [SAMPLE].[CUSTOMER] ([INFO$CID])
 ```
 
->[!IMPORTANT] Adding an extra column to the table (computed column in this case) will affect all `SELECT *` queries. Make sure your application explicitly lists all columns in the `SELECT` statements or disregards any extra columns that might be returned.
+> [!IMPORTANT]
+> Adding an extra column to the table (computed column in this case) will affect all `SELECT *` queries. Make sure your application explicitly lists all columns in the `SELECT` statements or disregards any extra columns that might be returned.
diff --git a/docs/ssma/oracle/messages/o2ss0007.md b/docs/ssma/oracle/messages/o2ss0007.md
@@ -69,4 +69,5 @@ BEGIN CATCH
 END CATCH;
 ```
 
->[!IMPORTANT] Trying to use `ISNUMERIC()` function in a check constraint for this scenario is not a viable solution, because `ISNUMERIC()` is designed to check for strings that might represent numeric values and not numeric underflow and overflow conditions.
+> [!IMPORTANT]
+> Trying to use `ISNUMERIC()` function in a check constraint for this scenario is not a viable solution, because `ISNUMERIC()` is designed to check for strings that might represent numeric values and not numeric underflow and overflow conditions.
diff --git a/docs/ssma/oracle/messages/o2ss0038.md b/docs/ssma/oracle/messages/o2ss0038.md
@@ -20,7 +20,8 @@ A hierarchical query is a type of SQL query that handles hierarchical model data
 
 When converting the hierarchical query, SSMA emulates it to a corresponding solution as a recursive query.
 
-> [!NOTE] A recursive CTE can greatly simplify the code required to run a recursive query within a statement. Oracle's `START WITH` clause becomes the first nested `SELECT`, the base case of the recursion, to be `UNION`-ed with the recursive part which is just another `SELECT`.
+> [!NOTE]
+> A recursive CTE can greatly simplify the code required to run a recursive query within a statement. Oracle's `START WITH` clause becomes the first nested `SELECT`, the base case of the recursion, to be `UNION`-ed with the recursive part which is just another `SELECT`.
 
 When aggregate function (i.e. `MAX`, `MIN`, etc.) is used as a part of sub query in a hierarchical query, SSMA cannot convert the hierarchical query to corresponding SQL Server query and generates a conversion error.
 
@@ -130,7 +131,7 @@ You can now use SSMA to convert the result to SQL Server.
 
 * O2SS0047: Hierarchical queries with asterisk not supported
 * O2SS0119: Hierarchical queries in sub query factoring clauses are not supported
+* [O2SS0268: Hierarchical query with OUTER JOIN cannot be converted](o2ss0268.md)
 * O2SS0285: Hierarchical query was not converted
-* O2SS0268: Hierarchical query with OUTER JOIN cannot be converted
 
 In most of these situations, consider what the query is trying to accomplish and rewrite it to use the emulation.
diff --git a/docs/ssma/oracle/messages/o2ss0054.md b/docs/ssma/oracle/messages/o2ss0054.md
@@ -33,9 +33,10 @@ BEGIN
 END;
 ```
 
->[!NOTE] This is a bad code example of Oracle, as Oracle also generates an error message when you try to execute this code.
+> [!NOTE]
+> This is a bad code example of Oracle, as Oracle also generates an error message when you try to execute this code.
 
-When you try to convert the above code in SSMA, it does not identify the user defined exception 'MYEXCEPTION_1' and hence generates the following error message:
+When you try to convert the above code in SSMA, it does not identify the user defined exception `MYEXCEPTION_1` and hence generates the following error message:
 
 > O2SS0054: Unable to convert EXCEPTION_INIT
 
diff --git a/docs/ssma/oracle/messages/o2ss0094.md b/docs/ssma/oracle/messages/o2ss0094.md
@@ -57,7 +57,8 @@ To resolve this error, you should perform the following steps:
 
 The SSMA conversion option **Convert OPEN-FOR statements for REF CURSOR OUT parameters** is used because there is an ambiguity when a `REF CURSOR` output parameter is opened in the procedure. The `REF CURSOR` might be fetched in the caller procedure or used directly by the application (SSMA can handle this if the option is set to **Yes**).
 
->[!NOTE] After converting this query, SSMA generates a warning message **O2SS0259: CURSOR type was converted to VARCHAR (8000)**. You can generally ignore this warning.
+> [!NOTE]
+> After converting this query, SSMA generates a warning message **O2SS0259: CURSOR type was converted to VARCHAR (8000)**. You can generally ignore this warning.
 
 ## Related conversion messages
 
diff --git a/docs/ssma/oracle/messages/o2ss0188.md b/docs/ssma/oracle/messages/o2ss0188.md
@@ -49,5 +49,5 @@ If the `SEQUENCE` that you are referencing is in another database using a databa
 ## Related conversion messages
 
 * O2SS0214: Column has bound sequence, but sequence was not found in source metadata
-* [O2SS0216: Call to identity sequence CURRVAL not supported](o2ss0216.md)
+* [O2SS0217: Call to identity sequence CURRVAL not supported](o2ss0217.md)
 * [O2SS0221: Call to identity sequence NEXTVAL not supported](o2ss0221.md)
diff --git a/docs/ssma/oracle/messages/o2ss0265.md b/docs/ssma/oracle/messages/o2ss0265.md
@@ -92,7 +92,8 @@ BEGIN
 END
 ```
 
->[!NOTE] In general practice, the cursor should be fetched before doing any operation on `CURSOR` attributes. So for the above example, make sure to execute `FETCH c1 INTO @emp_no` before doing any operations on the cursor.
+> [!NOTE]
+> In general practice, the cursor should be fetched before doing any operation on `CURSOR` attributes. So for the above example, make sure to execute `FETCH c1 INTO @emp_no` before doing any operations on the cursor.
 
 ## Related conversion messages
 
