Make titles (and their formatting) consistent #211
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Added 6 missing properties to reference page. * Made some Acrolinx fixes. * acrolinx updates * link cleanup * switch to cardsL * a ltitle more cleanup * a ltitle more cleanup2 * a ltitle more cleanup3 * Added Resources section to TOC per Craig's suggestion. * Had to remove parens to fix a validation error. * Changing mistaken memory limit of 2 GB back to 3.25 GB * Another try at fixing mysterious validation error. * AAAAAAAAAAAAAAAAAAARGH * Added spaces after EOL in desperate attempt to fix. * Okay, this time I tried removing whitespace. * removce duplicate * redirect * Okay, this time I removed the trailing backsplash. * Okay, this time I removed the asterisks from the next line. * Oh. * Minor fixes * Fixed a broken link. * Update quickstart-install-connect-clouds.md aws added * removed en-us from urls * Update quickstart-install-connect-clouds.md * Revised out-of-date topic for current tool. * Forgot to update freshness date. * Removed a reference to 2016 version. * Update quickstart-install-connect-clouds.md * Update TOC.md * Update install-sql-server-servicing-updates.md * added "or later" as recommended by @douglaslMS * Minor fixes * little correction of bytes vs. characters * Fixing docker link to windows image * Minor fix * Fixed erroneous default value per email from dev. * Made some Acrolinx fixes. * updated virtual machine list * Acrolinx changes * Add missing closing bracket * returning the right content to the OLAP catalog page * Fix emphasis * returning the right content to the OLTP catalog page * reverted SqlBindR link * Update database-catalog-oltp.md * Add Oxford comma for consistency * removed bold from VM name * deprecated reference to config file * updated branding * updated branding. added Python * Acrolinx fixes * Acrolinx fixes * Shortened the new TOC entries I added yesterday. * minor fixes * add APS * added graphics to headers * C6026: Unrecognized character in title Hello, @Shamikg, Localization team have reported source content issue that cause localized version to have broken format compared to en-us version. There are characters instead of an apostrophe. Please help to check my proposed file change into the article and help to merge if you agree with fix. If not, please let me know either if you would like me to fix it in another way within this PR, if you prefer to fix it in another PR, or if I should close this PR as by-design. In case of using another PR, please let me know of your PR number, so we can confirm and close this PR. Many thanks in advance. * C6026: Unrecognized character in title Hello, @Shamikg, Localization team have reported source content issue that cause localized version to have broken format compared to en-us version. There are characters instead of an apostrophe. Please help to check my proposed file change into the article and help to merge if you agree with fix. If not, please let me know either if you would like me to fix it in another way within this PR, if you prefer to fix it in another PR, or if I should close this PR as by-design. In case of using another PR, please let me know of your PR number, so we can confirm and close this PR. Many thanks in advance. * edits. added images * vendor edits * vendor edits * C6028: Unrecognized character in title Hello, @Shamikg, Localization team have reported source content issue that cause localized version to have broken format compared to en-us version. There are characters instead of an apostrophe. Please, help to check my proposed file change into the article and help to merge if you agree with fix. If not, please let me know either if you would like me to fix it in another way within this PR, if you prefer to fix it in another PR, or if I should close this PR as by-design. In case of using another PR, please let me know of your PR number, so we can confirm and close this PR. Many thanks in advance. * removed images, left colour * C6029: Unrecognized character in title Hello, @Shamikg, Localization team have reported source content issue that cause localized version to have broken format compared to en-us version. There are characters instead of an apostrophe. Please, help to check my proposed file change into the article and help to merge if you agree with fix. If not, please let me know either if you would like me to fix it in another way within this PR, if you prefer to fix it in another PR, or if I should close this PR as by-design. In case of using another PR, please let me know of your PR number, so we can confirm and close this PR. Many thanks in advance. * C6030: Unrecognized character in title Hello, @Shamikg, Localization team have reported source content issue that cause localized version to have broken format compared to en-us version. There are characters instead of an apostrophe. Please, help to check my proposed file change into the article and help to merge if you agree with fix. If not, please let me know either if you would like me to fix it in another way within this PR, if you prefer to fix it in another PR, or if I should close this PR as by-design. In case of using another PR, please let me know of your PR number, so we can confirm and close this PR. Many thanks in advance. * Update what-s-new-in-ssma-for-sybase-sybasetosql.md * updated branding, instructions, and screenshots * edits * edited client topics * updated main setup topic. added images * edits to main command line setup topic * edit pass: dma-assesssqlonprem * updates * updated reference topics * update branding in the setup FAQ * branding updates * link fixes * Fix repeated sentence Remove one occurrence of "Top is a logical and physical operator." from being repeated twice. * C3116: LOCBLOCKER - Missing content due to incorrect format Hello, @BYHAM, Localization team has reported source content issue that cause localized version to have blocked content. All < > which are incorrectly place should be removed. Please, help to check my proposed file change into the article and help to merge if you agree with fix. If not, please let me know either if you would like me to fix it in another way within this PR, if you prefer to fix it in another PR, or if I should close this PR as by-design. In case of using another PR, please, let me know of your PR number, so we can confirm and close this PR. Many thanks in advance. * Various updates to Everest overview topic. * Made one more formatting update. * Update always-encrypted-database-engine.md Fixed a typo. * added new tokens and update tokens for new branding * Acrolinx edits * ACrolinx fixes * Acrolinx fixes * fixed includes * Update guidelines-for-online-index-operations.md removed public preview for resumable index * corrected ms.workload metadata values * Update alter-index-transact-sql.md Removed public preview for resumable index * Metadata updates for author and manager. * Update sys-index-resumable-operations.md removed public preview * removed double ms.prod * Update create-table-transact-sql.md Remove public preview * Update create-table-transact-sql.md * removed bookmark from link * repaired include * Light update to refresh * Fix duplicate SQL 2012 in supported servers Hopefully I did that right, I'm a little new to Git/Markdown. The following URL lists SQL 2012 twice but then later on shows that SQL 2014 is supported with the SQL Native Client v11.0 https://docs.microsoft.com/en-us/sql/relational-databases/native-client/applications/support-policies-for-sql-server-native-client * Fix bad example for sp_changemergepublication As is [documented](https://docs.microsoft.com/sql/relational-databases/system-stored-procedures/sp-changemergepublication-transact-sql), `sp_changemergepublication` only accepts `90RTM` and `100RTM` for `publication_compatibility_level`, and it will give an error on other values. It's neither necessary nor possible to increase the compat level beyond `100RTM`, even for later versions of SQL Server, and implying it is [confuses people](https://stackoverflow.com/q/47076507/4137916). A possible alternative is to remove this example altogether, as, at present, almost nobody has any need to change the property. * fix typo in COALESCE function description * Removed some extraneous characters from code sample. * Add Partners to Montiroing. * Add quest * Update sentryone link * Capitalize "Datasheet" * Match spec dimension width (160 Px) * adding reference to SQL2017 * Fixed SQL Server version number to match metadata Metadata says: ms.prod: "sql-server-2016" but doc said: "SQL Server 2012" * Update sql-server-help-installation.md * Unclear large string types can't be used The description of the data type does not explicitly call out nvarchar(max) or varchar(max) which don't work. * Unclear large string types can't be used The description of the data type does not explicitly call out nvarchar(max) or varchar(max) which don't work. * Update sql-server-linux-setup.md * Update quickstart-install-connect-clouds.md * Linked to regions page, removed supported regions. * Removed en-us from URLs. * added new Python issues * added issue for path of pretrained models * added strings as factors issue which is not specific to SQL but a common one * Acrolinx fixes. Amendments from Tri (developer) * added updated art. started update of older Python and R topics * Update alter-database-scoped-configuration-transact-sql.md Removing the "public preview" remark about IDENTITY_CACHE, since we are no longer in public preview :) * updated links * branding and links * Update database-catalog-oltp.md * Update database-catalog-oltp.md * minimal edits. created bugs for missing content * edits. created bug for updates * Update quickstart-install-connect-clouds.md * updated max capacity for SQL2017 * Acrolinx fixes * updated branding and fixed typos * added implied auth art and updated related topics * Update maximum-capacity-specifications-for-sql-server.md * removing reference to index count there is no longer a limit on nr of indexes on SQL2017 * note about index limit * Update sp-server-diagnostics-transact-sql.md * Update compute-capacity-limits-by-edition-of-sql-server.md * Update compute-capacity-limits-by-edition-of-sql-server.md * meta * acro * Update indexes-for-memory-optimized-tables.md * C6025: LOCBLOCKER - Missing ``` that blocking content for localization Hello, @jeannt, There is a source issue that causes localizable text to be blocked from localization. Missing ``` are blocking content for localization. Please, help to check my proposed file change and help to merge if you agree with fix. In case of using another PR, please let me know of your PR number, so we can confirm and close this PR. Many thanks in advance.
This reverts commit 6db2a69.
Revert "sync"
Contributor
Author
|
Hold on. I found more changes that need to be made. I had not realized earlier the extent of the compound assignment operators. The naming really should be consistent with pretty much all other languages out there. Here are several examples, most of them being from within Microsoft-land:
Apparently neither Oracle, nor MySQL, nor PostgreSQL, nor DB2 have compound operators, so can't compare with them. They suck. With respect to Modulo vs. Modulus: |
Contributor
Author
|
There are too many changes for the moment. I will resume again tomorrow and post a message indicating when complete. |
Contributor
Author
|
ALL DONE! (or so I believe 😉 ). Serves me right, I suppose, for thinking, "Oh, this should only affect a few pages". D'oh! |
Contributor
Author
|
@craigg-msft Just FYI: I am all done this PR now (unless you or a reviewer finds something to change). |
Contributor
Contributor
Author
|
@craigg-msft You are quite welcome. And no need to apologize about taking a few extra days. I completely understand, and nobody is waiting for these changes 😉 . It is definitely a lot of files so I didn't expect that it would get pushed through quickly. |
|
@srutzky : Thanks for your contribution to the SQL documentation! The author, @"BYHAM", has been notified to review your proposed change. |
Contributor
Contributor
Author
|
@craigg-msft Yer welcome, and sounds good. Whatever you feel is best. Just out of curiosity, would it have worked to merely edit the files directly in branch of my fork? When I created the PR, I made sure that the "allow owners (or whoever) to make changes" was checked. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Made titles and formatting consistent using the following as guides:
Changes:
+=for numbers) to be "Add and Assignment" since=is assignment, and "equals" implies a test (i.e.IF) which this isn't.=is assignment, and "equal" implies a test (i.e.IF) which this isn't.